Methodology

The sequence we follow when we audit an analytics application.

This is the custom working page for the practice: not a product tour, a description of the engagement from the first login to the findings session on Jalan USJ 14/1 or at your office.

Two colleagues reviewing a document together

Every analytics application is configured differently. The method is not. We keep the same five stages so you can see where the days go, what we need from you, and what you should expect to hold at the end. Implementation work — changing tags, rebuilding events, rewriting dashboards — is outside this sequence unless you commission it separately.

01

Access and walkthrough

We collect logins to the analytics application, tag manager, and any staging site you name. A practitioner sits with your operator and clicks the journeys that matter: purchase, sign-up, lead, or the path you actually need audited.

02

Inventory

Properties, streams, containers, SDKs, and server-side endpoints are listed with owners. Parallel properties left over from migrations are flagged. Nothing is repaired at this stage.

03

Live collection

We record what the browser and the application emit on each journey, including consent accept, reject, and withdraw. The tracking plan, if you have one, is treated as a hypothesis.

04

Reconciliation

One conversion, one week, two systems. We explain the gap between the analytics application and the CRM, ads platform, or warehouse. Matching the numbers is not the goal; naming the cause is.

05

Findings session

You receive a ranked file with evidence and a repair order. We walk it with the people who will change tags or settings. Implementation work after that is optional and quoted separately.

What we need from you

Admin or analyst access to the analytics application under review, the tag manager or SDK repository, and a person who can complete the customer journeys on a staging or production site. If you want a discrepancy review, we also need a week of exports from the system you treat as operational truth — usually the CRM, billing, or warehouse.

What you hold at the end

A ranked findings file with evidence (screenshots, event payloads, and extracts), a repair order your developers can schedule, and notes from the working session. We do not leave you with a slide that says “insights” and no next action.

Book the scoping call that starts stage one