Most small business GA4 properties track plenty of events and very few of the ones that matter. Page views, scrolls and outbound clicks fill the reports, while the actual enquiry — the form, the call, the booking — is either missing or counted twice. GA4 key events are how you tell Analytics which actions are worth something to the business, and getting them right is what makes your reports, and any Google Ads campaign built on them, worth trusting.
This guide assumes GA4 is installed and events are flowing, ideally through Google Tag Manager. If not, start with the conversion tracking setup guide and the Google Tag Manager install for WordPress, then come back. As always with Google’s tools, menu labels move around; I describe each setting by what it does so the instructions survive the next interface change.
Key events vs conversions: what changed
In March 2024 Google renamed “conversions” in GA4 to “key events”. The idea was to end the confusion between two tools using the same word for slightly different things. Since then:
| Key events (GA4) | Conversions (Google Ads) | |
|---|---|---|
| What it is | An event you mark in GA4 as important | A conversion action in Google Ads |
| Where it lives | Google Analytics 4 property | Google Ads account |
| Used for | Reporting, analysis, audiences | Bidding, campaign optimisation, ads reporting |
| Source | Your website or app events | The Google Ads tag, imported GA4 key events, offline imports and more |
| Credited to | The date the event happened | The date of the ad interaction |
So when someone asks “how many GA4 conversions did we get?”, the accurate answer is now “how many key events” — and “conversions” belong to Google Ads. You will still see older guides, plugins and agencies using the old wording. The underlying setup is the same; only the label changed.
Which actions should be key events
A key event should be an action that is a real step towards revenue. If you would not be pleased to see one more of it tomorrow, it is not a key event. For most service businesses the list is short:
| Event | Key event? | Notes |
|---|---|---|
Lead form submitted (generate_lead) |
Yes | The core key event for most service sites |
| Booking made | Yes | Fire on confirmation, not on opening the calendar |
| Phone call from the site | Usually | A tap on a tel: link is intent, not a call; call tracking measures real calls |
Purchase (purchase) |
Yes | The main key event for e-commerce; often marked by default |
| Begin checkout, add to cart | Rarely | Useful funnel events, but they inflate key event totals |
| Page views, scrolls, outbound clicks | No | Engagement signals, not business outcomes |
Use Google’s recommended event names where one fits — generate_lead, purchase, sign_up and so on — because GA4 understands their parameters and some reports and integrations expect them. Google also lists recommended lead-stage events such as qualify_lead and close_convert_lead for businesses that send CRM outcomes back to Analytics.
For phone calls, a click on a phone link only tells you someone tried to call. If calls are a big part of your enquiries, call tracking will give you actual answered calls, which make a far better key event.
Keep the list short. As a rule of thumb from practice, a small business needs two to five key events. GA4 also caps how many key events a property can have (the limit has been 30 for standard properties; check the current figure). More key events mostly means less clarity about which number to watch.
How to create and mark GA4 key events
An event has to exist before it can be a key event. The cleanest way to send it is from Tag Manager — a GA4 event tag that fires when the form’s success message appears or the thank-you page loads. Once the event is arriving in GA4, the steps are:
-
Confirm the event is being collected.
Trigger it yourself, then look for it in GA4’s Realtime report or in DebugView (with Tag Manager preview mode or debug mode on). Check the parameters too, such as
form_nameorvalue. -
Find it in the events list.
In the GA4 admin area, open the list of events under the data display settings. New events can take up to a day to appear in this list.
-
Mark it as a key event.
Use the toggle or star beside the event. Alternatively, open the key events section and create a new key event by typing the exact event name — useful when you know the name before the first event arrives.
-
Choose the counting method.
Key events can be counted once per event or once per session. For lead forms, once per session stops one keen visitor who submits twice from looking like two leads; for purchases, once per event is right because each order matters.
-
Add a value where it helps.
Send a
valueandcurrencyparameter with the event, or set a default value if your property offers it. Even a rough average lead value makes reports and bidding more meaningful than counting every lead as equal.
When you cannot change the tagging
If the event you need does not exist and you cannot edit Tag Manager, GA4 can create an event from an existing one. For example, a new event named generate_lead whenever a page_view occurs on a URL containing /thank-you/. It works, but it is fragile: anyone reloading or bookmarking the thank-you page creates a lead. Tag Manager firing on the actual form success is more reliable.
Key events are not retroactive. Marking an event today does not turn last month’s events into key events. Set them up before a campaign or redesign launches, and annotate the date so nobody misreads the jump in reports.
Importing GA4 key events to Google Ads
If you run Google Ads, you can import GA4 key events as Google Ads conversion actions, so campaigns bid towards the same outcomes you report on. The general process:
- Link the GA4 property to the Google Ads account from GA4’s product links settings. You need the right access level in both accounts.
- In Google Ads, create a new conversion action and choose to import from Google Analytics 4 (web).
- Select the key events you want. Only key events are offered for import, which is another reason to mark them carefully.
- Decide which conversion actions are primary (used for bidding and the main Conversions column) and which are secondary (observed only).
- Check that you are not importing an action that the Google Ads tag already tracks, or the same lead is counted twice and bidding is skewed.
For local service campaigns, the bidding strategy is only as good as the conversion actions it learns from. The Google Ads guide for local service businesses covers how to choose them for small budgets.
Why GA4 and Google Ads numbers never match
Expect differences. They come from how each tool counts, not from one being wrong:
- Date of credit. Google Ads attributes a conversion to the date of the ad click; GA4 reports the key event on the day it happened.
- Attribution. Each tool applies its own attribution model and lookback windows, so the same lead can be credited to different channels.
- Scope. GA4 counts key events from every channel; imported conversions in Google Ads only include those it can tie to ad interactions.
- Counting method. Once per session in one place and once per event in another produces different totals.
- Consent. Where visitors decline cookies, modelled data and observed data differ by tool. The Consent Mode v2 guide explains how rejected sessions are handled.
A gap of a few leads a month is normal. A gap where Ads shows twice as many conversions as GA4 has key events usually means double counting — two tags tracking the same form — or a key event firing on the wrong trigger.
Reporting on key events
Once set up, GA4 key events appear as a metric across the standard reports, alongside session and user key event rates. The most useful views for a small business are traffic acquisition with key events by channel, landing pages with key events, and a simple exploration that breaks key events down by event name, so form leads and bookings are not lumped together. Check them monthly against the enquiries recorded in your CRM; that comparison is what tells you the tracking still works.
GA4 key event mistakes
- Marking page views, scrolls or clicks as key events, so totals look healthy and mean nothing.
- Firing the lead event when the form is opened or the button is clicked, not when submission succeeds.
- Both a GA4-imported conversion and a Google Ads tag tracking the same lead.
- Counting lead forms once per event, so double submissions look like extra leads.
- Thank-you page key events that fire on every reload.
- No value on any key event, so every enquiry looks equally important.
- Never testing again after a theme, form plugin or consent banner change.
Further reading: Google Analytics Help · GA4 recommended events reference · Google Ads Help.
FAQ
What is the difference between key events and conversions in GA4?
In March 2024 Google renamed GA4 conversions to key events. A key event is an event you mark in GA4 as important to your business, such as a lead form or a purchase. Conversions now refers to conversion actions in Google Ads, which can be imported from GA4 key events and are used for bidding and ads reporting. Same underlying action, two tools, two names.
How do I mark a key event in GA4?
Make sure the event is already being collected, then open the events list in the GA4 admin area and mark that event as a key event with the toggle or star next to it. You can also create a key event in advance by entering the exact event name. Key events only count from the moment they are marked; GA4 does not apply them to past data.
How do I import GA4 key events to Google Ads?
Link your GA4 property to your Google Ads account, then in Google Ads create a new conversion action and choose to import from Google Analytics 4. Select the key events you want, decide which should be primary for bidding, and avoid importing an action that the Google Ads tag already tracks, or it will be counted twice.
Why don’t my GA4 key events match my Google Ads conversions?
The tools measure differently. Google Ads credits a conversion to the date of the ad click and uses its own attribution and conversion windows, while GA4 reports key events on the date they happened using the property’s attribution settings. Counting method, consent modelling and imports that only include ad-driven traffic widen the gap. Small differences are normal; large ones usually mean a setup problem.
Want your key events, Tag Manager triggers and Google Ads imports set up so the numbers can be trusted? See the tracking and analytics services — I test every key event against real submissions before handing it over.