Zonos → Mixpanel · Conversion tracking
Connecting Zonos to Mixpanel
Zonos calculates duties and taxes so the shopper can prepay them, which removes the delivery-time surprise that causes international refusals — and creates a figure in the order that is not your revenue. Mixpanel is a product analytics tool, not an ad platform, which means it has no attribution model of its own and will faithfully report whatever event schema you give it — including a bad one. The join between them succeeds or fails on one thing: whether the distinct_id reaches the Zonos landed-cost order before the conversion happens, because Mixpanel can only match a conversion it can tie back to a click it recognizes.
✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.
Written guarantee
95%+ conversion accuracy on Zonos → Mixpanel
Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.
Built on — and certified for — the platforms that matter
Stape
Pro Partner
Meta
Tech Provider
Tag Manager
TikTok
Events API
Microsoft
UET Partner
CAPI Partner
CAPI Partner
Built on the same partner stack used by enterprise DTC brands.
By the numbers
No fake testimonials.Just the math.
70+
Platforms supported
Shopify · Woo · Magento · BigCommerce · 65 more
8+ / 10
Meta EMQ guaranteed
in writing — keep working free until hit
2–4d
Build to live
accurate data flowing within 7 days
$0
Monthly fees, ever
one-time fixed price · you own the stack
400d
Cookie lifetime
max RFC 6265bis allows · 57× Safari ITP
9
Ad channels covered
Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X
95%+
Tracking accuracy
verified vs Stripe · GA4 · ad-platform reports
30 min
Free founder call
no SDR · no pitch deck · written remediation plan
Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.
Real clients · real videos · real outcomes
Don’t take our word for it. Watch the receipts.
Founders, marketers, and agency owners describing the before-and-after of their Zonos → Mixpanel tracking rebuild — in their own words, on camera.
Why this join usually fails
The distinct_id never reaches Zonos
The single most common cause. Landed-cost calculation runs at checkout and can change the displayed total after the identifier was captured.
Government duty counted as your revenue
On high-duty markets this can be a fifth of the order total. It never reaches you, it is not margin, and including it makes exactly the most expensive markets look like the best performers.
One event schema, two teams, no agreement
Marketing names an event Purchase, the product team names it purchase_completed, and both are sent. Mixpanel treats them as unrelated, every funnel silently splits, and two teams spend a quarter arguing about which number is right when both are.
Nothing reconciles afterwards
An upload that succeeds is not an upload that matched. Mixpanel shows events in the live view within moments. Check that the distinct_id matches the signed-in user rather than a lingering anonymous ID, because that is the failure that quietly breaks every cross-signup funnel.
Architecture
How Zonos and Mixpanel actually connect
Two systems that know nothing about each other. Everything below exists to give them one shared reference.
Step 1
Zonos holds the truth
Prepaid duty sits inside the order total and belongs to a government, not to you. Including it in conversion value inflates international revenue by the duty rate of each market.
Step 2
Mixpanel needs a click to match
Mixpanel needs a distinct_id, an event name and its properties. Events without a distinct_id are rejected; events with the wrong one land on a stranger's profile.
Step 3
The identifier is the bridge
The distinct_id, captured at the visit and carried into the Zonos landed-cost order. Without it there is nothing to join on and no tool fixes that.
Step 4
The event source decides reliability
Send orders at merchandise value, excluding prepaid duties and taxes.
Step 5
Deduplication at the destination
Mixpanel deduplicates on $insert_id within a time window. Without it, a retried server request creates a second event, and because Mixpanel is where product decisions get made, that inflation ends up in a roadmap rather than in an ad report.
Diagnose it honestly
Working vs. broken, side by side
Both states look identical from the Mixpanel dashboard, which is why this runs for months before anyone notices.
Normal — not a fault
The distinct_id present on the order
Visible on the record itself in Zonos, not merely captured somewhere on the site.
Sent from the order record with the Zonos duty breakdown
Server-side, so it does not depend on the customer's browser still being there.
Deduplicated correctly
Mixpanel deduplicates on $insert_id within a time window. Without it, a retried server request creates a second event, and because Mixpanel is where product decisions get made, that inflation ends up in a roadmap rather than in an ad report.
Reconciles with the source
Mixpanel's count and Zonos's records agree within a few percent over a closed window.
Actually broken
The distinct_id missing on most records
Landed-cost calculation runs at checkout and can change the displayed total after the identifier was captured.
Sent from the browser
Anyone who closes the tab, blocks the script or converts without a page load is invisible. On high-duty markets this can be a fifth of the order total. It never reaches you, it is not margin, and including it makes exactly the most expensive markets look like the best performers.
Counted twice, or not at all
Marketing names an event Purchase, the product team names it purchase_completed, and both are sent. Mixpanel treats them as unrelated, every funnel silently splits, and two teams spend a quarter arguing about which number is right when both are.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to Zonos. A wrong number that nobody checks is indistinguishable from a right one.
Diagnostic sequence
Diagnostic order
Each step rules out a class of cause. Run them in order and the last one usually has a single explanation standing.
- 1
Count orders carrying the distinct_id
The ceiling on everything else. Do this before debugging anything downstream.
- 2
Follow one real conversion end to end
From the ad click through Zonos and into Mixpanel.
- 3
Check whether prepaid duty is inside the conversion value
If the value matches the customer's total, it almost certainly is.
- 4
List every event name in the project and look for near-duplicates
Case differences, tense differences and synonyms are the usual finding, and they are cheap to fix before a year of data is built on them.
- 5
Read the match rate, not the success message
Mixpanel shows events in the live view within moments. Check that the distinct_id matches the signed-in user rather than a lingering anonymous ID, because that is the failure that quietly breaks every cross-signup funnel.
Source-of-truth validation
How it gets proven
Against Zonos's own records, not against either platform's dashboard.
- The distinct_id confirmed present on a live order.
- A real conversion followed from click through Zonos to Mixpanel.
- Purchase events reconciled per transaction against your billing system, with identity aliasing verified across the signup boundary.
- Merchandise-value revenue reconciled per market against imported conversions, with duty excluded.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later.
Straight talk
When you don't need this
Worth reading before paying anyone, including us.
- If Mixpanel already reports conversions that reconcile against Zonos's records within a few percent, this join is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred orders and count how many carry the distinct_id. Ten minutes, free, and it tells you whether any of this is worth doing.
- Domestic-only sellers have no duty component and none of this applies.
- If you already have the same events in a warehouse and nobody is running product analysis on them, adding Mixpanel adds a second source of truth rather than an answer.
Who this is for
Honest about who we’re a fit for.
We don’t take every project. Here’s how to tell if we’re right for you.
You’re a great fit if…
- You run Zonos → Mixpanel (or are migrating to it)
- You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
- Your reported ROAS doesn’t match what your bank account is saying
- You want to own your tracking stack — no monthly SaaS fees forever
- You have 2–4 days to do this once and never think about it again
Skip us if…
- You spend less than $500/month on paid ads (browser pixel is fine)
- You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
- You need attribution modeling — we fix the data foundation, not multi-touch reports
- You want a 6-month enterprise consulting engagement (we ship in 4 days)
- You expect us to manage your ad accounts (we don’t — that’s a different service)
If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.
What working looks like
The distinct_id on every order
Server-sideCaptured before the conversion and stored where it survives.
Conversions arriving in Mixpanel
8+ EMQThe event lands on the user profile and becomes available in funnels, retention and cohort analysis.
Reconciled against the source
DedupedZonos's own records are the reference, not either dashboard.
What gets built
Identifier capture into Zonos
Capture on landing and record the duty component separately on the order so it can be excluded from value.
Event source: the order record with the Zonos duty breakdown
Send orders at merchandise value, excluding prepaid duties and taxes.
Dispatch to Mixpanel
The Mixpanel ingestion API, posted server-side from your backend with the distinct_id and event properties.
Reversals where they exist
Returns reverse the merchandise value; recovering duty is a separate and often unsuccessful process.
Pick the package that fits your ad spend
Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.
Browser-side starter
Wires the join and verifies it on a live conversion. Honest about its ceiling where the source can only be read from the browser.
- The join built and tested end to end
- Verified on a real conversion
- Reconciled against the source's own records
- Written handover
1st-party server-side
Save $18K–$120K over 5 years vs Triple Whale / Hyros
The join built server-side from the source's own records, so it does not depend on a browser being present when the conversion happens.
- Events sourced from the system of record, not the browser
- Identifier captured and persisted end to end
- Deduplicated at the destination
- Reversals wired where the source supports them
- 95%+ accuracy guaranteed in writing
Full 1st-party stack
Every destination fed from one place, plus monitoring so a broken join surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- All paid destinations from one container
- CRM and offline loop
- Refunds and cancellations reversed everywhere
- Monitoring per destination
Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.
How it works
Built in 2–4 days. Accurate data within 7.
We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.
Kickoff + audit
30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.
Build the stack
Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.
QA + go-live
Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.
Verify accuracy
Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.
Got questions?
The honestanswers.
No buzzwords, no upsell. If we don’t know, we say so.
01Why aren't my Zonos conversions showing in Mixpanel?
Almost always because the distinct_id never reached the Zonos landed-cost order. Landed-cost calculation runs at checkout and can change the displayed total after the identifier was captured. Measure coverage before debugging the dispatch.
02What identifier does Mixpanel need?
Mixpanel identifies people by distinct_id, which starts as an anonymous device value and should be aliased to your own user ID at signup. Getting that alias wrong is the single most common Mixpanel implementation failure: the anonymous pre-signup activity and the identified user become two separate people, and every funnel that crosses signup is broken.
03Where should the event come from?
The order record with the Zonos duty breakdown. Send orders at merchandise value, excluding prepaid duties and taxes.
04How do I know it worked?
Mixpanel shows events in the live view within moments. Check that the distinct_id matches the signed-in user rather than a lingering anonymous ID, because that is the failure that quietly breaks every cross-signup funnel.
Still have questions?Book a 30-min call— bring them all.
The call
What happens on your free 30-min call
No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourZonos → Mixpanel setup — we’ll work through it together.
Min 1–5
We get the lay of your store
What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.
Min 5–15
We audit your tracking live
Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.
Min 15–25
We map a fix
What needs rebuilding, what stays. The exact Zonos → Mixpanel setup we'd ship and what it would recover for you.
Min 25–30
Decide. Or don’t.
If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.
Get Zonos and Mixpanel joined properly
Book a free 30-minute call. We measure your identifier coverage live on your own account, and you leave with a written plan — including the option that you don't need us.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
