How to Track Website Leads in GA4: A Plain-English Guide

Tracking website leads in Google Analytics 4 does not require you to become an analytics expert or to learn code. GA4 automatically collects form events for most websites, when someone submits a form. Your job is to take the one action that actually matters, a successful enquiry, and mark it as a key event so GA4 counts it as a lead you can see in reports and, later, send to Google Ads.

This guide is written for the small business owner who has a website, suspects it should be producing enquiries, and wants a plain-English answer to “how many leads is my site actually getting?”. It covers the three-step mental model, how to turn a form submission into a key event using the path Google itself documents, the reports to check, whether to also track phone calls, and four mistakes that make the numbers lie. If you have not yet worked out whether your problem is the traffic or the page, start with our guide to websites that get traffic but no leads, which separates the two before you measure anything. This article assumes you already know a lead is worth counting and want to know how.

What Counting Your Leads Actually Requires

In GA4 there is no “set a goal” box the way there was in the old Universal Analytics. Instead there are events, and any event can become a key event. A key event is “an event that measures an action that’s particularly important to the success of your business” . A form submission, a phone number click, a quote request: each is just an event until you decide it matters, and marking it as a key event is how you tell GA4 to treat it as a lead.

That gives you a three-step mental model that this whole guide follows:

1. Make sure the action fires an event. For most sites, GA4 already fires automatically. If yours does not, you create an event for it.
2. Mark that event as a key event. This is the “this counts as a lead” switch.
3. Look in the reports that count key events. Realtime when you are testing, then the standard reports for trends.

One naming trap stops many people before they start. What GA4 now calls key events, Google Ads still calls conversions, and the old Universal Analytics called goals. They are the same idea at different stages. If you search the GA4 interface for “conversion” and find nothing, this is why: it now lives under the name “key event”.

You also do not need to track everything. For a small business, two or three key events are usually enough: the contact form, a phone number click if calls are your main enquiry channel, and possibly a quote or booking action. Every extra key event you mark dilutes the data, because GA4 then counts more of your traffic as “converting”. Start small and add only what reflects a genuine enquiry.

First, a Quick Map of How GA4 Counts a Lead

Before touching any setting, it helps to see the whole path. When a visitor submits your contact form, GA4 records an event. If you have marked that event as a key event, GA4 records it as a key event too, which is what lets you count leads, see which pages and channels produced them, and build audiences from the people who did and did not enquire.

Three terms carry most of the confusion, so here they are side by side:

The practical implication for a small business is that your “how many leads did the website get this month” question becomes “how many times did my form key event fire this month”. Answering it well depends on the event being accurate, which is why the next two sections matter more than any report.

Start With What GA4 Tracks Automatically

The good news is that most small business websites do not need Google Tag Manager or custom code to begin tracking leads. GA4’s enhanced measurement is a set of events it collects for you, switched on per data stream, and it includes form interactions. One of those events matters for leads: when the user submits a form. It fires automatically once enhanced measurement is on, with no code on your side.

To confirm the switch is on, follow this path :

1. In Admin, under Data collection and modification, click Data streams.
2. Click the name of your web data stream.
3. Under Enhanced measurement, make sure the switch is on. You can switch individual options off and on; for leads you want Form interactions enabled.

The automatic event carries a few useful parameters, including the form’s HTML name, its ID, and the destination URL. For everyday use you can ignore the parameters; they matter only once you want to separate one form from another, which is exactly the next step.

Here is an honest caveat that many guides bury. Enhanced measurement is reliable for the common case, but not perfect. If your form is an AJAX form that updates the page without a reload, or a multi-step form, the automatic form submission may not fire the way you expect. And because form submission fires when the form is submitted, it can fire even when validation stopped the enquiry from going through. That is why the reliable target is not “any submit” but “a successful submission of your specific form”, which is the subject of the next section. For a plain contact form that reloads the page, the automatic event is usually good enough to start.

If you have not yet confirmed your form actually delivers enquiries to your inbox, fix that first. Our guide to contact forms that are not generating leads walks through testing whether submissions arrive before you invest in measuring them.

Turn a Successful Form Submission Into a Key Event

Marking every form submission as a lead is better than tracking nothing, but it counts near-misses. A visitor who clicks submit, gets a validation error, and gives up still fires form submission if the event is based on the submit action. The cleaner approach, and the one Google documents for measuring a lead-generation form, is to create an event that captures the submission of your specific form, then mark that event as a key event.

Follow these steps in the GA4 interface:

1. In Admin, under Data display, click Events.
2. Click Create event, then Create in the top right.
3. Name the custom event something clear, such as form submission.
4. In Matching conditions, add the condition. This copies the automatic event so it keeps firing when a form is submitted.
5. Add a second condition that narrows it to your form. The value is the HTML name attribute of your form’s form element, which you can find in the form’s code or by asking whoever built the site. If you have one enquiry form, this step stops other forms on the site from counting as leads.
6. Click Create. The event appears in the list once GA4 starts collecting it.

Now mark it as a key event:

1. In Admin, under Data display, click Key events.
2. Click New key event.
3. Enter the name of the event you just created, and click Save.

There is a simpler route if your form leads to a dedicated thank-you page, a confirmation page that only appears after a successful submission. In that case you can mark the page view of that thank-you page as a key event instead, because reaching it is strong evidence the enquiry went through. This approach is common and reliable, though it counts a reload of the thank-you page as another lead, so it suits forms whose submission reliably navigates to that page. If your form is plain and reloads on submit, the event-filtering route above is the more precise default.

Whichever route you use, verify it before trusting it. Go to Reports, Realtime, submit a test through the form, and check that your key event appears. Google’s own walkthrough sends you to the Realtime report, where the Event count by Event name card and the Key events by Event name card show what has been collected in the last 30 minutes. If you do not see it, wait a little longer for processing, then recheck that your matching conditions are correct.

One timing note: marking an event as a key event applies from that point forward. It does not reach back and reclassify history, and the same is true for counting-method changes. So set this up now, even if you are not sure you need the data yet. Every day you delay is a day of leads your reports will never show.

If your numbers now show plenty of submissions but you still hear nothing from the form, the problem is downstream of tracking. Our guide to website conversion audits helps you check the whole path from landing to enquiry.

The Three Reports That Answer “Is It Working?”

Once your key event is set up and verified, you do not need to live in GA4. Three reports answer the questions that matter.

Realtime is where you confirm a setup worked. It shows events collected in the last 30 minutes, and the Event count by Event name and Key events by Event name cards are where Google’s own walkthrough sends you to check that a test submission registered. Use it the day you set something up, and again whenever you change the form.

The Key events reports answer “how many leads this month, and from where?”. Many standard reports, such as Landing pages and User acquisition, include a Key events column and a session key event rate, and you can narrow by a specific key event to see counts for just your form. This is the report to open when you want to know whether last month’s change to the page moved the number.

Traffic acquisition answers “which channels and pages actually produce enquiries?”. It shows where visitors came from, paired against how many triggered your key event. This is where you find out whether your Google Business Profile sends people who enquire while your social traffic just bounces.

A note on patience: standard GA4 reports take time to process, so a freshly submitted test may not appear in them immediately. Google’s guidance is to wait a little longer for processing when an event does not show up. Realtime is instant; the standard reports catch up on their own schedule.

Finally, resist the urge to compare your numbers to a conversion-rate figure you read in an article. For a small business the only meaningful comparison is your own trend over time. Our guide to websites that get traffic but no leads makes the same point about benchmarks, and it is worth repeating: a modest, improving enquiry rate on the right visitors beats a headline number built on the wrong ones.

Should You Also Track Phone Calls?

For local service businesses, the phone is often the real enquiry channel, and the form is secondary. A plumber or electrician who only tracks form submissions is measuring half their leads. The question is how to count a phone call in GA4 without a paid call-tracking service.

GA4 does not hand you a “phone call” key event out of the box, but it does give you the building blocks. Enhanced measurement tracks outbound clicks, defined as each time a user clicks a link that leads away from the current domain to another website. A tap-to-call link, one that dials a phone number from a mobile phone, is exactly that kind of outbound link. So the practical approach for a mobile-first local site is to count clicks on your phone-number links as a key event.

To do that you combine the same mechanism as the form: create an event that fires when a click happens on a link whose destination starts with tel:, then mark it as a key event. On a desktop site where the number is shown as text rather than a link, there is no click to count, which is why a phone key event makes most sense if your visitors reach you by tapping a call button on their phone. This is a reasonable assembly of GA4’s own click and outbound-click mechanisms, not a Google-provided one-click “track calls” setting, so test it in Realtime the same way before relying on it.

There is a hard limit worth naming. GA4 can count that someone tapped your number; it cannot tell you whether the call became a paying job. If you need to know which enquiries turn into revenue, you need a dedicated call-tracking service that records and transcribes calls. For most small businesses that is a later step, taken once form and click tracking are already telling a clear story.

If you are weighing whether calls or forms are your real conversion path, our guide to mobile UX and conversion covers how tap-to-call and other mobile actions behave, which helps you decide what is worth counting.

Why the Count Looks Different From Your Old Analytics

If you moved to GA4 from Universal Analytics, your new lead count may look higher than the old one, and that is often not because you gained leads. It is because the two systems count differently. GA4’s default counting method for a key event is once per event: if one person triggers the same key event five times in a single session, GA4 counts five key events. Universal Analytics-style goals, by contrast, counted once per session.

Google spells out the default: once per session is the default for key events created from migrated Universal Analytics goals, while once per event is the default for everything else. So a brand-new lead key event, like the one in this guide, counts every occurrence by default.

If you want the old feel, you can change it. Under Admin, Data display, Events, open the Key events tab, find the row for your event, click the menu to its right, choose Change counting method, and select Once per session.

Which should you choose? They answer different questions. Once per event shows real behaviour: how many times people actually performed the action, useful when a visitor might legitimately send more than one enquiry in a visit. Once per session answers “how many sessions ended in at least one enquiry”, which is closer to the old mental model and often a better fit for a lead form where one enquiry per visit is the norm. Pick one, stick with it, and do not switch back and forth, because a change applies only to future data and never rewrites the past.

Four Mistakes That Make the Numbers Lie

Tracked leads are only useful if the number is honest. Four mistakes quietly corrupt it, and the first two are by far the most common.

• Counting a button click as a success. If your key event fires on any submit, validation failures and abandoned attempts count as leads. The fix is the earlier step: filter to a successful submission of your specific form, or use a thank-you page.
• Forgetting GA4 counts repeats. One person submitting twice in a session can read as two leads under the default once-per-event method. Not a bug, a counting choice. Switch to once per session if one enquiry per visit is your reality.
• Trusting a form event that never fires. AJAX and multi-step forms can defeat automatic form submission. The Realtime report is your check: if you submit a real test and no event appears, enhanced measurement is not catching your form, and you need a developer or a Tag Manager setup.
• Benchmarking against an article. “Average conversion rates” from other industries tell you nothing about your town and your offer. Compare this month to last month on the same definition, and make one change at a time. Our guide to websites that get traffic but no leads explains why your own trend beats any published benchmark.

Fix the first two and your lead count becomes trustworthy enough to make decisions on. If you fix those and the honest number is still low, the tracking was not the problem, and our website conversion audit is the structured way to find where the enquiries leak.

Frequently Asked Questions

Do I need Google Tag Manager to track leads in GA4?

No. Most small business websites can start with GA4’s enhanced measurement, which collects data automatically, and the route Google documents for turning a specific form into a key event uses the Events page in Admin, not Tag Manager. Tag Manager becomes useful later, when you need to track AJAX forms, multi-step flows, or detailed button clicks that enhanced measurement cannot see.

How many leads should I track in GA4?

Start with two or three that genuinely mean business, such as a form submission and a phone number click. Every extra key event you mark makes more of your traffic count as “converting”, which dilutes the signal. You can always add more later.

What is a key event versus a conversion in GA4?

They are the same thing under two names. GA4 renamed conversions to key events in its interface, while Google Ads still uses “conversion”. An old Universal Analytics goal is now a key event. If you cannot find “conversion” in the GA4 menu, look for “key events” instead.

Why does my GA4 lead count not match my email inbox?

Usually one of three reasons: the event fires on any submit, so validation failures count; the same person submitting twice in a session counts twice under the default once-per-event method; or the automatic form event is not firing for your form type. Filter to a successful submission, decide on a counting method, and verify with the Realtime report.

How do I send my tracked leads to Google Ads?

You can create a conversion in Google Ads from a GA4 key event and manage its settings from either interface, which keeps the counts consistent between Google Ads and Analytics. That is a later step; this guide is about getting the count right first.

Does tracking leads in GA4 work on mobile?

Yes. Form events and key events work the same regardless of device. For local businesses whose mobile visitors tap a call button rather than fill a form, the phone link click can be counted through the outbound click event, which enhanced measurement tracks.

Conclusion

Tracking website leads in GA4 comes down to three steps: make sure the action fires an event, mark it as a key event, and verify it in the Realtime report. Start with what GA4 tracks automatically, filter the form submission down to your actual successful enquiry, and keep the count honest by deciding whether one lead per session is your reality. For local businesses, count the phone clicks too, because the form is often only half the story. Once the number is trustworthy, judge it against your own trend, not a figure from an article. If you would like a hand setting up lead tracking you can actually read, or help fixing what it reveals, talk to our Adelaide team. Bilingual English & Chinese support.