Dotdigital Destination
Destination Info
- Accepts Page, Alias, Group, Identify, and Track calls
- Refer to it as Dotdigital in the Integrations object
- This integration is partner owned. Please reach out to the partner's support for any issues.
- This destination is in Beta
Partner Owned
- This integration is partner owned. Please reach out to the partner's support for any issues.
Dotdigital is an all-in-one customer experience and data platform (CXDP) that empowers marketing teams to exceed customer expectations with highly personalized cross-channel journeys.
This destination is maintained by Dotdigital. For any issues with the destination, contact the Dotdigital Support team.
Getting started
- From your workspace’s Destination catalog page search for “Dotdigital”.
- Select Dotdigital and click Add Destination.
- Select an existing Source to connect to Dotdigital (Actions).
- Log in to your Dotdigital account. Expand the User menu in the bottom left and go to Settings > Access > API users.
- Note your API region (r1, r2 or r3) for step 7.
- Create a new API user {:target=”_blank”}.
- In Segment, select your Dotdigital account region and paste the API user and API password in the Dotdigital destination settings.
Destination Settings
Setting | Description |
---|---|
Region | Required. The region your account is in |
Password | Required. Your Dotdigital password. |
Username | Required. Your Dotdigital username |
Available Actions
Build your own Mappings. Combine supported triggers with the following Dotdigital-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Enrol Contact to Program
Creates a program enrolment.
Enrol Contact to Program is a Cloud action. The default Trigger is: type = "track" and event = "Enrol Contact to Program"
Field | Description |
---|---|
Contact Identifier type* | Type: STRING Select the field to identify contacts. |
Email Address | Type: STRING The Contact’s email address. |
Mobile Number | Type: STRING The Contact’s mobile number. |
Program* | Type: STRING List of active programs |
Remove Contact from List
Removes a Contact from a List.
Remove Contact from List is a Cloud action. The default Trigger is: type = "track" and event = "Remove Contact from List"
Field | Description |
---|---|
Contact Identifier type* | Type: STRING Select the field to identify contacts. |
Email Address | Type: STRING The Contact’s email address. |
Mobile Number | Type: STRING The Contact’s mobile number. |
List* | Type: NUMBER The List to remove the Contact from. |
Add Contact to List
Adds a Contact to a list.
Add Contact to List is a Cloud action. The default Trigger is: type = "track" and event = "Add Contact to List"
Field | Description |
---|---|
Contact Identifier type* | Type: STRING Select the field to identify contacts. |
Email Address | Type: STRING The Contact’s email address. |
Mobile Number | Type: STRING The Contact’s mobile number. |
List* | Type: NUMBER The list to add the contact to. |
Data Fields | Type: OBJECT An object containing key/value pairs for data fields assigned to this Contact. Custom Data Fields must already be defined in Dotdigital. |
Additional context
Add Contact to List
Before using the Add Context to List Action, complete the following prerequisites:
- Lists: Create a contact list in Dotdigital {:target=”_blank”}. After you’ve created a list in Dotdigital, return to the Segment app and select your list from the dropdown in the Segment event mapping.
- Data Fields: Create or edit your data fields in Dotdigital, then return to the Segment app, open the event mapping, and map Segment properties to Dotdigital data fields.
Enroll Contact to Program
When you use the Enroll Contact to Program action, Dotdigital creates a contact for the identifier you provide, if the contact doesn’t already exist.
Engage
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true
. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false
.
When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Real-time audience syncs to Dotdigital may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
Setting | Description |
---|---|
Region (required) |
select , defaults to https://r1-api.dotdigital.com. The region your account is in |
Password (required) |
password . Your Dotdigital password. |
Username (required) |
string . Your Dotdigital username |
This page was last modified: 24 Jun 2025
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!