Skip to main content
Shopify Plus server-sidePlatform solution

Server-side tracking for Shopify Plus

Plus is the strongest case for a server container in the Shopify family, because the things Plus adds — B2B, multi-store, wholesale, custom checkout logic — are precisely the things a templated tracking app handles badly. The orders webhook still carries the authoritative money event, and a container is where multi-store order IDs get namespaced before they collide.

Free30 minutesNo obligation

Shopify Plus server-side · what breaks

What goes wrong on Shopify Plus

  1. 01

    Multi-store order IDs colliding

    Two storefronts each starting order numbers at 1001 will deduplicate against each other and silently drop conversions.

  2. 02

    B2B orders distorting value-based bidding

    A wholesale order many times your retail average teaches bidding the wrong thing unless it's separated.

  3. 03

    Checkout extensibility apps adding paths

    Each one can send, and on Plus there are usually several.

  4. 04

    Wallet payments skipping the confirmation

    Same as standard Shopify, and at Plus volume the absolute number is larger.

Shopify Plus server-side · the fix

What changes — Shopify Plus server-side

  • Order IDs namespaced per store

    So deduplication works across the estate rather than against it.

  • B2B and retail separated

    Two economics, two conversion definitions.

  • One path per event per store

    Verified, after counting them all.

Shopify Plus server-side · architecture

What Shopify Plus exposes to a server container

A container is where a multi-store Plus estate becomes manageable rather than four separate tracking setups drifting apart.

  1. 1

    One container, several storefronts

    Each store's webhook feeding the same container, with the store identity carried through.

  2. 2

    Namespaced order IDs

    Prefixed per store, so deduplication keys are unique across the estate.

  3. 3

    B2B separated at the container

    Wholesale orders routed to their own conversion action rather than blended into retail.

  4. 4

    Customer data from the order

    On B2B orders, decide deliberately whose data is used for matching — the buyer or the account.

  5. 5

    Refunds per store

    Wired individually, because they are separate webhook subscriptions.

Shopify Plus server-side · diagnose

Where Shopify Plus 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.

  1. 01

    Check for order ID collisions across stores

    Two storefronts numbering from the same start is a silent conversion loss.

  2. 02

    Segment the gap by storefront

    An estate-level reconciliation hides which store is broken.

  3. 03

    List apps per store

    They differ between storefronts more often than anyone expects.

  4. 04

    Separate B2B from retail in the comparison

    Wholesale volume distorts the ratio.

  5. 05

    Test a wallet payment on each storefront

    Checkout configuration can differ per store.

Shopify Plus server-side · prove

The QA evidence — Shopify Plus server-side

Run on Shopify Plus specifically, on a live conversion rather than in preview mode.

Source of truth

your Shopify Plus order records, web orders only

  • Order ID uniqueness verified across every storefront.
  • A live order placed on each store and the payload read.
  • B2B and retail confirmed arriving as separate conversions.
  • Purchase count reconciled per storefront, not just in aggregate.
  • A real refund tested on at least one store per configuration.
  • Reconciled over a fully closed window, matched per record rather than on totals.
  • Re-checked 30 days later, and after any platform update.

Shopify Plus server-side · free audit

What we check in the free audit

  • Check for order ID collisions across stores
  • Segment the gap by storefront
  • List apps per store
  • Separate B2B from retail in the comparison
  • Test a wallet payment on each storefront

Checked against

your Shopify Plus order records, web orders only

Get my free conversion tracking audit

Free30 minutesNo obligation

Shopify Plus server-side · when not to buy

When you don't need this on Shopify Plus

Worth reading before you buy anything, from us or anyone.

  • If you run a single Plus storefront with no B2B and your numbers reconcile, you have standard Shopify's problem set and standard Shopify's answers. Nothing here is Plus-specific enough to need us.
  • If wholesale is a tiny share of revenue, separating it may cost more attention than it returns. Measure the share first.
  • Multi-store namespacing only matters if order sequences actually overlap. Check whether they do before treating it as a problem.
  • As always: reconcile a closed week per storefront first. If every store comes out clean, don't buy anything.

Shopify Plus server-side · what we deliver

What the server-side build gives you on Shopify Plus

  • Container on your own subdomain

    Your domain, your certificate, hosting in an account you control.

  • Money events from Shopify Plus orders

    orders/create per storefront, namespaced so order IDs stay unique across the estate.

  • 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 Plus order records, web orders only. Miss it and we keep working at no cost.

Get my free conversion tracking audit

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
Fix what I have

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
Rebuild it server-side

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
Get the full stack

FAQ

Shopify Plus server-side questions, answered

Yes, and it's the main reason a Plus estate benefits from one. Carry the store identity through and namespace the order IDs.

Free · 30 min

Move Shopify Plus events off the browser

Free30 minutesNo obligation