Writing the measurement plan is the hard part. Knowing whether you wrote it correctly is the expensive part.
Most tracking problems are not bugs. They are decisions nobody wrote down thought the process: a last minute value that quietly includes tax, an item dimension registered past GA4’s cap, or a tag that keeps firing after a visitor declines consent. None are technically errors but they show up a quarter later as a bug a team now has to deal with in their reports.
We read your measurement plan against the same standards we hold our own builds to, and tell you where there are problems and what the level of effort and estimated cost to fix should be.
Who this is for
- You have written a measurement plan and want it checked before development starts
- Your GA4 numbers disagree with your order management system and nobody can say why
- You are migrating from Tealium to GTM, or moving tags server-side
- You are about to spend a quarter building reporting on a spec nobody has reviewed
It is equally useful before a build and after one. We recommend before as a higher value exercise.
What we look at
- Completeness. Events with no tag assigned, parameters with no transformation rule, every decision still marked undecided.
- GA4 limits. Custom definitions against the 50 event-scoped, 25 user-scoped and 10 item-scoped caps — and, where you are over, which ones to stop registering rather than stop sending.
- Consent. Tags that still fire when a visitor declines. Cookies written before consent. Cookies missing from the privacy policy.
- Naming and vocabulary. Values that will not group, names that will not pass, controlled lists that have drifted.
- Spec conformance. Ecommerce object clearing, viewport batching, how
valueis defined, boolean typing, whether discounts reconcile back to the order. - The five things to fix first, ranked by what they cost you, each with the fix.
The last one is the point. The first five can be in an inventory but knowing which of them actually matters for your business is the part you are paying for now to save money later.
How it works
- Tell us what you want looked at. The form below – No file yet.
- We confirm scope and price, usually within a business day, and tell you how to send the workbook.
- You send it. Anonymized if you can, with test/uat data, or under NDA if you cannot. We will say which we need.
- Five business days from a complete workbook, you get the report.
Example of what it costs
Priced off our standard hour rate with some examples below:
| Examples | Hours | Price |
|---|---|---|
| Measurement Plan Review | 4 | $680 |
| Review + Walkthrough | 5.5 | $935 |
| Full Implementation Audit | from 16 | from $2,720 |
A review from a blank start runs closer to twelve hours, because most of it is reconstructing what the site actually sends. It is four when the plan is already documented — which is why we publish the GTM Tag & Event Matrix for free. Fill that in and you have done the expensive half yourself.
The walkthrough tier adds a sixty minute call. Worth it when the person who reads the report is not the person who has to action it.
What is not included
We review the document, not the running site. No container access, no live testing, no Preview session. That is what keeps the review fast and fixed-price.
If the review says you need a full implementation audit — container access, live QA against the real site — we will say so and quote it separately. We will not quietly turn a $680 review into a $10,000 engagement.
Your data
A completed measurement plan contains real product data, real URLs and real order values. If this is on behalf of a client or an organization you are not a decision making member of…
Two routes, and we will tell you which one applies before you send anything:
- Anonymise it first. We do not need real order values to find structural problems. This is the default and the faster path. We highly recommend giving us access to a testing/uat site where the data will be faked
- Mutual NDA. For anyone who cannot anonymise. Signed before the file moves, never after. If this is a live site test, we would need to know the order cancelation process with your team.
We hold the file for the length of the engagement plus ninety days, and delete it sooner on request.
Frequently asked questions
No. Send whatever you have — a spreadsheet, a Confluence page, a Jira epic, a dataLayer sample. Our template makes the review faster and therefore cheaper, but it is not a requirement.
Then the report says so, names what is strong, and recommends the next thing worth doing. A clean bill from someone who audits these for a living is worth having. We will not invent findings to justify the invoice.
Yes and No, as a separate engagement. The review stays independent on purpose — a review that exists to sell you a build is not a review. We can work with your development team or suggest one to support the effort. We will manage the project, support, and retest to confirm the corrections.
An account audit looks at settings: property configuration, conversions, attribution windows. This looks at the measurement plan — what your site sends and whether it survives the trip to GA4. Most revenue discrepancies live in the second one.
Yes. Say so on the form and we will price it for client delivery, including the multi-client licence for the template if you need it.
Scope confirmed usually within a business day. Five business days from receipt of a complete workbook.