One Page Measurement Plan for GA4

A GA4 property can be installed perfectly, firing events on every button and form on the site, and still be worthless. It happens often enough that I now assume it.

Someone opens the interface, leaves enhanced measurement on, wires up a few clicks in Google Tag Manager, and a year later nothing about how the business operates has changed because of a number in that account. The tags are usually fine, and the account is not the problem...the missing page in front of it is.

So I stopped starting in GA4...the work now starts in a document, one page, written before a single tag exists. It usually takes one working session with the owner or the marketing lead, and it does more for the data (if not the speed of the build) than any amount of tag debugging afterward.

The Plan Before the Property

GA4 uses an event based model, which means it will accept more or less whatever you decide to send it. That flexibility is exactly the problem...an account that accepts anything ends up holding everything.

A property built without a plan fills up with events that describe the website instead of the business. Clicks, scrolls, page views and video plays are all technically accurate. Accuracy was never the question...whether any of it connects to something someone does on Monday morning is.

The interface cannot tell you which numbers matter...it only counts what you point it at. Writing the plan on paper first moves the argument about what matters to where it is still cheap...nothing has been implemented and nobody is defending work they already did.

Outcomes That Pay the Bills

The first block on the page is a short list of business outcomes...not metrics. The question for the owner is what has to happen to make money this quarter, and the answers go on the page in their words rather than mine.

What counts as an outcome depends on how the money arrives.

• Service Business: a qualified inquiry, meaning a form filled out, a phone call during business hours or an appointment booked.
• Retail: a purchase, along with the couple of steps on the path that reliably precede one.
• Long Sales Cycle: a demo request plus the document download that sales recognizes as real intent...not idle research.

Keep this list short. If it runs long, the plan has drifted...it is describing the site rather than the business. For each outcome the page notes where it happens, who follows up and/or closes it, and what the owner would consider a normal week against a bad one, in their own terms.

The Decision Test, Out Loud

The decision test is the part of the page that does the most work. For every candidate event, someone in the room has to finish one sentence out loud. If this number moves meaningfully, we will do this. If nobody can finish that sentence, the event does not get tagged.

Quote requests drop for two straight weeks, so the form gets tested for breakage and then somebody looks at which pages were feeding it. That one passes. Average scroll depth on the about page moves, and then what...nobody in the room has an ending for that sentence, which tells you everything.

It is interesting, not actionable, and interesting has a way of crowding out actionable in a reporting deck. The test eliminates most of the initial list, and that is the point...a property that counts a handful of things people genuinely act on is worth far more than one that counts everything and gets opened twice a year.

Event Names the Business Recognizes

Event names outlive the person who wrote them, and somebody new inherits this account eventually. The names are the only documentation that person is guaranteed to find. So the plan specifies exact strings, decided once, before anyone opens a tag manager.

Two rules govern the naming, plus one check against GA4 itself.

• Business Words: if the shop says estimate, the event is estimate_request...not lead_form_submit_v2. If they say service call, then service_call_booked.
• Consistent Shape: lowercase, underscores, the same pattern of subject and action every time.
• Reserved Strings: check what GA4 collects on its own, so a new name does not collide with one already taken.

When the report matches the vocabulary of the weekly meeting, people read it. Writing the strings on the page means the tag manager, the CRM notes and the monthly report all end up agreeing with each other...no translation step sits in the middle.

Parameters, Context and Personal Data

An event tells you something happened...parameters tell you enough to act on it. Under each event the page lists the parameters worth carrying and, next to each one, the reason it exists.

• Source: which form or which location, when the business runs more than one.
• Category: the service or product being asked about, when follow up differs by type.
• Entry Point: the campaign that brought the visit, when the answer changes where the budget goes.
• Value: a number, but only when the business can honestly attach one to that action.

Two constraints go in writing right on the page, above the parameter list.

• No People: never a name, an email address, a phone number, or anything else that identifies someone.
• Custom Dimensions: register anything you want to report on, or it gets collected and stays invisible in GA4.

That second one is the most frustrating failure mode in the whole platform, because the data is there, the interface will not show it to you, and nothing in the account explains why.

What to Do This Week

Open a blank page rather than the analytics interface, then work down this order. The document does not need to be pretty...it needs to be decided.

1. Plain Language: write the outcomes the way the owner says them, before any metric gets a name.
2. Decision Test: sit with whoever would act on each number and run it out loud...cut anything nobody can finish.
3. Exact Strings: write the surviving event names and parameters down verbatim, with a one line note on why each exists.
4. Tag Manager: open it last and build precisely what is on the page...nothing extra because it was easy to add.

Revisit the page when the business changes...a new service or a new location earns an edit, and a new report type in the interface does not. I would rather argue about this on paper than inside a tag manager. If you want a second set of eyes on that session for your own site, that is a fine reason to get in touch.