Introduction to Dotdigital
Dotdigital is an omnichannel marketing automation platform that helps merchants personalize and automate communications across email, SMS, and other customer-facing channels.
Used by eCommerce merchants and retailers looking to drive revenue through targeted, automated messaging
Well-suited for marketing teams that need segmentation, journey building, and cross-channel campaign tools in one platform
Connecting Dotdigital to iPaaS.com keeps customer, order, and behavior data flowing from your Ecommerce, POS, and ERP systems so your campaigns are always working from accurate, up-to-date information
API Version Support
The integration works with the Dotdigital API, using its contacts, insight-data, and email resources, configured with your Dotdigital credentials. See the Dotdigital Connections and Settings and Dotdigital API Endpoints articles for details.
Data Flows
The table below summarizes the data the integration can move between iPaaS.com and Dotdigital, and in which direction. Arrows show the direction of transfer:
→ iPaaS.com writes the data to Dotdigital
← iPaaS.com reads the data from Dotdigital
↔ the data can move in both directions
Allow Initialization? indicates whether that data can be bulk-loaded from Dotdigital when a subscription first connects. Whether a given flow is enabled, and in which direction, is configured per subscription during implementation.
The table lists the records you configure directly. Data that belongs to one of them travels with its parent rather than transferring on its own: an order carries its line items, taxes, notes and discounts, and a product tracked at the variant level carries each of its variations.
iPaaS.com | Direction | Dotdigital | Allow Initialization? |
Customer | → | Contact | |
Transaction | → | Insight Data | |
Loyalty Certificate | → | Loyalty Certificate | |
Product | → | Insight Data | |
Product Category | → | Insight Data |
Versions and Release Notes
The integration follows its own version numbers. The current version is 1.0.5. Notable releases, newest first:
Version | Release Notes |
1.0.5 (current) | Products, their variants and product categories can now be sent to Dotdigital as account-level insight data, so catalog data is available to Dotdigital's product features and to campaign content. Every error the integration records in the iPaaS.com error logs now carries a stable error code, so an error can be looked up directly — the Dotdigital Error Messages article lists each code with what causes it and how to resolve it, and error wording was tidied so messages read in plain language rather than exposing internal detail. The setting that names the Dotdigital collection for order data was also renamed from Collection Name to Order Collection Name, so that it reads clearly alongside the separate collection-name settings for product and product-category data. Subscriptions that left the setting blank are unaffected. If you had entered your own collection name, see Upgrading to version 1.0.5 below. |
1.0 | Send customers as contacts, transactions as insight data, and loyalty certificates to Dotdigital to power targeted, automated campaigns. |
Upgrading to version 1.0.5
The order collection setting was renamed in this release, and a value entered against the old Collection Name setting is not carried across to Order Collection Name automatically.
If you left the setting blank, nothing changes for you. Blank meant orders were written to a collection named Purchases before the rename, and it means the same afterward, so those orders continue to go exactly where they always have.
If you had entered your own collection name, that value needs to be re-entered against the new setting. Until it is, the new setting is empty, so orders fall back to Purchases — they keep transferring successfully, but to a different collection, with nothing recorded in Integration Monitoring to indicate the change. In most cases iPaaS.com or your MiSP applies this for you as part of the upgrade; the steps are below so you can confirm it, or make the change yourself.
Open your Dotdigital subscription's settings in iPaaS.com.
Check Order Collection Name. If it already holds the name of the collection your orders belong in, no further action is needed.
If it is empty, enter the collection name your orders were previously written to — the value you had entered against the old Collection Name setting. If you no longer have that value to hand, you can find it in Dotdigital under Insight Data, as the collection that has been receiving your orders; iPaaS.com support can also retrieve the value previously saved on your subscription.
Save the setting, then send a single order from the Manual Sync page and confirm it appears in the expected Dotdigital collection.
If orders were sent after the upgrade but before the setting was corrected, they were written to Purchases. Re-sync those transactions so they land in the correct collection. The copies already written to Purchases stay where they are — the integration does not transfer deletions — so remove them in Dotdigital directly if they should not remain.
Leaving the setting empty is a valid choice if Purchases is genuinely where your orders belong. What to avoid is an upgraded subscription that was using its own collection and silently starts writing to Purchases instead.
Features by Release
The capabilities below are grouped by the version in which they became available. For the current behavior and any limitations of a given feature, see the linked reference articles and the Dotdigital Known Limitations article.
Version 1.0 — Marketing data synchronization
Customer synchronization: customers written to Dotdigital as contacts.
Transactions: transactions written to Dotdigital as insight data.
Loyalty certificates: loyalty certificates sent to Dotdigital.
Version 1.0.5 — Product data, coded error messages and clearer settings
Products and variants: products written to Dotdigital as account-level insight data. Products tracked at the variant level also write each variation, so catalog data is available to Dotdigital's product features and campaign content.
Product categories: product categories written to Dotdigital, resolved parent-first so a category's parents exist before the category itself.
Coded error messages: every error the integration can record in the iPaaS.com error logs carries a stable code, listed with its cause and resolution. The code stays the same even if the wording changes, so it is safe to search on and to reference in a support conversation.