The tracking function your agency doesn't have to hire
You keep the client relationship and the media strategy. We do the tracking work behind you — audits you can use to win accounts, server-side builds, offline conversion loops — to one repeatable standard, so your team learns a single system rather than inheriting a different setup per client. White label if you want it, or we join client calls as your tracking engineer. Your call, per account.
Free30 minutesNo obligation
For agencies · what breaks
Why agencies bring us in
- 01
Client data nobody can defend in a renewal
Reported numbers disagreeing with the client's own books and no explanation available.
- 02
Inherited accounts with unknown tracking
Built by whoever came before, undocumented.
- 03
Tracking work you can't staff
Not enough volume to justify a hire, too much to keep absorbing.
- 04
A different setup on every client
So nothing your team learns transfers.
For agencies · the fix
What you get out of it — For agencies
One standard across every account
Same taxonomy, same reconciliation, same evidence.
Findings you can sell with
Pre-pitch audits that win accounts.
Documentation your team owns
So account managers answer client questions without routing to us.
A defensible position in renewals
A reconciliation you can put in front of a client.
For agencies · architecture
Why the numbers were wrong before you got here — For agencies
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.
For agencies · diagnose
How we scope white-label tracking — For agencies
Before quoting. Each step narrows what the work actually is, so the price reflects your account rather than an average.
- 01
Establish access and who owns what
Which changes need a developer, which need platform access, which we can make.
- 02
Reconcile before changing anything
So there's a baseline you can show the client.
- 03
Inventory every firing path
Including the previous agency's, which is usually still live.
- 04
Identify what needs the client's developer
We write the spec; someone with commit access applies it.
- 05
Agree white label or named
Per account, before anything goes out.
For agencies · prove
How the work gets proven — For agencies
A dashboard turning green proves a dashboard turned green. These are what we hand over instead.
Source of truth
The client's backend order or CRM records
- A reconciliation you can put in front of a client, in a format that survives scrutiny.
- Firing-path inventory, so a future handover doesn't create a duplicate.
- Payload evidence from real transactions.
- Expected behaviour separated from faults — the part that defuses most client escalations.
- Anything undetermined listed as undetermined.
- 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.
For agencies · free audit
What we check in the free audit
- Establish access and who owns what
- Reconcile before changing anything
- Inventory every firing path
- Identify what needs the client's developer
- Agree white label or named
Checked against
The client's backend order or CRM records
Free30 minutesNo obligation
For agencies · when not to buy
When you shouldn't buy this — For agencies
We would rather say it now than three weeks into an engagement.
- You already have an analytics engineer with capacity. Use them; we'd only add a handoff.
- The account spends too little to justify the work. We'll say so during scoping rather than after invoicing.
- The client won't grant the access required. Server-side and offline work needs real access; without it we'd be guessing.
- The account's problem is media performance, not measurement. We'll tell you if that's what the audit finds.
For agencies · what we deliver
What's included in white-label tracking — For agencies
Pre-pitch audits
Three to five days, findings you can use to win the account.
Onboarding builds
Full tracking stack with validation evidence, one to two weeks.
Specific fixes
CAPI deduplication, consent ordering, offline loops, scoped individually.
White-label deliverables
Your branding, our work, and we stay invisible if you prefer.
Per-account documentation
Taxonomy, firing-path inventory and reconciliation method, in the same format every time.
Optional monitoring
Monthly reconciliation per account with breaks flagged to you.
Written guarantee
95%+ tracking accuracy
Measured against The client's 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
For agencies questions, answered
Only if you want us to. We can stay entirely invisible with your branding on the deliverables, or join calls as your tracking engineer. It's per account.
Then that's the finding, and you get an account you can defend rather than a fix nobody needed. We won't manufacture findings to justify a fee.
Yes. Through your agency accounts or direct from the client with you copied — whichever fits how you work.
Pre-pitch audit three to five days. Onboarding build one to two weeks. Specific fixes usually under a week.
Free · 30 min
Add a tracking team without hiring one
WhatsAppFree30 minutesNo obligation
