dotdigital

Overview

The dotdigital connector is a Reverse ETL destination intended to sync audience members into dotdigital Address Books.

Status

This destination is not yet available for loading data.

• Credential validation is implemented (the connector can verify your dotdigital credentials).
• Audience syncing (the actual “load” step) is still in development and will fail if you attempt to run it.

Authentication

dotdigital uses Basic Auth with:

• Username
• API password

To create or find your API password, refer to dotdigital’s API/authentication documentation in your dotdigital account.

Setup

1. In dotdigital, ensure you have API access and an API password.
2. In your workspace, add the dotdigital destination.
3. Enter the required authentication fields (below).
4. Save and test credentials.

Configuration fields

Field	Type	Required	Description
username	string	Yes	Your dotdigital API username used for Basic Auth.
api_password	string	Yes	Your dotdigital API password used for Basic Auth.

Hashing and normalization

This destination does not currently expose field-level hashing controls.

If you need hashing for identifiers (for example, hashing emails before sending to a destination), you must perform hashing upstream in your pipeline.

Data contract

Not yet published for this destination.

Streams / objects

This destination is intended to work with:

• Address Books (dotdigital “audiences”)

However, the connector’s load behavior is still in development, so stream/object mappings and supported operations are not yet available.