See what the Dotdigital integration can do →
Summary
This mapping sends a loyalty certificate to Dotdigital by triggering a campaign that emails the recipient. When a gift card is generated in iPaaS.com, the integration triggers a pre-configured Dotdigital campaign, which delivers the certificate email using the campaign template. The email carries the recipient name, the certificate value, and a link to the certificate. This is a one-way, send-only flow from iPaaS.com to Dotdigital.
ID Format
When sending a single certificate on demand, the Manual Sync ID is the iPaaS.com gift card number (for example, 10573).
External ID Format
This flow is a triggered send rather than a stored record. Dotdigital sends an email through the triggered campaign; it does not create a certificate record that iPaaS.com can later locate and update. As a result, there is no updatable external-id link between the iPaaS.com gift card and anything stored in Dotdigital.
Deleted Record Support
Deleted records are not supported. The integration is send-only: it triggers a campaign that emails the certificate and provides no way to retrieve or remove a certificate that has already been sent.
Custom Field Support
To include extra details in the certificate email (for example, a membership level or points balance), store the values in Dotdigital contact data fields and reference them in the campaign template. Subscribers or their MiSP create these data fields in Dotdigital under Settings → Contacts → Contact data fields.
Mapping Collection Status
This mapping collection is Enabled.
Trigger Events: Gift Card Create, enabled under Outbound Data Flows.
Duplicate or Conflicting Mappings
This mapping has no collision handling. A repeat transfer of the same gift card re-sends the triggered campaign; there is no in-place update of a previously sent certificate.
Supported Child Collections
None.
System Caveats
Dotdigital Caveats
The triggered campaign referenced by the campaign id must already exist and be active in Dotdigital before a certificate is sent.
The certificate link must be a valid HTTPS URL.
iPaaS.com Caveats
The recipient email, campaign id, and certificate link ship as example values. They must be replaced with production values before the first real transfer; until then, every certificate is sent to the example address and may reference the wrong campaign or link.
Setup Requirements
In Dotdigital, configure an API user able to send triggered campaigns.
In Dotdigital, create and activate the triggered campaign that delivers loyalty certificates, and note its campaign id.
In iPaaS.com, enter the Dotdigital API User and API Password.
On this mapping collection, replace the placeholder recipient email, campaign id, and certificate link with production values before enabling it.
Integration Flow
A gift card is generated in iPaaS.com, either automatically through an enabled outbound trigger or on demand from Manual Sync.
The integration sends a triggered-campaign request to Dotdigital, addressed to the recipient email and referencing the configured campaign.
Dotdigital validates the campaign and the recipient.
Dotdigital emails the certificate to the recipient using the campaign template, populated with the recipient name, certificate value, and certificate link.
Mappings
Add Dotdigital Loyalty Certificate FROM iPaaS.com
This mapping collection has no mapping filter applied. Every iPaaS.com gift card reached through an enabled outbound trigger or Manual Sync is processed.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Dotdigital) | Description |
Static | GiftCardAddresseeEmail | Required. The email address the certificate is sent to, and the contact it is recorded against in Dotdigital. Placeholder value — replace during implementation: the integration ships a fixed test email address. Left unchanged, every certificate is sent to that single test address. Change this mapping to draw the recipient's email from the source record so each certificate reaches the correct contact. | |
Field | ReceivingCustomer | GiftCardAddressee | Recommended. The name of the certificate recipient, used to personalize the certificate email. |
Field | OriginalAmount | GiftCardValue | Recommended. The monetary value of the certificate, provided as a numeric value with up to two decimal places. |
Static | "71711" | TriggeredCampaignId | Required. The Dotdigital triggered campaign that delivers the certificate email. It must reference an existing, active triggered campaign, or no email is sent. Placeholder value — replace during implementation: set it to the id of your own active loyalty-certificate triggered campaign. |
Static | GiftCardURL | Recommended. A link included in the certificate email, intended to point to the gift card or certificate page. Placeholder value — replace during implementation: the integration ships an unrelated sample image link. Set it to a valid HTTPS link to your certificate or gift-card page. |
This mapping collection has no mapping filter applied in the live configuration.
Error Handling
Invalid or inactive campaign: If the campaign id does not match an existing, active triggered campaign in Dotdigital, the transfer may complete without an email being sent. Confirm the campaign exists and is active, then confirm delivery in Dotdigital after the transfer.
Missing recipient email: If the recipient email is empty, Dotdigital cannot deliver the certificate. Ensure a valid recipient email is supplied before the transfer.
Testing & Validation
Test Scenarios
Send a gift card with a valid recipient email and an active campaign id, and confirm the certificate email arrives at the recipient.
Send a gift card referencing an inactive or non-existent campaign id, and confirm that no email is delivered.
Send a gift card with no recipient email, and confirm the certificate is not delivered.
Validation Checklist
The campaign id points to an active Dotdigital triggered campaign.
The recipient email is a valid email address drawn from the source record, not the example test address.
The certificate link is a valid, accessible HTTPS URL pointing to your certificate or gift-card page.
The certificate value appears correctly in the delivered email.
Delivery is confirmed in Dotdigital after the first transfer.