Overview
This article catalogs the error messages you may encounter when synchronizing data from iPaaS.com to Dotdigital, grouped by the mapping collection flow that produces them. Errors appear in iPaaS.com under Dashboard / Integration Monitoring / Error Logs. Each entry explains what the error means and how to resolve it.
Supported Flows
Add/Update Dotdigital Contact FROM iPaaS.com
Add Dotdigital Transaction FROM iPaaS.com
Add Dotdigital Loyalty Certificate FROM iPaaS.com
Connection and Dotdigital API
Add/Update Dotdigital Contact FROM iPaaS.com
Conflicting contact match
The provided email address and phone number belong to two different contacts in Dotdigital. Ensure both identifiers refer to the same contact before syncing.
Description: The contact's email address matches one Dotdigital contact while the mobile number matches a different Dotdigital contact, so the integration cannot decide which contact to update.
Resolution: In the source record, align the email address and mobile number so they refer to a single contact, or remove the identifier that points to the wrong contact, then re-sync. If both contacts should be one record, merge them in Dotdigital first.
Missing email address
A contact cannot be created in Dotdigital without a valid email address.
Description: The customer being synced has no email address. Dotdigital requires an email address on every contact and rejects the record.
Resolution: Add a valid email address to the customer in the source system before syncing.
Invalid email format
Dotdigital rejected the contact because the email address is not in a valid format.
Description: The email address supplied does not pass Dotdigital's validation.
Resolution: Correct the email address in the source system so it is a properly formatted address, then re-sync.
Add Dotdigital Transaction FROM iPaaS.com
Invalid transaction date
The transaction date could not be read as a valid date.
Description: The order's purchase-date mapping received a value that is not a recognizable date, so it could not be converted to the format Dotdigital expects.
Resolution: Ensure the transaction's created date is populated with a valid date in the source system. If the purchase-date mapping has been customized, confirm it points to a valid date value.
Order could not be linked to a contact
The order could not be attached to a Dotdigital contact because no contact email was resolved.
Description: Dotdigital stores an order against a contact identified by email. The order's customer has no email address on record, so the order cannot be linked.
Resolution: Ensure the order's customer has a valid email address in the source system, then re-sync the order.
Add Dotdigital Loyalty Certificate FROM iPaaS.com
Invalid or inactive campaign
Dotdigital could not send the certificate because the triggered campaign is missing or inactive.
Description: The triggered-campaign id configured on the mapping does not match an existing, active triggered campaign in Dotdigital, so no certificate email is sent.
Resolution: In Dotdigital, confirm the triggered campaign exists and is active, then set the campaign id on the loyalty-certificate mapping to that campaign. See the Dotdigital Loyalty Certificate mapping documentation for where to set this value.
Missing recipient email
The certificate could not be sent because no recipient email address was provided.
Description: The recipient email mapping is empty, so Dotdigital has no address to send the certificate to.
Resolution: Map the recipient email from the source record (the receiving customer's email) so each certificate has a valid recipient, then re-sync.
Connection and Dotdigital API
Authentication failed
iPaaS.com could not authenticate with Dotdigital using the configured API user.
Description: The Dotdigital API user or password is incorrect, expired, or lacks permission for the requested area of the Dotdigital API.
Resolution: Verify the API User and API Password in the subscription settings, and confirm the API user has access to the Contacts, insight data, and triggered campaign areas. See the Dotdigital Connections and Settings article for how to create and enter these credentials.
Dotdigital API error
The transfer failed with an error returned by the Dotdigital API.
Description: Dotdigital rejected the request and returned an error with an HTTP status code. Common causes include a validation failure on the record, a permission restriction on the API user, or a referenced resource that does not exist in Dotdigital.
Resolution: Review the error detail shown in Dashboard / Integration Monitoring / Error Logs, correct the underlying data or permission in the source system or in Dotdigital, then re-sync. If the cause is not clear, contact iPaaS.com Support at support@ipaas.com.
Rate limit reached
The transfer paused because Dotdigital's API rate limit was reached.
Description: Dotdigital limits how many API calls can be made in a given window. When the limit is reached, further calls are held until the window resets.
Resolution: No action is required — the transfer is automatically rescheduled to resume after the rate-limit window resets.