Summary
This document outlines the process for synchronizing Contact records from iPaaS.com to Dotdigital. The integration uses an Add/Update sync method, pushing records from iPaaS to Dotdigital's Contact API to ensure contact lists remain consistent across both platforms.
Field Constraints
EmailAddress: Must be unique, with a maximum length of 255 characters.
FirstName: Maximum length of 50 characters.
LastName: Maximum length of 50 characters.
Integration Settings
Mapping Status: Enabled
Trigger Events: The sync is triggered by Contact Add or Contact Update events in iPaaS.com.
ID Format: When manually syncing a contact, you must use the contact's Email Address (e.g.,
john.doe@example.com) as the unique identifier in the manual sync page input field.
Custom Field Support
Dotdigital uses data fields (custom fields) to store additional contact information. These fields can be accessed and mapped within iPaaS.com.
Formula Template
To map a value to a Dotdigital custom field from iPaaS.com, you can use the following function format:
return GetValueFromCustomField(customfields, "[CustomFieldName]");
Replace [CustomFieldName] with the name of the data field in Dotdigital you wish to populate.
Navigating to Custom Fields in Dotdigital
You can find and manage your custom data fields in Dotdigital by navigating to: Settings > Contacts > Contact data fields
System Caveats
iPaaS.com
If the
EmailAddressfield is missing, the record will be rejected and will not be sent to Dotdigital.Updates to existing contacts require a matching
EmailAddress.
Dotdigital
The Email address is a mandatory field for all contacts.
Duplicate email addresses are not allowed; the integration will update an existing contact if the email already exists.
Setup & Authentication
iPaaS.com Configuration
The Dotdigital connector must be enabled in your subscription.
Define the mapping rules for the standard and custom contact fields.
Dotdigital Configuration
Authentication: The integration requires an API user with valid credentials (API Key/Token).
Permissions: Ensure the API user has the necessary permissions to access the Contacts API.
Integration Flow
A contact is created or updated in iPaaS.com.
The mapping transforms the iPaaS fields according to the defined rules.
The record is pushed to Dotdigital via the Contacts API.
Dotdigital validates the data, particularly the
Email, and either inserts a new contact or updates an existing one.
Mappings
Mapping Type | Source Field (iPaaS) | Destination Field (Dotdigital) | Description |
Field |
|
| Required. The primary identifier for the contact. |
Field |
|
| Recommended. The contact's first name, used for personalization. |
Field |
|
| Recommended. The contact's last name, used for personalization. |
Static |
|
| Sets the opt-in type. Other values include |
Static |
|
| Sets the contact's preferred email format ( |
Error Handling
Missing Email
Description: The
EmailAddressfield is null or empty.
Resolution: The record is rejected by Dotdigital. Ensure every contact has a valid email address in iPaaS.com before syncing.
Invalid Email Format
Description: The provided email does not follow a valid format.
Resolution: An error is returned from the Dotdigital API. Correct the email format in the source system.
Duplicate Email
Description: A contact with the same email address already exists.
Resolution: The integration logic should be configured to update the existing contact record instead of attempting to create a new one.
Testing & Validation
Test Scenarios
Valid Contact Sync: Create a new contact in iPaaS.com with all required fields.
Expected Outcome: The contact is created successfully in Dotdigital.
Missing Email: Attempt to sync a contact without an email address.
Expected Outcome: An error is logged, and the contact is rejected by Dotdigital.
Duplicate Email: Create a contact in iPaaS.com with an email address that already exists in Dotdigital.
Expected Outcome: The existing record in Dotdigital is updated with the new information.
Validation Checklist
The
EmailAddressis populated and synced correctly.The email format is validated.
FirstNameandLastNameare synced within their character limits.
Additional Notes
Be mindful of API rate limits from Dotdigital, as they may delay large-volume syncs.
Dotdigital may automatically normalize data, such as trimming extra spaces from names.