Summary
This integration sends an iPaaS.com Customer to Dotdigital as a contact. Each Customer is written to Dotdigital with its email, name, mobile number, email format, and opt-in type so that Dotdigital's contact lists stay consistent with the current iPaaS.com Customer record. It is a one-way, combined Add/Update flow: a Customer that is not yet linked is created, and a Customer that matches an existing Dotdigital contact is updated in place.
ID Format
Manual Sync ID: the iPaaS.com Customer ID (for example, 150437). A single Customer can be sent on demand from the iPaaS.com Manual Sync page by entering this ID.
External ID Format
After a successful transfer, iPaaS.com records the Dotdigital contact identifier (for example, 129212619) as the external-id link on a dedicated external-id record. Later changes to the same Customer are then routed to the same Dotdigital contact rather than creating a duplicate.
Deleted Record Support
Deleted records are not supported. This integration adds and updates contacts only; deleting a Customer in iPaaS.com does not propagate a deletion to Dotdigital, and removing a contact from Dotdigital is not performed by this flow.
Custom Field Support
Dotdigital stores additional contact information in data fields. Subscribers or their MiSP create these data fields in Dotdigital under Settings → Contacts → Contact data fields, then map iPaaS.com Customer values (including iPaaS.com custom field values) into them. Only data fields that already exist in Dotdigital can be populated.
Mapping Collection Status
Status: Enabled.
Trigger Events: Customer Create and Customer Update. Subscribers or their MiSP enable these under Outbound Data Flows by subscribing to the Customer created and Customer updated events. No automatic transfers occur until those triggers are enabled. Dotdigital does not send change notifications back to iPaaS.com, so these outbound triggers are what drive this flow.
Duplicate or Conflicting Mappings
This single Add/Update flow handles both create and update; routing depends on whether the contact already exists.
Duplicate Matching
The integration matches an incoming Customer to an existing Dotdigital contact using both the email address and the mobile number:
If neither identifier matches an existing contact, a new contact is created.
If one or both identifiers match the same existing contact, that contact is updated and linked.
If the email matches one contact and the mobile number matches a different contact, the transfer stops with an error so the conflict can be resolved before the record is written. See the Dotdigital Error Messages article for the message text and resolution steps.
Because matching is by email and mobile number, two iPaaS.com Customers that share an email address or mobile number resolve to the same Dotdigital contact.
Supported Child Collections
None. The contact is written from the Customer record's own fields; there are no child collections.
System Caveats
Dotdigital Caveats
Email is mandatory: Dotdigital rejects any contact without a valid email address. A Customer with no email is not transferred.
Mobile number format: Mobile numbers must be in E.164 international format, including the country code (for example, +14155550123), or Dotdigital rejects the value.
Opt-in type: The shipped opt-in type is Unknown. Subscribers or their MiSP should set it to the value that matches how consent was actually collected so that Dotdigital holds accurate consent records.
iPaaS.com Caveats
Mobile number sourced from a custom field: The mobile number is read from the iPaaS.com Customer custom field DotDigital_PhoneNumber. A Customer without that custom field populated sends no mobile number.
Full-record update: Each transfer writes the full set of mapped contact fields. Dotdigital data fields that are not part of these mappings are not maintained by the transfer; manage all contact data fields that should stay in sync through the mappings on this flow.
Setup Requirements
Dotdigital
Create an API user with permission to access the Contacts API (Settings → Access → API users).
Create any Dotdigital contact data fields you intend to map under Settings → Contacts → Contact data fields before enabling the flow.
iPaaS.com
Enter the Dotdigital API User and API Password in the subscription settings.
Integration Flow
A Customer is created or updated in iPaaS.com, or a Customer is sent on demand from the Manual Sync page.
The integration matches the Customer to an existing Dotdigital contact by email address and mobile number.
If a matching contact is found, it is updated; if not, a new contact is created.
The integration writes the mapped contact fields — email, first name, last name, mobile number, email type, and opt-in type — to Dotdigital.
Mappings
This flow does not have a mapping filter applied. Every iPaaS.com Customer reached through an enabled outbound trigger or Manual Sync is processed.
Add/Update Dotdigital Contact FROM iPaaS.com
Mapping Type | Source Field (iPaaS.com) | Destination Field (Dotdigital) | Description |
Field | EmailAddress | Required. The contact's email address, used as the primary identifier when creating or matching the contact. Dotdigital rejects any contact without a valid email, and the integration matches on email (together with mobile number) so a repeat transfer updates the existing contact instead of creating a duplicate. Must be a valid email format and no longer than 255 characters. | |
Field | FirstName | FIRSTNAME | Recommended. The contact's first name, used for personalization in campaigns and automations. Provide a value no longer than 50 characters. |
Field | LastName | LASTNAME | Recommended. The contact's last name, used for personalization in campaigns and automations. Provide a value no longer than 50 characters. |
Field | DotDigital_PhoneNumber | mobileNumber | Recommended. The contact's mobile number, read from the iPaaS.com Customer custom field because the Customer record has no native mobile field. Supports duplicate matching on mobile number. Dotdigital requires E.164 international format, including the country code (for example, +14155550123). |
Static | "HTML" | emailType | Sets the email format Dotdigital uses when sending to this contact. The integration ships a fixed value of HTML, which delivers rich, formatted marketing emails. The allowed values are HTML and PlainText. Subscribers or their MiSP may change this to PlainText for a contact set that must receive text-only email. |
Static | "Unknown" | optInType | Sets the contact's opt-in type, which records the level of marketing consent captured. The integration ships a value of Unknown, meaning the opt-in status is not specified by the source system. The allowed values are Unknown, Single, Double, and VerifiedDouble. Subscribers or their MiSP should set this to the opt-in type that matches how consent was actually collected. |
Error Handling
Email and mobile number point to two different contacts — the incoming email matches one existing Dotdigital contact while the mobile number matches a different one. Resolution: Reconcile the records in Dotdigital so the email and mobile number resolve to a single contact, then re-run the transfer. See the Dotdigital Error Messages article for the exact message text.
Missing email — the email value is null or empty. Dotdigital rejects any contact without a valid email address. Resolution: Ensure every Customer has a valid email address in iPaaS.com before syncing.
Invalid email format — the supplied value is not a valid email address. Resolution: Correct the email format on the Customer in iPaaS.com and re-run the transfer.
Invalid mobile number format — the mobile number is not in E.164 international format including the country code. Resolution: Confirm the DotDigital_PhoneNumber custom field value is in E.164 format (for example, +14155550123) before re-running the transfer.
Dotdigital API temporarily unavailable — the Dotdigital API could not be reached when the transfer ran, so the transfer failed. Resolution: Retry the transfer via Manual Sync. The error appears in the iPaaS.com Dashboard / Integration Monitoring / Error Logs.
Testing & Validation
Test Scenarios
Valid contact sync: Create a new Customer in iPaaS.com with email, first name, and last name populated. Expected outcome: a new contact is created in Dotdigital and the Dotdigital contact identifier is saved back on the external-id record.
Update existing contact: Update a Customer that is already linked to a Dotdigital contact, or one whose email or mobile number matches an existing contact. Expected outcome: the existing Dotdigital contact is updated in place rather than duplicated.
Missing email: Sync a Customer with no email address. Expected outcome: the transfer is rejected and an error is logged; no contact is created in Dotdigital.
Mobile number sync: Populate the DotDigital_PhoneNumber custom field in E.164 format and sync the Customer. Expected outcome: the mobileNumber is written to the Dotdigital contact.
Conflicting match: Sync a Customer whose email matches one Dotdigital contact and whose mobile number matches a different one. Expected outcome: the transfer stops with an error and no contact is written.
Validation Checklist
The email address is populated, valid, and written to the Dotdigital email field.
FIRSTNAME and LASTNAME are synced within their 50-character limits.
The DotDigital_PhoneNumber custom field is populated in E.164 format and written to mobileNumber.
After a successful transfer, the Dotdigital contact identifier is saved on the iPaaS.com external-id record so later updates route to the same contact.
emailType and optInType reflect the intended email format and consent type; adjust the shipped defaults if needed.
For an update, confirm the existing Dotdigital contact was modified in place rather than duplicated.