> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/dotdigital.md).

# Dotdigital

DotDigital integration helps connect your website events to your DotDigital account. We handle server-side event streaming for you using their Insight Data Collections feature. Setup is quick - just enter your DotDigital API username and password, and we will send events to your DotDigital account.

{% hint style="info" %}
Events are linked to customer profiles via email
{% endhint %}

### Details

Channel Name: dotdigital

### Event Flow

Events are captured from your site and delivered to DotDigital via server-side API using their Insight Data Collections feature. Each event type is automatically created as a separate data collection in your DotDigital account (e.g., "Blotout\_Purchase", "Blotout\_AddToCart") and events are sent using Basic Authentication with your API credentials.


---

# 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://docs.edgetag.io/channels/dotdigital.md?ask=<question>&goal=<user_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.
