It is the first Monday of the month, and GA4 says your website drove 212 key events. Your inbox and call log show 19 real inquiries.
Nobody is lying. GA4 is counting scrolls, outbound clicks and contact page views as if they were leads.
GA4 key events are the few actions you tell Google Analytics matter most. For most small businesses, the right number is two to four: real inquiries and real sales.
A key event is any GA4 event you flag as important, such as a submitted quote form or a completed purchase. Google renamed GA4 conversions to key events, so both terms describe the same setting.
Google defines a key event as one that measures an action that's particularly important to the success of your business. The word doing the work is "particularly." Every event you promote competes for attention, and if you run ads, it shapes what the ad platform chases.
Mark only the actions that create revenue or start a real sales conversation. Scrolls, video plays and page views never qualify.
Run every event through a two-question test before you promote it. Would you pay to get more of this action? Could you explain it to your accountant without the word "engagement"?
If either answer is no, keep it as a regular event. You can still report on it, but it won't inflate the number everyone reads first.
| Business type | Mark as key events | Leave as regular events |
|---|---|---|
| Local service business | generate_lead on a confirmed form, phone clicks, booking confirmations | Scrolls, contact page views, outbound clicks |
| Online store | purchase, plus begin_checkout only while orders are too few to learn from | add_to_cart, view_item, scrolls |
| Restaurant or retail shop | Completed reservations or online orders, phone and directions clicks | Menu views, scrolls, video plays |
| B2B or consulting firm | Demo or consultation requests, gated guide downloads if sales follows up | Blog page views, file downloads, newsletter signups |
A contractor and a bakery won't share a list, and they shouldn't. What they share is the size of it: short enough to recite from memory.
The form_submit event comes from GA4's enhanced measurement, and it's a blunt instrument. It can fire for site search boxes, newsletter fields and login forms. It can also miss forms that submit without loading a new page.
Keep enhanced measurement on anyway. Google lists what enhanced measurement collects automatically, from page views and scrolls to outbound clicks and form interactions. That is useful context, but none of it proves a person asked for a quote.
Phone calls are the other blind spot. Outbound click tracking is built for links to other websites, so a tap on your phone number needs its own trigger. If calls are most of your leads, that gap is a common cause of traffic that grows while sales stay flat.
You need two things: an event that fires only when the action truly happens, and the key event toggle switched on for it. Work through these five steps in order.
1. Pick the confirmation moment. A thank-you page URL is the most reliable trigger. If your form shows an inline success message instead, ask your developer or form tool to push an event when it appears.
2. Create the event. In Google Tag Manager, add a GA4 event tag named generate_lead with that trigger. Without Tag Manager, use Create event in GA4 Admin, based on page_view where the page location contains your thank-you URL.
3. Add phone clicks. Build a click trigger for links that start with tel: and send an event with a clear name, such as phone_click.
4. Test it. Submit the form yourself and watch the Realtime report or DebugView. One submission should produce one event.
5. Mark it as a key event. In Admin, open the Events list, find the event and mark it as a key event. Then switch off any key events that failed the two-question test.
Stick to Google's recommended event names where they exist, such as generate_lead and purchase. Anyone who inherits the account later will know what they're looking at.
Use once per session for leads and once per event for purchases. A visitor who submits your quote form twice in one visit is still one lead, while two orders are two sales.
Google recommends once per event and labels once per session as legacy. For lead counts, override that default, because double submissions quietly overstate lead volume.
Once GA4 and Google Ads are linked, you can import any GA4 key event as a Google Ads conversion. Whatever you set as a primary conversion becomes the goal automated bidding works toward.
Feed it scrolls and page views, and it will find you cheap scrollers. Feed it real leads, and it looks for more of those.
Clean conversion data comes before any choice in our guide to choosing a Google Ads bidding strategy. A clean lead event also lets you exclude people who already converted from retargeting campaigns.
Two to four. Each one should be an action you would pay to get more of. Think quote requests, phone calls, bookings and purchases.
Yes, in GA4. Google renamed GA4 conversions to key events, while Google Ads still uses the word conversion for the goals your campaigns optimize toward.
No. It can fire on search boxes, newsletter fields and login forms. Use a generate_lead event that fires only on a confirmed submission.
Usually it is one of three causes: noisy events marked as key events, lead events counted once per event, or test submissions. Check them in that order.
You can track taps on a tel: link with a click trigger in Google Tag Manager. That records the tap, not whether the call connected, so treat it as a strong signal rather than a confirmed lead.
Same dashboard, one month later. GA4 shows 23 key events, and your inbox and call log show 21 inquiries.
The gap is small enough to explain. Your ad account is now optimizing toward real leads instead of scrolls.
Your next step takes 20 minutes: open Admin, list every event marked as a key event, and run each one through the two-question test.
.png)
