Server-side tracking for Shopify Hydrogen
Hydrogen runs on your own server infrastructure, usually Oxygen or a Node host, which makes a server container a natural neighbour rather than a bolt-on. The money event still comes from the orders/create webhook — that doesn't change with headless — but the storefront events can be emitted server-side from your own routes, which removes a whole class of client-side fragility.
Free30 minutesNo obligation
Shopify Hydrogen server-side · what breaks
What goes wrong on Shopify Hydrogen
- 01
Route changes firing no events
A client-side navigation isn't a page load, so anything bound to one silently never runs.
- 02
Checkout on a different origin
The customer leaves your storefront for Shopify's checkout, and the session splits unless identifiers are carried.
- 03
Hydration timing
Events fired before hydration completes can dispatch with empty values.
- 04
Nothing is automatic
No theme, no app defaults. Every event exists because someone wrote it.
Shopify Hydrogen server-side · the fix
What changes — Shopify Hydrogen server-side
Route changes emitting proper events
Bound to the router, not to page load.
Identifiers surviving the checkout hop
Carried into Shopify checkout via cart attributes.
Purchase from the order webhook
Independent of whether the customer returned to your storefront.
Shopify Hydrogen server-side · architecture
What Shopify Hydrogen exposes to a server container
Headless and server-side pair naturally, because you already run infrastructure.
- 1
Storefront events emitted server-side
From your Hydrogen routes, which removes client-side fragility entirely.
- 2
Purchase from orders/create
The checkout being someone else's origin makes this the only reliable source.
- 3
Order ID as the deduplication key
Same as any Shopify store.
- 4
Click IDs via cart attributes
Captured in your code, carried across the origin boundary, present on the order.
- 5
Container alongside your existing infrastructure
You already deploy a Node application; this is another one.
Shopify Hydrogen server-side · diagnose
Where Shopify Hydrogen 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
Navigate between routes and watch for events
If nothing fires on a client-side transition, that's the fault.
- 02
Check whether events fire before hydration
Empty values on the first event is the signature.
- 03
Walk the checkout hop
Confirm cart attributes carry the identifiers across.
- 04
Confirm the orders webhook is subscribed
Headless builds sometimes never set it up.
- 05
Match a closed week on order ID
Shopify web orders against each platform.
Shopify Hydrogen server-side · prove
The QA evidence — Shopify Hydrogen server-side
Run on Shopify Hydrogen specifically, on a live conversion rather than in preview mode.
Source of truth
your Shopify order records, web orders only
- Client-side route changes confirmed emitting events on a real navigation.
- Click identifiers confirmed present on the order via cart attributes.
- Purchase confirmed arriving from the webhook with the order ID.
- Purchase count within a few percent of Shopify web orders for a closed week.
- 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.
Shopify Hydrogen server-side · free audit
What we check in the free audit
- Navigate between routes and watch for events
- Check whether events fire before hydration
- Walk the checkout hop
- Confirm the orders webhook is subscribed
- Match a closed week on order ID
Checked against
your Shopify order records, web orders only
Free30 minutesNo obligation
Shopify Hydrogen server-side · when not to buy
When you don't need this on Shopify Hydrogen
Worth reading before you buy anything, from us or anyone.
- If your Hydrogen storefront already emits route-change events correctly and your purchase count reconciles, the headless-specific problems don't apply to you.
- Your developers can do most of this — it's their codebase and the Shopify webhook is well documented. Hand them this page.
- Server-side is a smaller step on Hydrogen than elsewhere because you already run infrastructure, which cuts both ways: it's cheaper to add and easier to do yourself.
- Reconcile a closed week on order ID before deciding anything.
Shopify Hydrogen server-side · what we deliver
What the server-side build gives you on Shopify Hydrogen
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from Shopify orders
orders/create, unchanged by going headless — the checkout is still Shopify's and the webhook is still authoritative.
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 Shopify order records, web orders only. 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
Shopify Hydrogen server-side questions, answered
Somewhat — you already run infrastructure and can emit events server-side from your routes, which removes client-side fragility.
The orders/create webhook, same as any Shopify store. Going headless doesn't change who owns the checkout.
Yes, and it's one of the genuine advantages of headless. Fewer things depend on the client running correctly.
For checkout-stage events, yes. Your code can't see inside Shopify's checkout.
Free · 30 min
Move Shopify Hydrogen events off the browser
WhatsAppFree30 minutesNo obligation
