The problem
What usually brings people here
Describe the symptom in the client’s own words, not in analytics vocabulary — “the numbers in the ad platform and the numbers in finance do not match” rather than “attribution discrepancy”. Two or three paragraphs. Name the cost of leaving it alone.
The work
What I actually do
Name the stack explicitly — server-side GTM, GA4, BigQuery, whichever applies. Vague capability language is what this whole site is built against, and a technical buyer reads it as a tell.
- First concrete thing you do, in the order you do it.
- Second.
- Third.
What you get
Deliverables
- A written tagging specification your developers can implement from.
- The container built, versioned and annotated — not a pile of untitled tags.
- Validation evidence: what fires, where, with which values.
- A recorded handover walkthrough, kept by you.
Engagement
- Typical length
- 2–6 weeks
- Pricing
- Fixed scope, fixed fee — quoted after a call
- You provide
- Container and property access, one technical point of contact
- Works alongside
- Your existing dev team or agency
Evidence
What this looks like when it is done
A real screenshot belongs here — the container, the debug view, the dashboard. Brief §3 makes artifacts first-class content; a service page with no artifact is the vague capability claim it was written to avoid. Never a stock UI mockup and never a fabricated screenshot.
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.