How to write a GA4 measurement plan

Start from business questions, choose GA4 events, write down naming rules and limits, mark the key events, and put it all in a one-page table.

· 11 min readData

Short answer

A GA4 measurement plan is a one-page table that runs from business questions to events. For each question, check automatic and enhanced measurement first, then recommended events, and build a custom event only if neither fits. The plan records names, parameters and which events are key events.

Imagine opening the GA4 event list of a small workshop’s website. Near the top sit buton_tikla, Buton_Tikla and button_click, side by side. GA4 treats upper and lower case as different in event names, so these are three separate events, and nobody remembers who added which. The cure is a measurement plan written before any code. This article shows how to write a measurement plan in eight steps, ending with a one-page table.

For the setup itself (property, data stream, consent mode, testing) see the GA4 setup checklist. For reading the reports, there is what GA4 is and how to read its reports. Here we cover only the plan: which question, which event, which name, which parameter.

Step 1: Write down the business questions

Start with questions, not events. Five to eight questions that each lead to a decision are enough. Examples: “Which pages bring enquiries?”, “How many people sent the quote form?”, “Which channel did the people who tapped the phone number come from?” Treat that number as our suggestion. Google sets no upper limit, but every extra event adds upkeep.

One level above the questions sit the business goal and the measures that represent it. We cover that in how to choose marketing KPIs. The measurement plan is the layer that says which GA4 event each of those measures will come from.

Step 2: Tie each question to one user action

Next to each question, write one action you can observe on the site: a form successfully sent, a tap on the phone link, a catalogue downloaded, a payment completed. Abstract words such as “interest” or “trust” do not turn into events; reduce them to a behaviour.

A small example: the action behind “How many people sent the quote form?” is the thank-you screen appearing, or a success response coming back from the server. The action behind “How many people called?” is a tap on the phone link. The action behind “Is the catalogue popular?” is a file download. Three questions, three clear actions.

Write down the moment as well as the action. For a form, count the successful submission, not the button click; otherwise failed submissions also look like enquiries.

It helps to sort events into four groups:

  • Automatically collected. They arrive without code once the Google tag is on the site (for example first_visit and session_start).
  • Enhanced measurement. When switched on for the data stream, it collects interactions such as scrolls, outbound clicks, file downloads, site search and form interactions without code.
  • Recommended events. Google defines their names and parameters, but you have to send them. Google’s recommended events list includes generate_lead for a lead that comes in through something like a form, purchase for a purchase and sign_up for creating an account.
  • Custom events. Your own definition, for actions none of the above describes.

The order should be: use the ready-made one first, and build a custom event only when nothing fits. The figure shows the three questions.

Three questions to ask when you need an event: automatic, recommended, custom Automatic or enhanced event already exists? Recommended event already exists? Still no suitable event? No No Yes: use it Yes: use it Yes: build a custom event All go into the plan: name, trigger, parameters Three questions to ask when you need an event: automatic, recommended, custom Automatic or enhanced event already exists? No Recommended event already exists? No Still no suitable event? Yes: use it Yes: use it Yes: build a custom event Everything goes in the plan: name, trigger, parameters
Figure: Try automatic and enhanced measurement first, then recommended events; if neither fits, build a custom event, and write all three into the plan.

We suggest not leaving an important enquiry to the automatic form event of enhanced measurement; this warning comes from our own experience. A separate event that confirms the successful submission is safer. You can build it with the steps in what Google Tag Manager is and how to set it up.

Step 4: Naming rules and limits

Google’s event naming rules say that a name must start with a letter and may contain only letters, numbers and underscores. It must have no spaces and is case sensitive. Reserved names cannot be used; click, form_submit, page_view and scroll are on that list. Parameter names also cannot start with an underscore or with prefixes such as ga_ and google_.

The numeric limits are on Google’s event collection limits page:

  • An event name can be at most 40 characters. If you mark an event as a key event and its name exceeds 40 characters, the page says it will not be reported as a key event because the appended “_c” is missing.
  • One event can carry at most 25 parameters.
  • A parameter name can be at most 40 characters and a parameter value at most 100.

On top of that, we suggest lower case, underscores, an “object_action” pattern (phone_click, brochure_download) and a single language. If an action already has a ready-made name, use it rather than inventing a new one.

Step 5: Parameters and custom dimensions

The event says what happened; the parameters say how. For a quote form, that means a generate_lead event with parameters such as form_name and service_type. Add each parameter only after writing which question it sharpens. Do not send a parameter that answers nothing; the limit of 25 is only a ceiling. For a custom event such as a phone tap, a single parameter (say, which section of the page the tap came from) is often enough.

To see a parameter as a dimension in reports, you need to define a custom dimension. According to Google’s custom dimensions page, a standard property allows 50 event-scoped, 25 user-scoped and 10 item-scoped custom dimensions, plus 50 custom metrics. Reporting can take 24 to 48 hours to start after you create one.

Three warnings:

  • Use a predefined dimension first, if one exists.
  • Do not make a custom dimension out of a parameter that carries a unique value per user; high cardinality can push data into the “(other)” row. For user IDs, Google points to the User-ID feature.
  • Never send personal data (name, email, phone number) as a parameter.

Step 6: Which events become key events

A key event measures an action that is particularly important to the success of the business; according to Google’s key events page, any event you collect can become one. The steps to mark one are in Admin, under Data display, on the Events page, where you click the star icon. A standard property can have at most 30 key events. You can also mark an event that has not arrived yet, and GA4 treats it as a key event once it does. When you create a new event, you also choose a default value and a counting method; write those into the plan too.

Look at two more details. First, purchase is marked as a key event by default. Second, if a linked Google Ads account has ads personalisation enabled, events such as add_to_cart, begin_checkout, session_start and view_item are marked as key events as well. If you do not open the list and tidy it, your main goal gets lost in the crowd.

We suggest starting with 3 to 5 events and marking only the actions that bring money or enquiries: quote form, phone, purchase. Scrolls, page views and file downloads do not have to be key events; following them as report breakdowns is enough. If you want to bid in Google Ads, you can create the conversion from a key event. According to Google’s key events page, this lets you report the same conversion counts in Google Ads and Analytics.

Step 7: Put it all on one page

The table below is a made-up example plan for a workshop website. Build yours with the same columns, and add the owner’s name and the date of the last check.

Event Type Question it answers Parameters Key event
page_view Automatic Which pages are visited? page_location, page_referrer No
generate_lead Recommended How many people sent the quote form? form_name, service_type Yes
phone_click Custom How many people tapped the phone number? click_location Yes
file_download Enhanced measurement Who downloaded the catalogue, from which page? file_name No
view_search_results Enhanced measurement What do visitors search for on the site? search_term No

Read the table like this: the first column is the exact event name and must match the code character for character. The type column says who sends the event and how; a “Custom” row means extra development or Tag Manager work. The parameter column also shows which ones need a custom dimension. The last column is the key event decision.

Keeping the table as plain text works well. It lives in a shared document or in the site’s repository, changes are written with dates, and a newcomer can read it on day one.

Step 8: Test it and name an owner

After implementing the plan, trigger each row from your own device and watch it in DebugView. Tick off that the name, the parameters and the count match the plan. The full testing steps are in the checklist. Give the plan an owner; anyone who wants a new event adds a row first. Reviewing the plan every three months is a good habit too: you remove unused events and refresh the key event list against the goal of the day. When an agency or a new team takes over, there is a document they can read.

Common mistakes

  • Adding events without writing a question; a year later half of them go unused.
  • Inventing your own name when a ready-made event exists.
  • Creating several names for the same action with different capitalisation.
  • Marking every event as a key event.
  • Sending a parameter but defining no custom dimension, then assuming the data never arrived because the report shows nothing.
  • Counting the button click on a form; failed submissions also look like enquiries.

Once the plan is in place, funnel analysis gets easier too, because the steps are already named. We cover that in how to do a GA4 funnel analysis. Writing and implementing a measurement plan is part of our data and CRO service.

Common questions

How many events should I measure in GA4?

There is no fixed number. For web data streams there is no limit on distinctly named events, but every event should have a question. We suggest never adding an event that has no question behind it. At the start, five or six rows in the plan are more than enough for most small and mid-sized sites; you add rows as needs arise.

Is a key event the same as a conversion?

In GA4, the actions that matter to the business are marked as key events. In Google Ads, a conversion can be created from a key event. Google says this route is a consistent way to measure the action and reduces the risk of discrepancies between Google Ads and Analytics. We suggest adding a note next to each key event in the plan: “Will it be sent to Google Ads?”

When do I need a custom event?

When none of the automatic, enhanced and recommended events describes the action. A tap on a phone link is an action where a custom event is often needed. Check Google’s list first; if a suitable name exists, use it. If not, choose your own name that follows the rules in Step 4.

One thing you can do today: open Admin, Data display, Events in GA4 and copy the event names into a table. Note the duplicate names that count the same action and the events marked as key events. That list is the first draft of your plan.

Sources

This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 15 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.

Tell us about
your project.

Fill in the form or write to us directly, and we will agree on a day to talk.

Your first meeting is with Deniz Sezer, founder of Detmore.

First meeting free · Reply within one working day · Written proposal in 2 to 3 days · NDA ready

What do you need? pick as many as you like

Name, email and phone are required.

Contact

We reply within one working day.