Analytics and Measurement
Analytics audit and rebuild
Within Analytics and Measurement, this is the piece that fix the tracking before arguing about the numbers it produces.
What does analytics audit and rebuild mean here?
Fix the tracking before arguing about the numbers it produces. In practice that means a full audit of what fires, where, and whether it fires twice, and then the harder half: Conversion definitions checked against what the business actually counts as a win.
Why this work exists
Nothing about this is difficult. It is just rarely anybody’s job, so it waits.
This is one part of Analytics and Measurement, described separately because it is usually the first thing anybody needs.
The nearest piece of work to it is fixing the implementation before arguing about the numbers. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
You can tell it is right when a new person can pick it up and be useful inside a week.
The gap between that and where most accounts start is why this is scoped as analytics audit and rebuild rather than as a line inside something larger. Pointing the account at the thing the business actually wants is the usual second step once it is in place.
When this is the right work
What tells you to start here:
- Two reports disagree and nobody can say which is right
- Conversions look implausibly high or low and have for months
- Nobody knows what half the tags in the container do
If none of those is true, something else is probably the constraint, and the Analytics and Measurement overview maps the alternatives. The usual neighbours are separating what is measured from what is modelled, in the report itself and configuring the assistant channel group so that traffic stops reading as direct.
What the work covers
The scope, stated plainly:
- A full audit of what fires, where, and whether it fires twice. Usually quick; occasionally the thing that reopens the whole scope.
- Conversion definitions checked against what the business actually counts as a win, scoped against what the business can actually act on rather than what is possible.
- Cross-domain and subdomain handling, where sessions get split and attribution quietly breaks, usually the first thing to show a result, so it goes early.
- Documentation, so the next person does not start this audit again in a year. This is where the theory meets the account and usually loses.
How it runs
Three stages. Most of the risk sits in the first one.
Bringing in whoever owns the system
Developers, agency partners or whoever actually controls the platform get involved before recommendations are written, not after they are rejected.
Proving it in one place first
Changes get made to a small, representative slice and measured there before being applied everywhere. It is slower for three weeks and faster for the rest of the year.
Clearing the contradictions
Where two systems disagree about the same fact, that gets settled before anything is built on top of either of them.
What each part runs into
Where each part tends to meet resistance:
- A full audit of what fires, where, and whether it fires twice, which in Sharjah runs into a procurement step nobody accounted for
- Conversion definitions checked against what the business actually counts as a win: the New York version of this has to deal with a measurement baseline that was never taken
- Cross-domain and subdomain handling, where sessions get split and attribution quietly breaks, where a Austin engagement contends with a language mix the content has to match rather than assume
- Documentation, so the next person does not start this audit again in a year – working in Singapore this means accounting for an enquiry path that runs through a messaging app rather than a form
The error worth naming
Adding more tracking on top of broken tracking. It multiplies the disagreement instead of resolving it.
Naming it upfront is the difference between a result and a report about effort.
How it is measured
Data quality checks passing, and agreement between platforms within an explainable range. That is what gets reported, and it is deliberately narrow enough to move within the engagement.
Where this number and the revenue number disagree, the revenue number wins and the measure gets revisited.
What you end up with
You finish with a corrected implementation, a documented measurement plan, and a tag inventory with owners.
Versioned, so the next pass starts from this one rather than from scratch.
How it differs by sector
This work is not sector-neutral, and the differences are specific:
- Finance and fintech, constrained by the fact that regulated claims, compliance review in the publishing path, and trust signals that have to be real.
- Travel and hospitality: Aggregators hold the demand, so direct booking depends on being the specific named property. so this work has to account for that before anything else.
- Marketplaces and platforms, where two sides to acquire, and a programmatic page set that can sink the whole domain. which moves this work earlier in the plan.
The industry pages carry the rest of that detail. Finance and fintech and Travel and hospitality are the two where this piece of work most often decides the outcome.
Common questions
How long does an analytics audit take?
A week or two to find everything, longer to fix depending on who owns the site. The finding is the fast part.
Should we rebuild or repair?
Repair, unless the measurement plan itself is wrong. A rebuild loses historical comparability, which is often the most valuable thing you have.
Does anything need doing before analytics audit and rebuild?
Sometimes. The signals above are the honest test, and where something upstream is the real constraint we will name it even though it is not the work on this page. Noida explains the method. Pune explains why the method is the one being used.
Is there a minimum worth doing?
There is a point below which the measurement cannot detect a change, and we would rather say so than take the work. Data quality checks passing, and agreement between platforms within an explainable range has to be able to move for the engagement to mean anything. Worth a look before committing budget: Manufacturing and industrial, then Marketplaces and platforms.
Does this have to be bought separately from Analytics and Measurement?
No. It is usually part of a wider Analytics and Measurement engagement, and it is described separately because it is the piece clients most often ask about by name. It can also be scoped on its own where that is genuinely what is needed, and we will say which applies after looking. The page that answers the follow-up question is Digital PR and Link Building. The one that answers the objection is Ecommerce SEO.
Ask about analytics audit and rebuild
Tell us what you have tried already. That is usually the fastest route to a useful reply.
See what the first ninety days would cover
Most accounts have one thing holding them back. The useful first conversation is about finding which one.