> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-integrations/zap-post-integrations/dotdigital/installation-guide.md).
# Installation Guide
See the steps below, or watch the video
1. Log into **Dotdigital**
2. Once logged in head to **Settings** and **Access**
3. Once in **Access** click on **API Users**
4. Click **Add New API User**
5. The email address will be automatically populated, add a **description**, something like 'ZAPPOST Integration'
6. Add a **password** and click **Save**
7. Once an API user has been created, log into [ZAP-POST](https://app.zappost.com)
8. From the dashboard click on the **integrations** tile
9. Here you will see a tile to add **Dotdigital**
10. Add the **API username** and **password** that was created in Dotdigital
11. Click **Connect**
12. If the correct credentials have been provided, you see a **confirmation**
13. You are all set! Your Dotdigital account is integrated with ZAP-POST. In order to ingest List and Segment data see our Use case how-to guide
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://userguide.zappost.com/zap-integrations/zap-post-integrations/dotdigital/installation-guide.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
