Overview
This mapping transfers Loyalty Certificate data from the iPaaS.com Gift Cards collection to Dotdigital for the specific purpose of triggering automated loyalty email campaigns. When a loyalty certificate is generated in iPaaS.com, this integration sends the necessary details to a pre-configured campaign in Dotdigital, which then delivers the certificate email to the customer. Synchronization is handled via manual sync flows.
Field Constraints
ReceivingCustomerEmail: Must be a valid email format, with a maximum length of 255 characters.
TriggeredCampaignId: Must match an existing and active triggered campaign ID in Dotdigital.
GiftCardValue: Must be a numeric value, supporting up to two decimal places.
GiftCardURL: Must be a valid HTTPS URL.
Integration Settings
Mapping Status: Enabled
Trigger Events: The sync is triggered by a loyalty certificate creation event in iPaaS.com.
ID Format: When manually syncing a certificate, you must enter the correct Certificate ID from iPaaS.com (e.g.,
12345) into the manual sync page.
Custom Field Support
For loyalty certificates, you may want to include additional customer details (like membership level or points balance) in the email. This data can be stored in Dotdigital's custom data fields and accessed in iPaaS.com.
Formula Template
To access a custom field value from Dotdigital within an iPaaS.com flow, use the following function:
return GetValueFromCustomField(customfields, "[CustomFieldName]");
Replace [CustomFieldName] with the name of the data field in Dotdigital.
System Caveats
iPaaS.com
This integration only supports create and update operations. Deletions of loyalty certificates are not transferred to Dotdigital.
Dotdigital
Triggered campaigns must be pre-configured and active in Dotdigital before initiating a sync.
If an invalid
TriggeredCampaignIdis provided, the mapping may fail silently without triggering the campaign.
Setup & Authentication
iPaaS.com Configuration
The Loyalty Certificate to Dotdigital flow must be enabled.
Ensure that the source payload from iPaaS.com provides valid values for the mapped fields.
Dotdigital Configuration
Authentication: An API Key or Token from an active API user is required to authenticate with the Dotdigital API.
Campaigns: You must create and activate the Triggered Campaign that this integration will use to send emails.
Integration Flow
A Loyalty Certificate is generated in iPaaS.com.
The mapping transforms the certificate data and validates the
ReceivingCustomerEmail.The payload is pushed to Dotdigital's Triggered Campaigns API.
Dotdigital validates the
TriggeredCampaignIdand the customer's email address.Upon successful validation, Dotdigital sends the Loyalty Certificate email using the specified campaign template.
Mappings
Mapping Type | Source Field (iPaaS) | Destination Field (Dotdigital) | Description |
Field |
|
| Required. The primary customer's email, used to identify the contact in Dotdigital and populate the recipient email field. |
Field |
|
| Recommended. The name of the recipient, used for personalization. |
Field |
|
| Recommended. The monetary value of the gift card or certificate. |
Static |
|
| Required. The static ID of the specific Dotdigital campaign to be triggered. |
Static |
|
| Recommended. A static link to the gift card or certificate page. |
Error Handling
Invalid Campaign ID
Description: The
TriggeredCampaignIddoes not exist or is inactive in Dotdigital.Resolution: Verify that the static campaign ID in the mapping matches an active triggered campaign in Dotdigital.
Missing Email
Description: The
ReceivingCustomerEmailfield is null or empty.Resolution: The record is skipped, and an error is logged. Ensure every certificate has a valid recipient email.
Invalid URL
Description: The
GiftCardURLis not a valid HTTPS URL.Resolution: The mapping will reject the record. Correct the URL in the mapping to a valid HTTPS link.
Testing & Validation
Test Scenarios
Valid Loyalty Certificate: Generate a certificate with a valid email and campaign ID.
Expected Outcome: The sync succeeds, and the triggered email is sent from Dotdigital.
Missing Email: Attempt to sync a certificate with no
ReceivingCustomerEmail.Expected Outcome: An error is logged in iPaaS.com, and the record is rejected.
Invalid Campaign ID: Use a
TriggeredCampaignIdthat does not exist in Dotdigital.Expected Outcome: The sync may appear to succeed, but no email will be sent. Check Dotdigital logs for errors.
Validation Checklist
TriggeredCampaignIdpoints to an active Dotdigital campaign.GiftCardValueis numeric and within any expected limits.GiftCardURLis a valid and accessible HTTPS link.ReceivingCustomerEmailis a valid email format.
Additional Notes
Be aware of API rate limits from Dotdigital, as they may delay the processing of large batches of loyalty certificates.
Skipped or failed records will not be retried automatically and must be reprocessed manually from iPaaS.com.