How to Write a GA4 Measurement Plan (7 Steps)

Most GA4 properties were built tag first.

Someone pasted the measurement ID, switched on every option and called it done.

A year later, nobody can say what half the events mean, and the key events column counts things nobody cares about.

A measurement plan prevents that.

It is the document I write before any GA4 build, and it is shorter than you might expect.

In this guide you will write one in seven steps, with an example you can copy.

What Goes in a GA4 Measurement Plan?

A GA4 measurement plan is a document that maps each business question to the event, parameters, key event status and report that will answer it.

At its core is one table. Here is a cut-down example for a B2B software company, so you can see the shape:

Around that table, the plan also records:

• Property settings and why each was chosen.
• Naming rules for events and parameters.
• A UTM convention for campaigns.
• An owner and a change log.

That is it. Your plan will probably fit on a few spreadsheet tabs.

Step 1: List the Decisions the Data Must Support

Start with people, not tags.

Ask everyone who uses the numbers: what decisions do you make each month?

Then ask what you would need to know to make those decisions better.

Typical answers:

• "Where should next quarter's ad budget go?"
• "Which landing pages produce enquiries, not just traffic?"
• "Is the new pricing page helping or hurting?"

Write each one down as a question.

Then cut the list.

If nobody will act on the answer, it does not belong in your plan.

Pro tip: Invite someone from sales or operations, not just marketing. They know what a real lead looks like, and they will spot a "lead" definition that sales would never accept.

Step 2: Define Success in Plain Words

Before you name a single event, write down what each outcome actually means.

Be precise:

• A lead is a submitted form that passed validation, not a click on the submit button.
• A booking is a confirmed slot in the scheduling tool, not a visit to the booking page.
• A purchase is a completed payment, on every payment method you accept.

This step settles arguments before they happen.

It also tells whoever builds your tracking exactly when each event should fire. My guide on how to set up key events in GA4 shows why the success-not-click rule matters so much.

Step 3: Map Each Question to an Event

Now turn each question into an event.

Pick the event type in this order:

1. Automatically collected events. GA4 records these with no extra work, such as page views and first visits.
2. Enhanced measurement events. Scrolls, outbound clicks, site search, video engagement, file downloads and form interactions. Switch them on only if they measure something reliably on your site.
3. Recommended events. Google's predefined names, such as generate_lead, sign_up and purchase. Google's recommended events list shows which ones exist for lead generation and online sales.
4. Custom events. Only when nothing above fits.

That order matters.

Google's own help notes that custom events do not show up in most standard reports. You will need explorations to see them.

For every event, write the exact trigger condition in your plan.

"Fires when the form handler confirms success" is a spec. "Form submit" is not.

Step 4: Choose Parameters and Custom Dimensions Carefully

Parameters add detail to events: which form, which plan, which service.

But GA4 has limits, and they shape what you can plan.

According to Google's event collection limits, a standard property accepts:

• Up to 25 parameters per event.
• Event and parameter names up to 40 characters.
• Parameter values up to 100 characters, with longer allowances for page title, referrer and page location.

To use a parameter in reports, you also have to register it as a custom dimension.

Google's configuration limits cap standard properties at 50 event-scoped and 25 user-scoped custom dimensions.

So register only what you will actually report on.

Watch out for high-cardinality values too.

Google treats dimensions with more than 500 unique values in a day as high cardinality. Unique IDs and timestamps push useful rows into (other), so keep them out of custom dimensions. If you need them, send them to the BigQuery export instead, as part of the wider Google Analytics consulting picture.

Warning: Never plan a parameter that carries personal data, such as a name, email address or phone number. Google's policies prohibit sending it to Analytics.

Step 5: Pick the Few Key Events

Go back to your success definitions from step 2.

Those outcomes, and only those, become key events.

A standard property allows up to 30 key events. Treat that as a ceiling, not a target.

Most service and B2B sites need between one and five.

Everything else stays a normal event.

Supporting events, such as pricing page views or calculator use, are still valuable. You use them in explorations, funnels and audiences.

Mark the decision in the plan's "Key event?" column, with a one-line reason for each yes.

That reason stops the next person from adding scroll depth as a key event because a dashboard looked empty.

Step 6: Record Property Settings and Naming Rules

The plan is not only about events.

Write down your property settings and the reason behind each one:

Then add the naming rules.

Event names in GA4 are case sensitive, so agree on lower case with underscores and stick to it.

Finish with a UTM convention: allowed source and medium values, and a worked example for each channel you use.

Whoever builds next quarter's email links will need it.

If your events will run through Tag Manager, match the container's naming to the plan. These Google Tag Manager best practices cover the container side.

Step 7: Get Sign-Off and Keep the Plan Alive

Share the finished plan with everyone from step 1 and ask for one thing: does this answer your questions?

Fix what they flag, then freeze version one.

After that, your plan needs an owner and a change log.

Every new event, renamed parameter or changed setting gets a dated line.

Review it whenever the site changes shape:

• A redesign or new CMS. Put tracking checks inside your SEO migration plan so both get tested at launch.
• A new form, booking tool or payment method.
• A new agency or marketing hire.

Once a year, compare the plan against what the property actually collects.

The checks in my GA4 audit checklist work well for that review. When the numbers drift from your CRM, why GA4 data does not match explains which gaps are normal.

Turn Your Measurement Plan Into a Working Property

A GA4 measurement plan does not need to be long.

It needs to be agreed, specific and kept up to date.

Start with step 1 today.

List the five decisions your business makes from data and write each one as a question.

Everything else follows from that list.

When your plan is ready, the build is the easy part: tags, key events and settings that match the document line by line.

My GA4 setup service does exactly that, from the planning sessions through to tested, documented tracking.

If you already have a property and want to know how far it is from a plan like this, a GA4 audit will show you. And once the numbers hold up, you can judge marketing by real outcomes, for example by feeding them into an SEO ROI calculator.

See how a planned GA4 implementation works if you would rather hand over the build.