Server-side tracking for Mailchimp
The Mailchimp build is largely a set of decisions about what not to do. Write the identifier to an audience field once and guard it, source money events from the store rather than Mailchimp's mirror, and keep engagement entirely out of the conversion path. What Mailchimp adds is persistence across a nurture period longer than any browser cookie.
Free30 minutesNo obligation
Mailchimp server-side · what breaks
What goes wrong on Mailchimp
- 01
Mailchimp treated as the revenue source
It mirrors the store with a sync delay.
- 02
Engagement sent as conversions
Opens and clicks are abundant and predict little.
- 03
The identifier overwritten by campaign clicks
So email claims sales that paid media produced.
- 04
Mailchimp's own ad features confused with your ad accounts
Two separate reporting worlds.
Mailchimp server-side · the fix
What changes — Mailchimp server-side
Money events sourced from the store
Not from Mailchimp's mirror.
The first-touch identifier preserved on the contact
Guarded against campaign-click overwrites.
Engagement reported, never bid on
Useful internally, wrong as a target.
Mailchimp server-side · architecture
What Mailchimp exposes to a server container
The server-side build around Mailchimp.
- 1
Write the identifier to an audience field at subscribe
Once, and guarded.
- 2
Source money events from the store
The mirror adds delay you do not need.
- 3
Keep engagement out of the conversion path
Report it; never send it.
- 4
Reconcile against the store, not Mailchimp
Because the mirror can drift.
- 5
Use Mailchimp for exclusion audiences
Existing customers should not be paid for twice.
Mailchimp server-side · diagnose
Where Mailchimp tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Check whether the identifier field survives a campaign click
Look at a contact who clicked an email after converting.
- 02
Compare Mailchimp revenue against the store
A gap here is a sync issue and tells you which to trust.
- 03
Look for engagement events sent as conversions
Common and quietly damaging.
- 04
Check whether existing customers are excluded from prospecting
Mailchimp makes this easy and most accounts skip it.
- 05
Measure the nurture length against import windows
Long sequences push sales toward the edge.
Mailchimp server-side · prove
The QA evidence — Mailchimp server-side
Run on Mailchimp specifically, on a live conversion rather than in preview mode.
Source of truth
Your store or billing system's orders — Mailchimp mirrors them and is not the original
- A contact created from a paid click, with the identifier unchanged after a later campaign click.
- Money events confirmed to fire from the store rather than the mirror.
- Revenue reconciled against the store per order over a closed window.
- Engagement events confirmed absent from every conversion action.
- Customer exclusion audiences confirmed active on prospecting campaigns.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Mailchimp server-side · free audit
What we check in the free audit
- Check whether the identifier field survives a campaign click
- Compare Mailchimp revenue against the store
- Look for engagement events sent as conversions
- Check whether existing customers are excluded from prospecting
- Measure the nurture length against import windows
Checked against
Your store or billing system's orders — Mailchimp mirrors them and is not the original
Free30 minutesNo obligation
Mailchimp server-side · when not to buy
When you don't need this on Mailchimp
Worth reading before you buy anything, from us or anyone.
- If your store is already tracked properly, the Mailchimp side may only need the identifier preserved and exclusion audiences wired.
- If you send broadcast email only, most of this does not apply.
- Check whether engagement is currently being sent as conversions — removing it is free and often the largest single gain.
- Mailchimp's own ad features report separately and are not a substitute for your ad accounts.
Mailchimp server-side · what we deliver
What the server-side build gives you on Mailchimp
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from your store's orders
The store is authoritative for revenue; Mailchimp is authoritative for audience and engagement. Say which one a number came from every time, because the two will not agree exactly and the gap is a sync delay rather than a bug.
Deduplicated at every destination
On a shared event ID, verified before any existing path is removed.
Consent enforced before dispatch
A denied destination receives nothing, verified by capture rather than configuration.
Written guarantee
95%+ tracking accuracy
Measured against Your store or billing system's orders — Mailchimp mirrors them and is not the original. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Mailchimp server-side questions, answered
Because it is a mirror. Orders arrive through an integration with a sync delay, so reconciling against it produces gaps that look like tracking bugs and are actually timing. Go to the store directly for anything financial.
An audience field on the contact, written once at subscribe. Contacts persist across the whole nurture, which is exactly the period the identifier needs to survive.
Almost never at Mailchimp's typical scale. A small handler for the store's order webhook covers it.
Persistence and segmentation. Holding an identifier for months, and building exclusion and lookalike audiences from real purchase behaviour. Those are worth having and neither requires it to be your revenue source.
Free · 30 min
Move Mailchimp events off the browser
WhatsAppFree30 minutesNo obligation
