Traffic data without conversion data is noise. You can see that 3,000 people visited your site last week — but without knowing how many of them filled in a form, made a purchase, or signed up for your list, that number tells you almost nothing actionable. GA4 calls conversions "key events" — and setting them up is simpler than most people expect.
This guide walks through the full process: what key events are, which ones to track for different business types, how to mark an event as a key event in GA4 without touching any code, how to verify it's working, and what to look at once conversions are flowing.
What key events are (and why the name changed)
In March 2024, Google renamed "conversions" to "key events" in GA4. The underlying concept is identical: you designate certain events as things that matter to your business, and GA4 starts counting them separately, attributing them to traffic sources, and surfacing them in dedicated reports.
The renaming happened to clarify the distinction between GA4 key events and Google Ads conversions, which are a related but separate concept. For site owners not running Google Ads, the practical difference is zero — you're marking your most important actions, and GA4 tracks them.
Without a key event, you're flying by traffic alone. Traffic going up feels good. Traffic going up while conversions go down is a problem you won't see.
Which events GA4 collects automatically
GA4 auto-collects a set of events the moment you install the tracking code — no setup required:
- page_view — fires on every page load
- session_start — fires at the start of each session
- first_visit — fires the first time a user visits your site
- scroll — fires when a user scrolls 90% of a page
- click — fires on outbound link clicks (enhanced measurement)
- purchase — fires automatically for standard e-commerce implementations
Many popular form builders also send events automatically. Gravity Forms, WPForms, HubSpot Forms, Typeform, and Contact Form 7 (with the right add-on) often fire a form_submit or generate_lead event when a form is completed. Before setting anything up manually, it's worth checking whether these events are already arriving in your GA4 property.
Step 1: Check what's already being collected
Go to Admin > DebugView in GA4. On a separate browser or device, visit your site and submit one of your forms. Watch the DebugView panel. If a form_submit or generate_lead event appears within 30 seconds, the tracking is already in place. You just need to mark it as a key event.
You can also check Reports > Engagement > Events and look at the event list. Any event that has fired in the past 30 days appears here. If you see form_submit or generate_lead in the list, you're most of the way there.
DebugView requires the GA4 DebugView extension or a test device. In Google Chrome, install the "Google Analytics Debugger" Chrome extension and enable it. Your device will then appear in DebugView in GA4 within a few minutes, and you can watch events fire in real time as you use your site.
Step 2: Mark the event as a key event
Once you've confirmed the event is being collected, marking it as a key event takes about 30 seconds:
- In GA4, go to Admin > Data display > Key events
- Click Create key event
- Type the exact event name (for example: form_submit, generate_lead, or purchase)
- Click Save
That's it. GA4 will now count that event as a key event going forward. Note that this does not backfill historical data — key events are counted from the moment you mark them, not retroactively.
Step 3: Verify it's working
After marking the event as a key event, go back to DebugView and submit your form again. The event should now appear with a star icon in DebugView, indicating it has been recognised as a key event.
You can also check the Real-Time report (Reports > Realtime) while submitting a form. The event should appear under "Event count by Event name" in real time. Within 24–48 hours, it will start appearing in Reports > Engagement > Conversions alongside historical data for that event name.
Once conversions are flowing: what to look at
With key events in place, two reports become significantly more useful:
Conversions report
Go to Reports > Engagement > Conversions to see a day-by-day view of how many key events occurred. Look at this alongside your session count. If sessions go up but key events stay flat, your traffic quality has changed — more visitors, but fewer who are ready to act. If sessions go down but key events hold, you're losing noise and keeping quality.
Traffic acquisition by conversion
In Reports > Acquisition > Traffic acquisition, you can add "Key events" as a metric to see which channels are actually driving conversions — not just sessions. This is often the most eye-opening report for site owners who assumed their top traffic channel was also their top converting channel. It frequently isn't.
For readers who want to go deeper on how GA4 decides which channel gets credit when a conversion happens across multiple touchpoints, see our post on data-driven vs last-click attribution.
The most common mistake: marking page_view as a key event
Do not mark page_view as a key event. Every session includes at least one page_view, which means your key event count will equal or exceed your session count, and every metric that references conversions becomes meaningless.
The same logic applies to session_start and first_visit. These are automatically collected events that happen in every session — marking them as key events tells you nothing about whether users actually did anything valuable.
A key event should represent a genuine business outcome — a form submitted, a purchase completed, an account created, a phone number clicked. If the event fires on every session regardless of what the user does, it isn't measuring a conversion.
| Business type | Recommended key event | Notes |
|---|---|---|
| Professional services / B2B | generate_lead or form_submit | Fire on contact form or enquiry submission |
| E-commerce | purchase | Auto-collected if using standard GA4 e-commerce |
| SaaS / subscription | sign_up or trial_start | May require custom event via GTM |
| Content / publisher | newsletter_signup or download | Depends on your email tool's GA4 integration |
| Local business | phone_click or directions_click | Configure click events in GTM for these |
What happens when you track traffic but not conversions
The pageviews up, revenue flat case study is the clearest illustration of what goes wrong without conversion tracking. Traffic was growing — meaningfully, month over month. Every report looked healthy. But revenue was flat. Without key event data, there was no way to see that the traffic growth was coming from channels that never converted, while the channels that did convert were actually declining. Conversion tracking made the invisible visible in under a week.
Frequently asked questions
What are key events in GA4?
Key events are what GA4 calls conversions as of March 2024. They are specific events that you mark as important in your GA4 property — actions like form submissions, purchases, sign-ups, or downloads that represent meaningful outcomes for your business. Once an event is marked as a key event, GA4 highlights it in reports and lets you filter and compare data by whether sessions included that action.
How do I track form submissions in GA4?
Many popular form builders (Gravity Forms, WPForms, Typeform, HubSpot Forms, Contact Form 7 with the right plugin) automatically send a form_submit or generate_lead event to GA4 when a form is completed. Check your GA4 DebugView while submitting a test form — if you see the event appear, the tracking is already in place and you just need to mark it as a key event. If nothing appears, you may need to configure the event manually via Google Tag Manager.
How do I check if conversion tracking is working in GA4?
The fastest way to verify is DebugView: go to Admin > DebugView in GA4, then on a separate device or browser, complete the action you're tracking. You should see the event appear in DebugView in real time, usually within 30 seconds. If the event appears and has been marked as a key event, it will show with a star icon. The Real-Time report also shows events as they arrive.
What is the difference between events and key events in GA4?
In GA4, every interaction can be tracked as an event — a page view, a scroll, a button click, a form submission. Key events are the subset of events that you have marked as important conversions for your business. GA4 collects dozens of events automatically; you decide which ones matter enough to be key events. Not every event should be a key event — marking too many inflates your numbers and makes them meaningless.
Where WebSignalytics fits
Setting up key events is a one-time task. Monitoring them — checking week over week whether conversions are holding up, which channels are performing, and when something drops — is ongoing. That's where most site owners lose the thread: they set up the tracking and then never look at it consistently enough to catch when it drifts.
WebSignalytics pulls your key event data alongside your traffic data and delivers a plain-language summary each week. You can see at a glance whether your conversions went up, down, or flat — and which channel drove the change. If conversions drop suddenly without a traffic explanation, that shows up in the digest before it has time to quietly cost you a month of leads.
See your conversions in plain language, every week
WebSignalytics connects to your GA4 and emails you a weekly report that shows how your key events moved, which channels converted, and what changed — no dashboard required.
Start your 14‑day free trial