Server-side tracking for BigCommerce
BigCommerce exposes order webhooks and a solid API, which is everything a container needs. Sourcing purchase from the order webhook removes the dependency on the confirmation page and gives you one authoritative event to deduplicate on, which the native path cannot offer.
Free30 minutesNo obligation
BigCommerce server-side · what breaks
What goes wrong on BigCommerce
- 01
Purchase count higher than order count
The native integration and a Script Manager pixel both sending.
- 02
Forgotten Script Manager entries
Tags added months ago still firing, unaudited.
- 03
Low match quality from the native path
Thin parameter coverage caps it regardless of your data.
- 04
Refunds never reversed
Not by the native path, and not by most app integrations.
BigCommerce server-side · the fix
What changes — BigCommerce server-side
One conversion per order
Deduplicated on the BigCommerce order ID.
Match quality at 8 or above
From customer data on the order record.
Refunds reversed
So revenue can fall as well as rise.
BigCommerce server-side · architecture
What BigCommerce exposes to a server container
The webhook is the thing worth having here, because it's the only path that gives you deduplication control.
- 1
Purchase from the order webhook
Independent of the confirmation page.
- 2
Order ID as the deduplication key
Available to both paths identically.
- 3
Customer data from the order record
Normalized then hashed, which the native path can't do as well.
- 4
Native connections retired after verification
Not before — run in parallel and confirm deduplication first.
- 5
Refunds wired from the refund webhook
The gap the native path leaves.
BigCommerce server-side · diagnose
Where BigCommerce 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 orders to platform purchases on order ID
For a closed week.
- 02
Read the Deduplicated indicator
Its absence with two live paths is the diagnosis.
- 03
List every Script Manager entry
Including ones nobody recognises.
- 04
Check match quality per event
Purchase specifically.
- 05
Test a refund
It almost never reverses.
BigCommerce server-side · prove
The QA evidence — BigCommerce server-side
Run on BigCommerce specifically, on a live conversion rather than in preview mode.
Source of truth
your BigCommerce order records
- Only one system confirmed sending purchase, on a live order.
- Order ID present as the deduplication key at every destination.
- Purchase count within a few percent of BigCommerce orders for a closed week.
- Match quality at 8 or above on Purchase.
- A real refund tested 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.
BigCommerce server-side · free audit
What we check in the free audit
- Compare orders to platform purchases on order ID
- Read the Deduplicated indicator
- List every Script Manager entry
- Check match quality per event
- Test a refund
Checked against
your BigCommerce order records
Free30 minutesNo obligation
BigCommerce server-side · when not to buy
When you don't need this on BigCommerce
Worth reading before you buy anything, from us or anyone.
- If you're a smaller store using only the native connections and your counts reconcile, that's a legitimate setup and you don't need a container.
- The native integrations are free. The three things that justify leaving them are deduplication control, refund handling and richer customer parameters. If none apply, stay.
- Adding a container without removing the native connection is worse than either alone. If you can't complete the migration, don't start it.
- Reconcile a closed week on order ID first — it's an hour and it tells you whether there's a problem.
BigCommerce server-side · what we deliver
What the server-side build gives you on BigCommerce
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from BigCommerce orders
The order webhook, carrying order ID, value, currency and customer data with no browser dependency.
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 BigCommerce order records. 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
BigCommerce server-side questions, answered
Yes — order webhooks and a solid API give a container everything it needs.
Only after running in parallel and verifying deduplication. Removing it first loses events; leaving it forever double-counts.
The order record, normalized then hashed at the container. That's the main reason match quality improves.
For browser-side funnel events, yes. Audit it — old entries firing silently is the norm.
Free · 30 min
Move BigCommerce events off the browser
WhatsAppFree30 minutesNo obligation
