Server-side tracking for Magento 2
Magento is your own infrastructure, so a server container is a natural fit and the order-placed observer gives you an authoritative money event. It also solves the cache problem structurally: an event fired from the order can't be served from a cached page, because it never touches one.
Free30 minutesNo obligation
Magento 2 server-side · what breaks
What goes wrong on Magento 2
- 01
Identical values across different orders
Full-page cache serving stored HTML with a baked-in data layer.
- 02
Some payment methods tracked, others not
Offsite gateways, iframes and redirects each return the customer differently.
- 03
Store views reporting inconsistently
Currency, locale and tag configuration can all differ per view and diverge over time.
- 04
Headless frontends where the confirmation isn't Magento
A PWA or decoupled storefront changes where the event can fire at all.
Magento 2 server-side · the fix
What changes — Magento 2 server-side
Purchase sourced from the order record
Immune to caching by construction.
Every payment return path covered
Tested individually, because they genuinely differ.
Consistent behaviour across store views
One configuration, verified per view.
Magento 2 server-side · architecture
What Magento 2 exposes to a server container
On Magento a container isn't just about durability — it's how you get out of the caching problem entirely.
- 1
Purchase from the order observer
Fired from the order record, so caching is irrelevant to it.
- 2
Increment ID as the deduplication key
Magento's own order reference, unique and stable.
- 3
Store view carried through
So a per-view fault is visible rather than averaged away.
- 4
Customer data from the order
Not from a cached page that may not be this customer's.
- 5
Credit memos wired as reversals
The refund equivalent on Magento.
Magento 2 server-side · diagnose
Where Magento 2 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
Compare two different orders' data layer values
Identical means cache, and that's the whole diagnosis.
- 02
Segment the gap by payment method
One method dominating names the cause.
- 03
Segment by store view
Configuration drift is common and invisible in aggregate.
- 04
Check which blocks are cached
And which are private content.
- 05
Match a closed week on increment ID
Against each platform's purchase count.
Magento 2 server-side · prove
The QA evidence — Magento 2 server-side
Run on Magento 2 specifically, on a live conversion rather than in preview mode.
Source of truth
your Magento order records, matched on increment ID
- Two different orders confirmed carrying different values, not cached ones.
- Every payment method's return path tested with a real order.
- Each store view verified individually.
- Purchase count reconciled on increment ID for a closed week.
- A credit memo issued and confirmed reversing.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Magento 2 server-side · free audit
What we check in the free audit
- Compare two different orders' data layer values
- Segment the gap by payment method
- Segment by store view
- Check which blocks are cached
- Match a closed week on increment ID
Checked against
your Magento order records, matched on increment ID
Free30 minutesNo obligation
Magento 2 server-side · when not to buy
When you don't need this on Magento 2
Worth reading before you buy anything, from us or anyone.
- If two consecutive orders produce different, correct payloads and your counts reconcile, you don't have the Magento cache problem and this page isn't describing your site.
- A single store view with one payment method is a much simpler situation than this page assumes. Reconcile first.
- Moving purchase to the order observer is standard Magento development. If you have a Magento developer, they can do it.
- Headless Magento makes server-side more obviously necessary, not more expensive — the same observer is the source either way.
Magento 2 server-side · what we deliver
What the server-side build gives you on Magento 2
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from Magento orders
The order-placed observer, which fires from the order record and is unaffected by full-page cache.
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 Magento order records, matched on increment ID. 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
Magento 2 server-side questions, answered
It solves the cache problem structurally rather than working around it, which is a stronger argument than on most platforms.
The order-placed observer. It runs once per order, from the order record, with no page involved.
The increment ID — Magento's own order reference, unique and stable.
You already run infrastructure, so yes, and it should be in your own account rather than an agency's.
Free · 30 min
Move Magento 2 events off the browser
WhatsAppFree30 minutesNo obligation
