Services
Four named engagements, fixed scope
Most of what I am asked for is one of these four, or a sequence of them. Each is quoted as a fixed scope for a fixed fee after a call — no hourly billing, and no change order for something that was obviously part of the job.
Engagements
Four ways I get brought in
GA4 & server-side GTM
A data layer that is specified before it is built, a GA4 property that matches it, and server-side tagging so your conversions survive ad blockers, ITP and Consent Mode.
Tracking & tag audit
Every tag in the container checked against what actually fires on the live site — double-fires, dead pixels, deprecated tags, and vendor scripts nobody in the building put there.
Experimentation programs
Tests that are powered before they launch, instrumented so the result is trustworthy, and read out honestly — including the ones that lose, which is most of them.
Reporting & automation
The weekly deck built once and then never rebuilt: warehouse-backed dashboards, scheduled pipelines, and alerting that tells you when collection breaks.
How it runs
Find it, fix it, hand it over
Every engagement ends with documentation and a walkthrough. You should not need me on retainer to keep your own measurement working.
01
Audit what is actually there
I open the container, the property and the live site together. Not what the spec says is implemented — what fires, in what order, with what values, on the pages that matter. You get the findings whether or not we work together after that.
02
Fix the collection layer first
Data layer specified, events named consistently, server-side tagging where it earns its keep, consent handled properly. Reporting built on a broken collection layer is just a faster way to be wrong.
03
Hand it over documented
A tagging spec your next hire can read, dashboards owned by your team, and a recorded walkthrough. The measure of a good engagement is how little you need to call me afterwards.
Before you ask
Questions I get on the first call
What does an engagement cost?
It depends on the size of the estate and the state it is in, so I quote after a call rather than publishing a number that would be wrong for most people. What I will commit to on that call is a fixed scope and a fixed price — no hourly billing, and no change order for something that was obviously part of the job.
How long does a tracking audit take?
For a typical single-brand site, a working week from access to written findings. Large multi-brand estates or containers with heavy custom templating take longer, and I will tell you that before starting rather than halfway through.
Do we need server-side tagging?
Often, but not always, and I will say so when the answer is no. Server-side GTM earns its keep when you are losing conversions to ad blockers and ITP, when you need to enrich events with data the browser should not hold, or when you want one governed pipeline out to several vendors. If your real problem is a data layer nobody maintains, moving the same broken events to a server does not fix it — it just makes them harder to debug.
Will you work with our existing agency or dev team?
Yes, and it is usually the fastest route. I write the tagging spec, your developers implement the data layer, and I validate it in the container. That split keeps the work in your codebase and out of a black box only I can open.
What happens when the engagement ends?
You keep everything: the container, the documentation, the dashboards, and a recorded walkthrough. There is no proprietary layer to license and nothing that stops working if you stop paying me. Ongoing support is available, but it should be a choice rather than a dependency.
Can you sign an NDA?
Yes. Where a client’s name is under NDA, the case study on this site describes the work and abstracts the brand — it does not invent a substitute.
Next step
Tell me what you are trying to measure
A short call, no deck. Bring the question your data cannot currently answer and I will tell you straight whether it is a tracking problem, a modelling problem, or neither.