How to Set Up Key Events in GA4 (6 Steps)

Open most GA4 properties and look at the key events list.

You will find button clicks, scrolls, file downloads and something called test_event_final.

All counted as success.

That is how reports end up showing three times more "leads" than the sales team ever saw.

This guide shows you how to set up key events in GA4 properly, in six steps. You will pick the right outcomes, make them fire at the right moment and prove they work before anyone reports on them.

What Is a Key Event in GA4?

A key event is a GA4 event you have marked as important to your business, such as a lead, booking or purchase.

GA4 used to call these conversions.

Google renamed them so that "conversion" means the same thing in GA4 and Google Ads. In GA4 today, conversions are Google Ads conversions, shown in the Advertising section. Key events are what you see in standard reports.

A few facts worth knowing before you start:

• Standard properties allow up to 30 key events. Analytics 360 allows 50.
• GA4 marks purchase as a key event by default.
• Marking an event affects reports from that moment on. Past data does not change.

Those come from Google's guide to marking key events.

Before You Start

You need a few things in place:

• Access. The Editor role or above on the property covers every step here. Marketer is enough to change counting methods, but not to mark existing events or create events from them.
• Google Tag Manager access if your events come from GTM, with permission to publish.
• A way to test. A real form you can submit, a test booking or a test order.
• A list of outcomes. Ideally from a written GA4 measurement plan. If you do not have one, step 1 covers the short version.

Allow an hour for a simple lead-gen site. Longer if a developer needs to add data layer code.

Step 1: Pick the Outcomes Worth Counting

Start with the business, not the event list.

Ask one question: what would the business celebrate if it doubled?

For most sites the answer is short:

The right-hand column still matters. Track those as normal events and use them in explorations and audiences.

They just do not belong in the key events column.

Where Google has a recommended event name for your outcome, use it. For lead generation, Google's recommended events list includes generate_lead, plus later stages such as qualify_lead and close_convert_lead. Those names feed GA4's Lead acquisition report.

Step 2: Make the Event Fire on Success, Not Intent

This is the step most setups get wrong.

A click on a submit button is not a lead. Forms fail validation. Spam filters reject entries. People double-click.

Your event needs to fire on the confirmed outcome. In order of preference:

1. A data layer push from the form or checkout code after the submission succeeds. Most reliable, and the backbone of any clean Google Tag Manager setup.
2. A success message that appears on the same page, detected with an element visibility trigger.
3. A dedicated thank-you page that only loads after a successful submission. Step 3 covers this without code.

If you use Tag Manager, create a Google Analytics: GA4 Event tag, enter the event name and attach a trigger for the success condition. Then add parameters such as form name or service type.

Follow GA4's naming rules while you are there:

• Event names are case sensitive. generate_lead and Generate_Lead are two different events.
• Start with a letter. Use only letters, numbers and underscores.
• Keep names to 40 characters or fewer.

If the tag does not fire as expected, these steps to debug Google Tag Manager help you trace why.

Step 3: Create a Thank-You Page Event Without Code

If your form sends people to a thank-you page, you can build the event inside GA4.

Do not mark page_view as a key event. That would count every page view on your site as a success.

Instead, create a new event based on page_view:

1. Go to Admin, then Events under Data display, and click Create event.
2. Give it a clear name, such as generate_lead.
3. Add matching conditions: event_name equals page_view, and page_location contains your thank-you URL.
4. Save it.

According to Google's guide to creating events, you can create up to 50 events this way. They take an hour or more to start working and never apply to historical data.

Warning: A thank-you page only works if nobody can reach it any other way. If it is in your sitemap, linked in the menu or indexed by Google, visitors can land on it directly and count as leads. Keep it out of navigation and add a noindex tag, a routine technical SEO fix.

Step 4: Mark the Event as a Key Event

Now flag the event as a key event.

For an event GA4 has already received:

1. Open Admin, then Events under Data display.
2. Find the event in the Recent events tab.
3. Click the star next to it.

For an event you are creating fresh, switch on the "Mark as key event" toggle as you create it.

Standard reports can take up to 24 hours to show the new key event. The Realtime report shows it within minutes of someone triggering it.

Need to stop counting one? Remove the star on the Key events tab. Data already counted stays as key events.

Step 5: Choose the Counting Method and Value

Every key event has a counting method:

• Once per event (recommended). Counts every time the event fires. Five enquiries in one session means five key events.
• Once per session (legacy). Counts one key event per session, however many times it fires.

Once per event is the default for new key events. Key events that came from old Universal Analytics goals often use once per session, so check them.

To change it, open the Key events tab, click the three-dot menu on the row and choose Change counting method. Changes only apply going forward.

For value, purchase events should send real revenue. For leads, you can set a default key event value if your business has an agreed average lead value.

One catch: GA4 needs a currency next to any value, in ISO 4217 format such as GBP or USD. Without it, the event still counts but the value will not pass to Google Ads.

Step 6: Test in DebugView and Reconcile

Never trust a key event you have not watched fire.

Turn on debug mode with Google Tag Assistant or Tag Manager's preview mode. Then open Admin and click DebugView under Data display.

Now test like a sceptic:

• Submit the form properly. The key event should fire once.
• Submit it with a required field empty. The key event should not fire.
• Refresh the thank-you page. Note whether it fires again.
• Repeat on mobile.

One gotcha from Google's DebugView guide: if you use consent mode and decline analytics cookies, your test events will not appear. Accept cookies when you test.

Finally, place one real test enquiry or order and follow it through. It should appear once in GA4 and once in your CRM or store, with the right source.

That last check is what turns GA4 into something you can judge SEO and ads by, rather than a traffic counter.

Common Key Event Mistakes

These turn up in almost every GA4 audit checklist I work through:

• Marking clicks as key events. Phone link clicks and button clicks measure intent, not outcomes.
• Leaving form_submit from enhanced measurement as a key event. It can fire on newsletter boxes, search bars and failed forms.
• Too many key events. When everything is a key event, the column tells you nothing.
• GA4 installed twice. A plugin plus Tag Manager doubles every key event.
• No reconciliation. Nobody compares key events against the CRM, so a broken event goes unnoticed for months.

If your numbers already look wrong, start with why GA4 data does not match your other tools.

Start With One Key Event You Trust

You do not need a perfect setup today.

Pick your single most important outcome. Make it fire on success. Mark it. Test it until you trust it.

Then add the next one.

One reliable key event beats twenty you cannot explain.

If you are building a new property or rebuilding a messy one, my GA4 setup service covers the whole job: measurement plan, tested events, key events and documentation your team can follow.

Already have key events and not sure they are right? A GA4 audit tests each one against real outcomes. And if the events live in a cluttered container, keep these Google Tag Manager best practices close.

For more on how I plan and build properties, see how I approach GA4 implementation.