GA4 Key Events for Lead-Gen Sites: What to Track and Why

Getting GA4 key events for lead gen right is the difference between knowing whether your website earns enquiries and just watching traffic go up and down. For a lead-generation site, the visit was never the point — the form submission, the phone call, the booked consultation is. This guide explains what a key event actually is in GA4, which ones a lead-gen site should track, how to mark an event as a key event, and how to avoid the over-counting that quietly inflates every number you report.

Most small business sites have GA4 installed and measuring sessions out of the box. Far fewer have told GA4 which of those sessions resulted in something that matters. Until you do, your analytics can tell you how many people arrived but not how many turned into a potential customer — which, for lead generation, is the only question worth answering.

What a key event is in GA4

In GA4, almost everything is an event. A page view is an event. A scroll is an event. A click on an outbound link is an event. By default GA4 fires a steady stream of these automatically, and they pile up into the totals you see in your reports. The problem is that not all events are equal: a scroll down your About page is not worth the same as someone submitting a contact form.

A key event is simply an event you have told GA4 to treat as important — one that represents a meaningful outcome for your business. Marking an event as a key event is how you separate the signal from the background noise. Once an event is flagged this way, GA4 starts counting it as a key event, surfacing it in conversion-focused reports, and making it available for attribution and audience-building.

If you used the older Universal Analytics, you may remember “goals.” Key events are the modern equivalent of that idea, rebuilt on GA4’s event-based model. Google renamed what used to be called “conversions” in the GA4 interface to “key events” in late 2024, reserving the word conversion for the advertising side — the key events you import into Google Ads to optimise campaigns. For everyday analytics, the term you will see in GA4 is key event.

The key events lead-gen sites should track

A lead-generation site has a short, specific list of things that count. The discipline is in keeping that list short. The goal is not to mark everything as a key event — it is to mark the handful of actions that genuinely indicate someone is becoming a lead.

Form submissions

For most lead-gen sites this is the central one. A completed contact form, quote request, or newsletter sign-up is the clearest signal that a visitor has raised a hand. GA4 form submissions can be captured automatically through enhanced measurement, but the automatic version is unreliable across custom forms and form plugins. The dependable approach is a deliberate event — often called something like generate_lead or form_submit — that fires only on the confirmation step or thank-you page, so you are counting genuine completions rather than attempts.

Phone calls

Plenty of lead-gen happens over the phone, and a click on a tap-to-call link is a strong intent signal worth capturing. A click on a tel: link can be tracked as an event and marked as a key event. Be honest with yourself about what it measures: a click means someone intended to call, not that a conversation happened. It is a useful proxy, not a confirmed lead — treat it accordingly when you read the numbers.

Bookings and appointments

If your site uses a scheduling tool — Calendly, Acuity, an embedded booking widget — a completed booking is one of the highest-value actions on the site, because it represents a person who has committed time. These often happen on a third-party domain or inside an iframe, which makes them easy to miss. Confirm the booking tool can pass an event back to GA4, or track the redirect to its confirmation page, so the booking actually registers as a key event.

Beyond these three, some sites reasonably add a downloaded resource behind an email gate, or a started-but-abandoned form as a diagnostic. The test is always the same: does this action mean someone moved closer to becoming a customer? If yes, it is a candidate. If not, leave it as an ordinary event.

How to mark an event as a key event

Once the right event is firing, marking it is quick. In GA4, the steps are straightforward.

First, confirm the event is actually being collected. Open Admin › Events (under Data display) and check that your event — say, generate_lead — appears in the list. Realtime and the DebugView are the fastest ways to verify it fires when you complete the action yourself. An event has to be seen by GA4 at least once before you can flag it.

Second, mark it. In the same Events table, find your event and toggle the Mark as key event switch. That is the entire action. From that point forward GA4 counts every future instance as a key event. One important caveat: marking a key event is not retroactive — it does not reclassify events that were collected before you flipped the switch, so do this early.

If the action happens somewhere GA4 cannot see by default — a thank-you page on another domain, a booking confirmation in an iframe — you may need to create the event first, either through Google Tag Manager or GA4’s own event-creation rules, before it shows up to be marked. The marking step itself never changes; getting the event to fire reliably is the part that takes care.

Avoiding over-counting

Here is where many lead-gen setups quietly go wrong. GA4 will faithfully count exactly what you tell it to, and if you are not careful, that includes counting the same lead several times.

The classic culprit is firing the event on the wrong trigger. If your generate_lead event fires on a button click rather than on a successful submission, every misclick, every validation error, and every double-tap inflates the count. Fire key events on confirmation — the thank-you page or a verified success state — not on the attempt.

A second culprit is double-counting across overlapping events. If enhanced measurement is automatically capturing form interactions and you have also built a custom form_submit event, a single submission can register twice. Pick one source of truth for each action and turn the other off.

A third is the thank-you page refresh. If someone lands on your confirmation page, then reloads it or returns to it later, a page-based key event can fire again for the same lead. Where you can, tie the event to the submission itself rather than to merely viewing the confirmation page.

An inflated key event count doesn’t just flatter you — it teaches you the wrong lessons about which channels actually work.

Over-counting is not a harmless vanity problem. Every downstream decision — which campaign to fund, which page to fix, whether the month was good — rests on these numbers. One lead-gen site we wrote about watched its reported conversions collapse overnight and assumed the business was failing, when the real story was a measurement change. The cautionary tale is worth reading: When Conversions Fell Off a Cliff.

Connecting key events to attribution

Counting leads is only half the value. The other half is knowing where they came from — which is what attribution does. Until an event is marked as a key event, GA4 has nothing to attribute; once it is, every key event can be traced back to the channels and campaigns that contributed to it.

GA4 uses an attribution model to decide how credit for a key event is shared across the touchpoints in a visitor’s journey. A lead rarely arrives on a single click. Someone might find you through organic search, leave, return a week later from a newsletter, and finally submit a form after a direct visit. The attribution model decides how much credit each of those steps receives. GA4’s default is data-driven attribution, which distributes credit based on observed patterns rather than crediting only the last click.

This is exactly why clean key events matter so much. Attribution can only be as trustworthy as the events feeding it. If your key event over-counts, attribution dutifully spreads inflated credit across your channels, and you end up over-investing in whatever happened to be involved in the phantom leads. Get the key event right first; the attribution becomes meaningful only then.

Read together, key events and attribution answer the two questions a lead-gen site actually has: how many real enquiries did we earn, and what produced them? Sessions and pageviews never answered either. They were always a means to that end.

Where WebSignalytics fits

Setting key events up correctly is a one-time job. Keeping an eye on what they tell you, week after week, is the part that quietly slips. That is the gap WebSignalytics was built to close.

It connects to your Google Analytics in the background and emails you a plain-language report every Monday: how many leads came in, whether that is up or down, where they came from, and what is worth your attention. No dashboards, no logging in. If your key event count moves sharply — in either direction — you hear about it in a sentence, with a plausible explanation, rather than discovering it three weeks later in a report you never open.

The data was always there once your key events are set. WebSignalytics reads it for you and tells you what it means — in a paragraph, not a spreadsheet.