Find out your tracking broke in days, not at quarter end
Tracking is not a project that finishes. Platforms deprecate parameters, themes get updated, apps get installed, and setups drift — and the reason breaks go unnoticed for months is that a site with broken tracking looks completely normal. We reconcile against your own order records every month, watch for the anomalies that precede a full break, and review site releases before they ship.
Free30 minutesNo obligation
Monitoring · what breaks
Why breaks go unnoticed — Monitoring
- 01
A site with broken tracking looks fine
Nothing errors, nothing warns, and the pages all load.
- 02
Conversion drops read as seasonality
So the real cause goes unexamined for weeks.
- 03
Google's inactive label arrives 30 days late
By which point a month of bidding has run blind.
- 04
Nobody owns it between projects
So drift accumulates until something obvious breaks.
Monitoring · the fix
What you get out of it — Monitoring
Breaks caught in days
Before they become a quarter of misread reporting.
A trend line for your gap
Measured monthly, so drift is visible rather than discovered.
Releases reviewed before they ship
Which is far cheaper than fixing afterwards.
Someone accountable
The thing most setups actually lack.
Monitoring · architecture
Why the numbers were wrong before you got here — Monitoring
Worth understanding before buying anything, because it decides which tier you need — and for some readers the answer is that you don't need us yet.
- 1
The browser is the weakest link, and it is getting weaker on purpose
Every browser-side tag has to survive the page loading, the visitor staying, the script running and the request leaving. All four are now contested. The order in your database is certain; the browser event reporting it is not.
- 2
Safari caps the cookie your attribution depends on
Intelligent Tracking Prevention limits JavaScript-set cookies to seven days whatever expiry you set, so a customer who takes longer than a week to decide returns as a stranger. A cookie your own server writes in an HTTP response is not capped — the single largest practical difference between browser-side and first-party server-side.
- 3
Ad blockers remove the tag with no error
A blocked pixel does not warn anyone. The customer buys, the order lands, and no platform hears about it. First-party events from your own subdomain are not a third-party request and are not filtered the same way.
- 4
Consent is enforced by hope, not by architecture
Client-side consent means trusting each vendor script to honour a flag. A server container decides at the container: a denied destination receives nothing. That is a materially stronger position, and it also stops the over-blocking that discards data no law required losing.
- 5
Checkout can end where your tag isn't
Wallets and hosted payment pages can be abandoned after the money moves. Sending the purchase from the order record means it arrives whether or not anyone came back.
Monitoring · diagnose
How we scope tracking monitoring
Before quoting. Each step narrows what the work actually is, so the price reflects your account rather than an average.
- 01
Establish the baseline
Reconcile before changing anything.
- 02
Agree the source of truth in writing
Which prevents most of the arguments that follow.
- 03
Inventory every firing path and platform account
Including accounts from previous agencies still live.
- 04
Identify who owns what
Unclear ownership is the most common reason findings sit unfixed.
- 05
Wire release review into the deploy process
The cheapest prevention available.
Monitoring · prove
How the work gets proven — Monitoring
A dashboard turning green proves a dashboard turned green. These are what we hand over instead.
Source of truth
Monthly reconciliation against your backend or CRM
- The gap measured every month with the trend visible over time.
- Breaks found by us before they're noticed in reporting.
- Documentation current enough for another engineer to pick up.
- Someone on your team able to run the reconciliation without us.
- Open findings going down, not sideways.
- Reconciled over a fully closed window, matched on ID rather than on totals — totals hide equal and opposite errors.
- Payload evidence captured from real transactions, saved to your own records.
- The same reconciliation repeated 30 days later, because a setup that works once and drifts is the harder failure.
Monitoring · free audit
What we check in the free audit
- Establish the baseline
- Agree the source of truth in writing
- Inventory every firing path and platform account
- Identify who owns what
- Wire release review into the deploy process
Checked against
Monthly reconciliation against your backend or CRM
Free30 minutesNo obligation
Monitoring · when not to buy
When you shouldn't buy this — Monitoring
We would rather say it now than three weeks into an engagement.
- Your setup is stable, spend is flat and nothing about your site changes. An annual audit serves you better.
- You have a capable in-house analytics engineer. Then you need occasional review, not ongoing ownership.
- You're pre-launch. Build it correctly first; monitor afterwards if you need to.
- The retainer is a large share of your media budget. Put the money in media.
Monitoring · what we deliver
What's included in tracking monitoring
Monthly reconciliation
Backend orders against every platform, matched on ID, with the gap trended over time.
Weekly anomaly checks
Volume, value and match-quality shifts that precede a full break.
Platform change review
Deprecations and API changes, with what needs updating and what's safe to ignore.
Pre-release review
Tracking checked against site changes before they go live.
Break alerts
Raised to you with the likely cause, not just a red number.
Quarterly configuration review
Taxonomy, windows and documentation kept current.
Written guarantee
95%+ tracking accuracy
Measured against Monthly reconciliation against your backend or CRM. 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
The correct browser-side build, done properly and verified on a live transaction. Honest about its ceiling: it will not survive Safari's cookie cap, an ad blocker, or a checkout that ends somewhere your tag isn't. If you spend $1K+/month on paid media, start one tier up.
- Correct events, correct parameters, correct values
- Verified on a live transaction, not in preview
- Reconciled against your own order records
- Written handover you keep
1st-party server-side
Recommended$800One-time fee · most popular
The tier that changes the outcome rather than patching it. Your money events stop depending on the browser: they are sent from your order records through a first-party server container on your own subdomain, so iOS, ad blockers, consent banners and interrupted payment redirects can no longer take them away. Built in 2–4 days. You own the stack outright, with no monthly SaaS.
- First-party server container on your own subdomain
- Money events sent from your order records, not the browser
- Meta, Google, TikTok, Microsoft and LinkedIn all fed server-side
- Deduplicated on a shared event ID, verified at every destination
- First-party cookies beyond Safari's 7-day cap on JavaScript-set cookies
- 95%+ conversion accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel server-side, plus the offline loop that connects closed revenue back to the click. For advertisers whose spend makes an attribution leak more expensive than the build.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop, so closed revenue reaches bidding
- Refunds and cancellations reversed at every destination
- Klaviyo identity stitching, BigQuery and Looker Studio
- Monitoring, so the next break surfaces in days rather than a quarter
FAQ
Monitoring questions, answered
Weekly anomaly checks catch volume and value shifts within days. The monthly reconciliation catches slower drift that anomaly detection misses.
Read access to the ad accounts and analytics, plus a way to pull an order export. We don't need write access to monitor.
You get an alert with the likely cause and what it's costing. Fixing it is a separate conversation, and small fixes are usually included.
That's the goal. The method is documented specifically so your team can run it, and needing us less is the correct outcome.
WhatsApp