Data, reconciliation & reportingClient work
Tracking Watch: a daily read-only reconciliation against your own orders, an hourly watcher for tags and consent, and alerts the day something breaks.
Sounds familiar?
How I solve it
I build Tracking Watch: a daily, read-only reconciliation of GA4, Google Ads and your other platforms against your own orders and records, an hourly watcher that alerts when a new conversion tag deploys or a consent setting changes, and a live report you can read. It fails visibly instead of quietly, and where I host the watch the alerts come to you, not to your client. This is the monitoring layer around a measurement setup, not a replacement for one.
The process
6 steps. Scope and a fixed price are agreed before the first one.
The conversions that matter, and the orders or records they must match.
A read-only job runs the last 14 days with per-event cutover timestamps and commits a snapshot each day.
A watcher checks the live storefront for a new conversion label going live, tracks the consent-mode passthrough value and alerts on a change.
Detectors flag a dead connection, a dark store and a stalled delivery, and raise an alert instead of waiting for month end.
A live read and a monthly reconciled table: what was delivered, what was accepted, what drifted.
Each mismatch is labelled tracking loss or attribution modelling, with the evidence.
Handover
Built with
Proof
Client work Done for real clients. Client details are anonymised.
Before → after
On a marketplace’s server-side sign-up events, the share whose session could be attached rose from 48–58% to 85% after the identifier fix, and 120 of 120 transaction ids joined in the reconciliation. Google Ads backfills conversions for about nine days, so the latest week always reads low until the reconciliation accounts for it — the kind of drift a daily watch catches on the day. Read in September 2026.
UK online marketplace (Shopify Plus)
120/120
Google Ads counted about 2.9 conversions for every real submission; 120 of 120 transaction ids matched after the event contract; server sign-up session attach 48–58% → 85%; a daily reconciliation runs against the marketplace's own records.
Read the case: 2.9 Conversions per Real Submission: An Event Contract for a MarketplaceEU premium fashion brand, multi-currency
37/37
37 of 37 orders delivered to Meta once, matching amount and currency across 9 presentment currencies; Purchase EMQ 7.7 → 8.1; a host cron watches Google upload freshness with alerts.
Read the case: Three Tools, Three Answers: Reconciling Triple Whale, Meta and Google for a Multi-Currency StoreFixel Pixel
detectors for a dead connection, a dark store and a stalled delivery, with incidents and alerts; one release to 61 store apps on 2026-09-26.
His setup with Google Data Studio was absolutely awesome and lets us track all the events in an easy to read format where we can make determinations that matter.
What you can look at
A redrawn reconciliation view — daily delivered-versus-real orders, with cutover markers — plus a redacted alert message on synthetic data. The view and alert are rebuilt for this page; the figures below are live reads.
Client details anonymised. Figures read from live platform APIs in August–September 2026. I am the founder of Fixel Pixel, the pipeline some of this runs on, named as disclosure.
Price and timeline
Tracking Watch is a Technical Partnership at USD 1,000 per month: 8 engineering hours in an agreed area, one active task, with the daily reconciliation, the hourly watcher, the alerts and the live report. If you would rather have managed server-side tracking hosted and watched per store, that is from USD 149 per store per month on top of setup. A one-store, one-off reconciliation is a Tracking Health Check at USD 395. Discussing the task is free.
QuoteFixed before work starts
A note from Daniilbefore you decide
If you already check your numbers every morning, your stack is stable, and a break is caught by a human the same day, a watch adds cost you don’t need — I’ll say so. And if all you need is a one-off answer about which number is right, a single reconciliation (Health Check) is cheaper than a monthly watch. If the entire gap turns out to be attribution windows and view-through, the watch will show you that plainly — that is modelling, not lost tracking.
— Daniil
Questions
Three things: a daily reconciliation against your orders, an hourly watcher for new conversion tags and consent changes, and detectors for a dead connection, a dark store and a stalled delivery.
Yes. The reconciliation and the watcher read your platforms; they do not change your setup.
To you. When I run the desk, alerts are routed to the partner, never to the end client.
Hourly for a tag or consent change, daily for a reconciliation drift. Both run automatically once set up.
Then the watch says so and shows why — widening an attribution window inflates a count without any change in tracking.
The first answer is free, within one working day. Or write directly: next@taskfordaniel.com
