Dotdigital (Dotmailer) ↔ Sage 200 Integration
DotdigitalMarketing automationCustomers, consent and order history synced out of Sage 200 — segmentation and triggered campaigns driven by what the ledger actually knows.
Dotdigital (formerly Dotmailer) is the marketing automation platform; Sage 200 is where the customer truth lives — accounts, contacts, marketing preferences, and every order and invoice ever raised. The integration feeds Dotdigital the segments that make campaigns convert: customers who bought X but not Y, accounts overdue for reorder, lapsed buyers by last-invoice date, consent flags honoured at source. Done properly it's a scheduled sync from Sage's own data — not a CSV exported on a Friday. The subtleties are consent (what Sage records as opted-in must win), segmentation freshness (a 'lapsed 30 days' list that's a week stale misfires), and making sure marketing never sees the credit-control customers nobody wants to upsell.
Data Flows
- 1
Contacts → Dotdigital
Customer accounts and their contacts sync to Dotdigital address books — mapped by segment (trade, retail, key-account), with custom fields carrying the Sage data marketing actually segments on: account manager, region, payment terms, customer type.
- 2
Order history → insight
Order and invoice lines feed Dotdigital's contact insight data: last order date, lifetime value, category spend, average order value. That's what powers reorder-nudge and win-back campaigns — not guesswork.
- 3
Consent → suppression
Marketing preferences recorded in Sage (or unsubscribes captured in Dotdigital) reconcile both ways. Sage's flag is authoritative for legal consent; Dotdigital's unsubscribe suppresses sends instantly.
- 4
Behavioural triggers
Sage events can trigger Dotdigital programs: first order → welcome series, invoice overdue → stop marketing sends, quote sent-not-ordered → nudge sequence.
Where These Integrations Go Wrong
The failure modes we design around — most Dotdigital ↔ Sage projects hit at least two of these.
Consent is a legal field, not a sync field
UK PECR/GDPR mean a contact that opted out can't reappear because the nightly sync re-added them. Suppressions must be applied before contacts upsert — and the audit trail of who consented when has to live somewhere durable.
Don't market to credit-hold accounts
Sending a 'we miss you' campaign to an account 90 days overdue is a fast way to annoy the exact customers credit control is chasing. Credit status syncs as a suppression field, not just a segment label.
Order-line volume gets big fast
Pushing every invoice line forever blows up Dotdigital's insight storage. Aggregate at the right level — category spend, RFM scores, last-N-orders — rather than replicating Sage's line detail.
Contact ≠ account
Sage accounts carry multiple contacts with different roles. Sending reorder reminders to the accounts-payable contact instead of the buyer is a mapping mistake — role/type fields need to drive which contacts sync where.
What's Included
- Customer/contact sync to Dotdigital address books with segment mapping
- Order-history insight feed (RFM, category spend, reorder signals)
- Bidirectional consent/suppression reconciliation with Sage authoritative
- Credit-hold and account-status suppression fields
- Trigger wiring for Sage-event-driven programs
- Sync monitoring with failure alerts (no silent list drift)
Who It's For
Sage 200 businesses using Dotdigital for email/SMS marketing where campaigns run on stale exports — or where nobody trusts the list because consent and credit status aren't reflected. Especially distributors with long reorder cycles where purchase history is the best targeting signal.
FAQ
Dotmailer is the old name — does it matter?
No — Dotmailer rebranded to Dotdigital; the platform and APIs are continuous. If your search said 'dotmailer sage integration', this is the same product.
Can Dotdigital write back to Sage?
Yes, selectively — unsubscribes and preference changes should flow back so Sage's consent record stays current, and campaign engagement scores can annotate the customer record for sales. We don't sync ephemeral engagement events into Sage; that noise belongs in Dotdigital.
What about contacts that aren't customers yet?
Prospects live fine in Dotdigital without Sage records — we sync the Sage side and leave prospect acquisition inside Dotdigital. When a prospect becomes a customer, the sync links rather than duplicates them (email match with a merge rule).
Scope Your Dotdigital Build
Fixed quote once we know your Sage version, the flows you need and the volumes.