Decide which number answers which question, once
Most measurement arguments aren't technical — they're definitional. Four systems report four numbers, nobody agreed which one governs which decision, and budget conversations stall on whose figure is right. This engagement is mostly not implementation work: it's agreeing a source of truth, writing down what each number is for, and building the one reconciliation that keeps everyone honest.
Free30 minutesNo obligation
Measurement strategy · what breaks
Symptoms of a missing measurement strategy
- 01
Budget decisions stalling on whose number is right
The real cost of an unresolved definition.
- 02
The same question answered differently each month
Because nothing is written down.
- 03
Platform revenue summed into a total nobody can bank
The most common reporting mistake we see.
- 04
Dashboards nobody uses to decide anything
Built, maintained, and ignored.
Measurement strategy · the fix
What you get out of it — Measurement strategy
An agreed source of truth
In writing, before the arguments.
A one-page reporting definition
Which number answers which question. Usually the actual deliverable.
A reconciliation your team can run
So the agreement stays honest over time.
Decisions that get made
Which is the entire point of measuring anything.
Measurement strategy · architecture
Why the numbers were wrong before you got here — Measurement strategy
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.
Measurement strategy · diagnose
How we scope measurement strategy
Before quoting. Each step narrows what the work actually is, so the price reflects your account rather than an average.
- 01
Identify the decisions the numbers support
Reporting with no decision attached can go.
- 02
Agree the source of truth
Which prevents most future arguments.
- 03
Document each platform's model and window
Most disagreement is explained here.
- 04
Establish the reconciliation method
Window, matching key, procedure.
- 05
Find the decisions being made on bad numbers
Usually the highest-value finding in the whole engagement.
Measurement strategy · prove
How the work gets proven — Measurement strategy
A dashboard turning green proves a dashboard turned green. These are what we hand over instead.
Source of truth
Your backend order or CRM records
- A written statement of which number answers which question, agreed by the people who use them.
- The reconciliation method documented and run once with your team watching.
- Attribution models and windows documented per platform.
- At least one piece of reporting retired because no decision depended on it.
- 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.
Measurement strategy · free audit
What we check in the free audit
- Identify the decisions the numbers support
- Agree the source of truth
- Document each platform's model and window
- Establish the reconciliation method
- Find the decisions being made on bad numbers
Checked against
Your backend order or CRM records
Free30 minutesNo obligation
Measurement strategy · when not to buy
When you shouldn't buy this — Measurement strategy
We would rather say it now than three weeks into an engagement.
- Your team already agrees on a source of truth and reconciles regularly. That agreement is the strategy.
- You run one channel and make decisions from its own numbers. There's little to reconcile.
- Your tracking isn't correct yet. Strategy on top of wrong data produces confident wrong decisions — fix the data first.
- Nobody will maintain the practice afterwards. A documented method nobody runs is worth nothing.
Measurement strategy · what we deliver
What's included in measurement strategy
Source of truth agreed
Backend orders or CRM closed-won, documented before any technical work.
Reporting definitions
Each number, what it answers, what it doesn't, and its known differences.
Attribution windows documented
Per platform, so the expected disagreement is known in advance.
The reconciliation method
Window, matching key and procedure, written so anyone can run it.
Decision map
Which metric governs which decision, so reporting has a purpose.
Handover session
With whoever actually uses the numbers, not just whoever owns the tools.
Written guarantee
95%+ tracking accuracy
Measured against Your backend order or CRM records. 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
Measurement strategy questions, answered
Largely, yes, and the technical work is the smaller part. The expensive problem in most accounts is a definitional disagreement, not a broken tag.
We can agree definitions, but strategy on unreliable data produces confident wrong decisions. Usually the reconciliation exposes what needs fixing first.
Whoever uses the numbers to decide something — media buyers, finance, and whoever owns the budget. Tool owners are secondary.
Usually one page: which number answers which question, with the known differences stated. It sounds slight and it settles most recurring arguments.
More on Measurement strategy
Free · 30 min
Settle which number governs which decision
WhatsAppFree30 minutesNo obligation
