Skip to content

Managed server-side trackingClient work

Meta and Google Miss Orders Shopify Records: Managed Server-Side Tracking With a Receipt per Event

Managed server-side tracking on my own pipeline: every event with a delivery receipt, reconciled order by order against Shopify.

For
Shopify DTC stores that advertise
Checked

Sounds familiar?

Tick what applies to you

The situation Managed server-side tracking
Why do Meta and Google report fewer orders than Shopify shows?

Tick the lines that describe your case.

Describe my task

How I solve it

What I build

I build server-side order capture and run it for you, or install it where you own it. A storefront pixel collects the browser leg. A backend validates the events, deduplicates them and delivers the server leg from one mapping that shares a single event_id, so the platform counts each order once. Delivery is reconciled against Shopify orders, and every dispatched event leaves a delivery receipt you can read.

This runs on Fixel Pixel, the pipeline I built and operate. It has seven destination adapters. Live delivery is confirmed for Meta, GA4, Google Ads and Pinterest; TikTok, Snapchat and Klaviyo are wired the same way.

The process

How it works

6 steps. Scope and a fixed price are agreed before the first one.

  1. Connect the store

    A Shopify web pixel plus the order webhook, with a consent gate in front of the browser leg. Your theme is not rewritten to make this work.

  2. One mapping

    Browser and server legs are generated from one event mapping and share one event_id, so dedup is structural, not a hopeful setting.

  3. Deliver

    Each event is sent to the destinations you run — Meta CAPI, GA4 Measurement Protocol, Google Ads, Pinterest, TikTok, Snapchat, Klaviyo — and each dispatch produces a result you can look up.

  4. Reconcile

    Delivered events are matched back to real Shopify orders: did every order arrive once, with the right value and the right currency?

  5. Watch

    Detectors flag a dead connection, a dark store and a stalled delivery, and raise an alert instead of waiting for the month to end.

  6. Report

    A monthly read: what was delivered, what was accepted, what was skipped and why.

Handover

What you get

  • A receipt per event: dispatched, accepted, retried or skipped — not a monthly summary.
  • One event per order: the browser and server legs carry the same event_id, so duplicates stop.
  • An order-level reconciliation you can hand to a finance lead.
  • A choice of where it runs: hosted on your own infrastructure (your Cloudflare Worker, Stape or GCP) so you own everything, or hosted and watched by me.
  • A named contact and a written change record for anything that touches your store.

Built with

  • Shopify Web Pixel and order webhooks
  • Fastify ingest
  • PostgreSQL and Redis
  • Meta CAPI
  • GA4 Measurement Protocol
  • Google Ads
  • Pinterest
  • TikTok
  • Snapchat
  • Klaviyo
  • ClickHouse for spend
  • COGS and ROAS views
  • Cloudflare

Proof

Done before, with dates and numbers

Client work Done for real clients. Client details are anonymised.

Before → after

One store’s click signal on InitiateCheckout carried fbc on 11.8% of events before the switch and 78.9% after; browser fbp on PageView went from 0.06% to 65.9%. Across the same rollout, 37 of 37 orders reached Meta exactly once with the matching amount and currency across nine presentment currencies — read from the live Meta API on 2026-09-29.

  • EU premium fashion brand, multi-currency

    active client since Sep 2026

    37/37

    37 of 37 orders delivered to Meta once, matching amount and currency across 9 currencies; Purchase EMQ 7.7 → 8.1.

  • Herbal-tea brand, Greece

    delivered Jul 2026

    29% to 80%

    GA4 conversion coverage against real orders 29% → 80%, with about 85% of orders captured server-side.

  • Merchants on my pipeline, EU and US

    one store: 1,202 purchase events delivered, 100% accepted, 0 errors, 93.6% carrying a click id.

Rated 5 out of 5 on Upwork.

...rebuilt Meta tracking for my funnel with browser + server deduplication, set up the tracking Worker to run on my own Cloudfare account (for full ownership)...

Eve S., Balance Works SL Upwork · 2026

What you can look at

A redrawn flow diagram on a synthetic store: order → validate → dedup → seven adapters → reconciler, with a redacted excerpt of a delivery receipt and the one-store scorecard below. The diagram and receipt are synthetic and rebuilt for this page; the numbers come from live platform reads.

I am the founder of Fixel Pixel, the pipeline this managed service runs on — a recommendation, not the only option. Client details anonymised. Figures read from live platform APIs in September 2026.

Price and timeline

What it costs and how it runs

Setup is a bounded build with a fixed quote before it starts — a Focused Fix, from USD 450. After that you choose:

  • Hosted on your own infrastructure — your Cloudflare Worker, Stape or GCP. You own everything; support comes by request through a Working Session (USD 195) or a Technical Partnership.
  • Hosted and watched by me — daily delivery control, alerts and a monthly report, from USD 149 per store per month.

If you want ongoing oversight beyond that, a Technical Partnership is USD 1,000 per month. Nothing here is a mandatory step before the other.

QuoteFixed before work starts

Price
Managed server-side tracking: setup from USD 450, then either hosted on your own infrastructure or hosted and watched by me from USD 149 per store per month; ongoing oversight as a Technical Partnership USD 1,000 per month.
Timeline
Setup is a bounded build with a fixed quote before it starts. The watch begins the day the first event lands with a receipt.
First step
Describe the task. I reply within one working day, free, and tell you which option fits — or that you can fix it yourself.
Describe a task like this

A note from Daniilbefore you decide

When you don’t need this

If Meta’s one-click Conversions API and Shopify’s own GA4 channel already agree with your orders within the tolerance you can live with, I’ll say so — a managed pipeline adds work you don’t have. And if the gap is only attribution modelling (view-through and different attribution windows), no capture fix will change it; a reconciliation will show you that instead.

— Daniil

Questions

What people ask about this

How long until it is live?

The setup is a bounded build and gets a fixed quote before it starts; the watch begins the day the first event lands with a receipt.

Where does the server run?

Your choice. On your own Cloudflare Worker, Stape or GCP so you own it, or hosted and watched by me on my pipeline.

Do you touch my theme?

No rewrite. The storefront is connected through the supported pixel path and the order webhook.

What if Meta and Shopify still disagree afterwards?

Then we can tell you which of the two is losing data and which gap is modelling, because every event has a receipt and every order is reconciled.

Is this the same as a server-side GTM container?

It can deliver through one — a managed server-side GTM activation is part of the pipeline — but the difference is the receipt and the reconciliation, not the container itself.

More like this

All situations
Daniil Maximkin

Hi, I’m Daniil.

I work with you from defining the problem to implementation and handover. You talk to the person who does the work. I work in English and Russian.

My story My work

Have a task like this?

Describe your task

The first answer is free, within one working day. Or write directly: next@taskfordaniel.com