> 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.md).
# Dotdigital
Summary functionality:
* Collect recipient data from Dotdigital Lists and Segments
* Map them to a ZAP\~POST Campaign
* Map any custom fields you have set up in the ZAP\~POST Campaign
* Events are added to Dot Digital contacts.
Integration to Dot Digital is directly available from your ZAP-POST account, once signed in.
When a campaign is created, connect Recipient data via “Data Sources” from within the app, you will be directed to add your Dot Digital API username and password.
Set up is self-service whilst ZAP-POST will assist and manage the set up where required, at no additional cost. All steps are covered in detail in the following pages. All steps are covered in detail in the following pages.
---
# 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 dynamically 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.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 `build a script that syncs our docs to a CMS` 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.
