1) Summary of the integration
The Vortex IQ Dotdigital integration allows customers to manage Dotdigital contacts, campaigns, data fields, and performance reporting using Vortex IQ’s Ask Viq conversational interface. Actions requested by the user are executed against the customer’s Dotdigital account via secure API calls.
- Create contact data fields and retrieve existing data fields
- Create email campaigns and retrieve campaign lists
- Retrieve contacts and update contact data field values
- Send campaigns to selected contacts
- View campaign performance metrics and compare multiple campaigns
- Generate daily or weekly campaign activity reports
2) Onboarding and point of contact
Customers can complete setup self-service from Settings in Vortex IQ. Enterprise and partner deployments can optionally be supported by a Vortex IQ account manager.
3) Integration setup steps
Navigate to Settings and locate the Dotdigital integration card.
Enter your Dotdigital API credentials. Credentials are encrypted at rest.
- Integration Name
- Dotdigital Username
- Dotdigital Password
If you see an “Invalid credentials” error, re-check your username and password.
View, reorder, or remove connected Dotdigital accounts.
Use conversational commands to manage campaigns and reporting.
Create a new email campaign called 'January Winback Offer'List all campaigns containing 'welcome'Show open rate for campaign ID 12345
4) Data fields passed across
| Data type | Examples | Direction |
|---|---|---|
| Contact identity | Email, contact ID | Read / Targeting |
| Contact data fields | Custom attributes and values | Read / Create / Update |
| Campaign metadata | ID, name, status | Read |
| Performance metrics | Open rate, clicks, conversions | Read |
5) Two-way data transfer
This integration supports secure, user-initiated bi-directional data exchange.
6) Marketing preferences and consent
- Unsubscribed or suppressed contacts are not overridden
- No consent flags are modified
- All targeting respects Dotdigital’s permission framework
7) Security and data handling
- Credentials encrypted at rest
- No raw API data shown to end users
- Confirmation required before write actions
