GA4 conversion tracking works by sending an event for each action you care about, such as a form submission or a phone tap, and then marking that event as a key event. Google Analytics now calls these important actions key events and reserves the word “conversion” for actions you use in Google Ads. Set up the events, mark the right ones, respect consent, then confirm each one in DebugView before you trust the numbers.
In Google’s own words, “A key event is an event that measures an action that’s particularly important to the success of your business.” Everything else in GA4 is just an event. To keep setups honest, I use a four-step loop I call Name, Fire, Mark, Prove: name the action, fire an event when it really happens, mark it as a key event, and prove it in DebugView.
What changed between conversions and key events in GA4?
Only the vocabulary in Analytics changed, but it matters. Google’s page on conversions vs. key events says important actions in Analytics “are now called ‘key events.’” A conversion, by contrast, “now refers to an important action that you want to use to measure the performance of your ad campaigns.”
So a key event lives in your Analytics reports. A conversion lives in Google Ads, and you create one from a key event through a linked Ads account. The same page notes that beginning June 15, 2026, Google Analytics moved to Consent Mode (within Google Ads) as the single control for Google Ads cookies and IDs. If you don’t buy ads, key events are all you need.
How does GA4 conversion tracking work now?
It’s a chain of three links: an event fires, you mark it as a key event, and optionally you turn that key event into a Google Ads conversion. Some events arrive automatically. Enhanced measurement can send form_start “the first time a user interacts with a form in a session” and form_submit when a user submits a form, plus a click event for outbound links.
Automatic events are a starting point, not a finished setup. Google’s list of recommended events includes generate_lead for when a visitor “submits a form online or submits information offline,” and lead-funnel events such as qualify_lead and close_convert_lead.
Good tracking also feeds your SEO work. Without reliable key events, you can’t tell whether the traffic from local SEO for small business or ranking in AI Overviews turns into calls and leads.
Which events should a small business mark as key events?
Mark the handful of actions that mean someone wants to buy or talk to you, and nothing else. Google’s lead generation events give you six stages, from generate_lead to close_unconvert_lead, but most small sites only need the first one plus a few contact actions:
| Visitor action | Event name | How it fires | Key event? |
|---|---|---|---|
| Submits the contact or quote form | generate_lead | Tag Manager, on the success signal | Yes |
| Taps a phone number | click_to_call | Tag Manager click trigger on tel: links | Yes |
| Clicks “Book a call” or a booking link | book_call_click | Tag Manager click trigger | Yes |
| Starts a form | form_start | Enhanced measurement | No |
| Views any page | page_view | Automatic | No |
click_to_call and book_call_click are custom names I use, not Google’s. Marking page_view or form_start as key events inflates your numbers and hides the real signal.
How do you track forms, phone clicks and CTA buttons with Google Tag Manager?
Use Tag Manager triggers that fire only on the real action, then send a GA4 event tag. Google’s click trigger documentation describes two types: All Elements, which tracks clicks on any element, and Just Links, which tracks clicks on HTML links. Set it to fire on “Some Clicks” and add a condition so it only fires where you expect.
- Phone taps: a Just Links trigger where Click URL starts with tel:, sending click_to_call.
- CTA buttons: an All Elements trigger matched on the button’s text or URL, sending a named event.
- Forms: fire generate_lead on the success signal, such as a thank-you page view or a confirmation message appearing, not on the button click.
That last point is where most setups go wrong. A click on “Submit” also fires when validation fails, so the count runs high. If your forms submit in the background, a redesign can silently break tracking, which is why I include it in my website redesign checklist.
How do you mark an event as a key event in GA4?
In Admin, under Data display, open Events and mark the event as a key event. When you create a new event in the same screen, Google’s create or modify key events guide shows a “Mark as key event” toggle where you also pick a default value and a counting method.
Give a key event a value only if you can defend it, such as an average lead value your sales data supports.
How does consent mode affect GA4 conversion tracking?
When a visitor declines cookies, GA4 records less, and consent mode decides what happens next. Google’s consent mode guide explains that with analytics_storage denied, Analytics doesn’t read or write its first-party cookies and sends cookieless pings instead. The basic setup blocks tags until consent. The advanced setup loads tags first and enables behavioral modeling to fill the gaps.
Modeling has a size floor. Google’s behavioral modeling requirements are:
| Requirement | Threshold |
|---|---|
| Events per day with analytics_storage denied | At least 1,000, for at least 7 days |
| Daily users with analytics_storage granted | At least 1,000, on 7 of the previous 28 days |
| Consent mode coverage | All pages of the site |
Many small business sites never reach those numbers, so expect a gap between key events and real leads. Read trends, and compare against your CRM.
How do you verify key events in DebugView?
Turn on debug mode, perform the action yourself and watch the event arrive. Google’s DebugView guide says the seconds stream shows events from the last 60 seconds and the minutes stream covers the last 30 minutes. Enable it with Tag Assistant, Tag Manager preview mode, or a debug_mode parameter set to true.
Check three things for each key event: it fires once, it fires only on success, and its parameters are filled in. One trap: setting debug_mode to false does not turn debug mode off. You have to remove the parameter.
How I help with GA4 conversion tracking
Measurement is the first step of my marketing and analytics work: GA4 and Tag Manager tracking, event tracking and live dashboards, then funnel analysis and CRM connections through tools like HubSpot, GoHighLevel and Zapier. I don’t run ads, but I set up the key events an ad buyer needs.
Clean tracking is also how I measure SEO results, including a 136% peak organic-traffic lift; you can see examples in my SEO portfolio and the work behind SEO powered by AI. If your site needs a rebuild first, see web design and development. I’m in Jacksonville, FL and work with businesses in Ponte Vedra Beach, Orange Park and across the US. If you want GA4 set up properly, that’s where to start.
Frequently asked questions
Are GA4 key events the same as conversions?
Not anymore. In Google Analytics, a key event is any event you mark as important to your business, and it shows up in your Analytics reports. A conversion now means an action you use in Google Ads to measure campaigns and guide bidding. You create a Google Ads conversion from a GA4 key event, which needs a linked Google Ads account. The underlying event is the same; what changes is the name and where it’s used. If you don’t run Google Ads, key events are all you need.
How long does it take for key events to show up in GA4 reports?
DebugView shows events within seconds, which is why it’s the right place to test. Standard reports take longer because Analytics has to process the data, so a newly marked key event can look empty for a while even when it fires correctly. Confirm the event in DebugView, wait for processing, then check the Events and Key events reports. If the event still doesn’t appear after a full day, check the event name for typos and confirm the Tag Manager container is published, not just saved.
Should I track form submissions with enhanced measurement or Google Tag Manager?
Start with enhanced measurement, then move to Tag Manager if it misfires. Enhanced measurement can collect form_start and form_submit automatically. Many modern forms submit through JavaScript, show an inline thank-you message or live inside an embedded widget, and those can be missed or double counted. In those cases I send a generate_lead event from Tag Manager on the real success signal, such as a thank-you page view. Then I mark generate_lead as the key event, so the number in reports means a lead that actually went through.
Does consent mode reduce the number of key events I see?
It can. When a visitor declines analytics cookies, GA4 can’t set or read its cookies for that person, so observed numbers drop. With advanced consent mode, tags still send cookieless pings, and Google can use behavioral modeling to estimate the gap, but only if your property meets its thresholds: at least 1,000 events a day with analytics storage denied for at least 7 days, and at least 1,000 daily users with it granted on 7 of the previous 28 days. Smaller sites often fall short, so read trends rather than exact counts.
Where should you start?
Pick your two or three most valuable actions, run them through Name, Fire, Mark, Prove, and ignore everything else until those numbers match your inbox. If you’d like a second pair of eyes on your setup, send me a note and I’ll tell you what I’d fix first.