Almost nobody decides what to measure: an event list gets copied from another project and months later nobody knows whether the number means anything. When someone asks "is this true?", there is no answer.
One-time purchase · no subscription · no account to maintain
Event lists travel between projects far more easily than the reasons behind them. What arrives is the list; what stays behind is why each event was there.
Months later the dashboard is full and the business question is still unanswered — because it was never the question that site had to answer.
Each archetype asks a different business question. From a catalogue of 14 events it separates the minimum from what opens later, sets the perimeter at three levels —some data must never leave the browser— and gives you eight verification controls, so the plan can be checked instead of believed.
A Telemetry Plan in seven pieces, derived from seven context questions.
What your site is and which business question that archetype has to answer. Everything downstream depends on this.
From a catalogue of 14, separated into the minimum set and what opens later. An event that opens later is a decision, not an omission.
Three levels — including what must never leave the browser. Declaring it up front is what stops it being decided by whoever implements it.
What each event has to carry so the number can be read afterwards without guessing.
Eight verification controls, so the plan is something you check rather than something you believe.
Printable and exportable, with your name on it. You hand it to whoever implements it, and show it when the measurement is doubted.
The five set-up screenshots are real and anonymised. Their consoles are in Spanish: that is how those implementations were configured, and screenshots are not restaged.
Seven context questions, one per screen, each changing the plan.
Editorial medium, personal brand, B2B services or utility product. The archetype sets the business question.
From the catalogue of 14 events, the minimum comes out for that archetype — and what opens later comes out as a dated decision.
Three levels, including what must never leave the browser. It is a decision, not a default.
Seven pieces plus eight verification controls, so whoever implements it can be checked.
Seven pieces, printable and exportable, with your name on it. It is the document you show when someone doubts the measurement — and the one that says what was deliberately left out.
It produces the plan, not the build. That boundary is what makes it useful: a document that decides what to measure is worth exactly as much as it is independent from whoever installs it.
Every line is a boundary declared before purchase, not discovered afterwards.
It teaches no platform and no console.
It produces the plan, not the build.
That is the Analytics Audit Tool. One decides before, the other rules after.
Only a better defence — which is the only thing a plan can honestly offer.
Deciding what to measure comes before ruling on what got implemented.
Once the plan is implemented, the question changes: how far can the resulting number be believed? That is what the audit rules on, and together they are the Measurement Stack.
See Analytics Audit Tool →If what you need is to check what must be configured before spending on ads —signals, tracking, events and CRM connected— that is the entry-level tool.
See Digital Marketing Setup →Measurement Plan + Analytics Audit Tool. You decide what to track, then you rule on whether what got implemented holds. It is the only bundle with a real price advantage: 898 apart, 799 together.
799 MXN See the bundle →Thirteen years building acquisition systems for operations that do not forgive: BAIT and Farmacias YZA (Walmart, FEMSA), Movistar, Mercedes-Benz. Over 5M MXN a month under management.
I don't optimise campaigns. I govern systems. And I don't publish courses here — I publish the instruments I work with. Same judgement I apply on a paid engagement; the difference is that here you run it.
Instant download. Unzip it, open it with a double click, and it runs offline.
Base price. Hotmart's checkout will show 462.84 MXN with tax included.
This one decides what to measure before it is implemented. The audit rules on a chain that already exists. One comes before building, the other after — and together they are the Measurement Stack, the only bundle with a real price advantage.
No. The plan is platform-independent: it says what to measure and why, with the dimensions and the controls. Whoever implements it does so in whichever tool you already use.
Because that is how those implementations were actually configured. They are real and anonymised, and screenshots are not restaged: a restaged screenshot is a drawing of evidence, not evidence.
No. It is a tool you run yourself in the browser. You answer what you know about your operation and you leave with a document you can put in front of whoever signs.
A ZIP file. Unzip it and open it with a double click. It runs on your machine, with no account, no sign-up and no connection: nothing you type leaves it.
No. One-time purchase, no renewal and no account to maintain. The price shown is the base price; the checkout will show the amount with tax.