GA4 lead tracking means recording each enquiry on your website (a form submission, a call click, a booking request) as its own named event, then marking that event as a key event so GA4 and Google Ads can report on it. Out of the box, GA4 does not know what a lead is on your site. You have to tell it. This guide shows you how, in the order we do it for clients, with the mistakes that quietly wreck the data.
TL;DR
-
Create a dedicated event for each lead action, such as
generate_leadfor a form submission, and mark it as a key event in Admin. -
Don’t rely on automatic tracking. Newsletter signups and real enquiries need different event names, or your lead count is inflated.
-
Test with DebugView and Tag Assistant before you trust a single number, and re-check after every website or form change.
-
Collect only what you need and say so in your privacy policy. The OAIC treats privacy as an ongoing job, not a one-off setup.
-
If leads are the goal, wire GA4 into Google Ads so bidding learns from real enquiries, not just clicks.
Table of Contents
What counts as a lead in GA4
Before you touch any settings, write down what a lead is for your business. For a Wollongong electrician, it might be a quote form, a tap on the phone number and a booking through an online calendar. For a B2B software company, it might be a demo request only.
GA4 is event-based. Every interaction is an event, and a small number of events can be flagged as key events (the name Google now uses for what used to be called conversions). Google’s help page on measuring key events explains that key events let you see user paths, calculate key event rates and enable bidding in linked advertising accounts.
A useful starting list of lead actions:
| Lead action | Suggested event name | Typical value to you |
|---|---|---|
| Quote or contact form submitted | generate_lead |
High |
| Phone number tapped on mobile | click_call |
Medium to high |
| Email link clicked | click_email |
Medium |
| Booking confirmed | booking_complete |
High |
| Brochure or guide downloaded | file_download |
Low to medium |
| Newsletter signup | newsletter_signup |
Low (keep separate) |
The last row matters. If a newsletter signup and a quote request both fire the same event, you cannot tell which marketing activity is actually producing work.
Why automatic tracking isn’t enough
GA4 has enhanced measurement, which switches on page views, scrolls, outbound clicks, file downloads and some form interactions without any code. It’s a handy baseline, but it is built to be generic.
The form interaction events it collects tell you someone started or submitted a form somewhere on the page. They don’t tell you which form, whether the submission succeeded, or whether the person was a buyer or someone asking about your opening hours. For lead work, you want a custom event name tied to a specific form, for example, lead_form_submit for the quote form only. That one change filters out the noise and makes your lead count something you can show to a business owner without wincing.
Three common ways automatic tracking misleads you:
-
Button clicks counted as submissions. The visitor clicks Submit, the form shows a validation error, and GA4 still logs it.
-
Multiple forms, one event. The footer newsletter box and the main enquiry form look identical in the data.
-
Double counting. A thank-you page that reloads, or a tag firing on both the click and the page view, inflates numbers.
Use Google’s recommended lead events
Google publishes a list of recommended events with set names and parameters. For lead generation, the relevant ones follow the whole life of an enquiry: generate_lead when someone submits a form, qualify_lead when you decide they are a good fit, working_lead when your team is actively talking to them, and close_convert_lead when they become a customer.
Using these exact names matters. GA4 uses them to populate its lead-focused reporting and to build suggested audiences. Custom names still work for your own reports, but you lose the built-in extras.
The first event generate_leadfires from your website. The other three usually come from your CRM or your sales process, which means they have to be sent back to GA4 later. That’s where the Measurement Protocol comes in, covered below. If you want a broader look at how a business site becomes a steady source of enquiries, this piece on turning a business website into leads is worth a read alongside the technical steps here.
Most small businesses never need the last three events. If you have two staff and a handful of enquiries a week, generate_lead plus a call event is plenty. Add the later stages once you have a CRM and someone willing to update it.
Setting it up step by step
The cleanest method for most sites is Google Tag Manager. Wix and WordPress sites can also send events through built-in integrations or plugins, but the logic is the same.
1. Pick a reliable trigger
The best trigger is one that only fires when the form actually succeeds. In order of reliability:
-
A thank-you page that only appears after a successful submission. Simple and sturdy.
-
A form submission trigger built into your form plugin or Wix Forms, which fires on a confirmed success message.
-
A data layer push from the form’s own code. Best accuracy; needs a developer.
Avoid triggers that fire on a button click. They count attempts, not leads.
2. Create the event
In Tag Manager, create a GA4 event tag. Name it generate_lead (or your custom name such as lead_form_submit), point it at your GA4 measurement ID and attach the trigger from step 1. Add a parameter such as form_id or form_name so you can separate your quote form from your contact form later.
3. Mark it as a key event
Once GA4 has received the event at least once, go to Admin, then Data display, then Events, and switch on the key event toggle for it. Google’s guide to measuring key events walks through the same process for lead forms. You can also create the key event ahead of time from the Key events page if you want it flagged from the first hit.
Only mark the events that represent real business value. If you mark ten things as key events, the number stops meaning anything.
4. Test before you publish
Open Tag Manager’s preview mode (Tag Assistant), submit your own form, and confirm the tag fires once. Then open DebugView in GA4 and check the event arrives with your parameters. Submit a test with a deliberate error, such as an empty required field, and make sure nothing fires.
Before you go live, do all of these:
-
Submit the form once and confirm exactly one event.
-
Submit it with an error and confirm zero events.
-
Check the event on mobile as well as desktop.
-
Filter out your own team’s traffic so internal tests don’t pollute reports.
-
Write the date of the change in a note, so a jump in numbers later has an explanation.
Tracking calls, chats and bookings
A lot of local enquiries never touch a form. Plumbers, dentists, mechanics and accountants often get most of their work by phone.
For click-to-call, set a trigger on clicks where the link URL starts with tel: and send a click_call event. This counts taps, not answered calls, so treat it as a strong signal rather than a confirmed lead. If phone calls are your main channel, call tracking numbers or Google Ads call assets give you better data than a tap count.
For chat widgets, check whether the vendor offers a GA4 integration or a data layer event when a chat starts. For online booking tools, the cleanest option is a confirmation page or a webhook, so the booking is recorded only when it is actually made.
Whatever you add, keep the event names tidy. A short, consistent naming style (lowercase, underscores, no spaces) saves hours later when you build reports.
Sending offline lead stages back to GA4
A form fill is not a sale. If you want GA4 to learn which leads turn into customers, you need to feed those later stages back in. That’s what qualify_lead, working_lead and close_convert_lead are for.
The usual route is the Measurement Protocol, which lets your server or CRM send events directly to GA4. Two details trip people up. The payload needs a valid client or session reference so the event can be tied to the original visitor, and it needs engagement_time_msec for the event to show up in real-time and standard engagement reports. Leave those out, and you’ll swear the events were never sent, when really they arrived and went unreported.
If events sent this way go missing, check the Measurement Protocol payload first, before you blame the tag on the website. It’s the step most often overlooked when troubleshooting.
This is a more advanced job. For a small business, a monthly spreadsheet review of enquiries against actual jobs often delivers 80 per cent of the value for a fraction of the effort.
Connect GA4 to Google Ads
If you run paid search, key events do more than fill a report. When GA4 is linked to Google Ads, the key events you’ve marked can be imported and used for bidding. Without clean, correctly attributed lead events, the bidding system has nothing reliable to learn from, so it optimises for clicks or the wrong actions.
That’s why messy tracking is expensive. If your newsletter signups are counted as leads, Google Ads will happily find you more newsletter signups.
Google also offers enhanced conversions, which supplement your key events with hashed customer data such as an email address to improve measurement accuracy. It can help, but it involves user-provided data, so read the privacy section below before switching it on.
If you’re weighing up what paid search actually costs locally, our guide to Google Ads benchmarks for Australia gives realistic cost-per-click ranges, and our paid advertising and PPC services page explains how we manage campaigns.
Privacy: What Australian businesses need to do
This is the part many how-to guides skip, because they are written for a global audience.
The Office of the Australian Information Commissioner (OAIC) says in its guidance on tracking pixels that the Privacy Act does not prohibit tracking pixels, but organisations using them need to do due diligence and follow the Australian Privacy Principles. In practice, that means:
-
Collect only what you need. Don’t capture form field contents, names or email addresses in your analytics events. Send the event name and a form ID, not the person’s details.
-
Be transparent. Your privacy policy should state that you use Google Analytics, what it collects and why. Note a deadline: from 10 December 2026, privacy policies must also disclose any automated decision-making that significantly affects people’s rights or interests, including the kinds of personal information involved. Our guide to an APP-compliant privacy policy covers what to include.
-
Avoid sensitive information. Health, financial hardship and similar details should never end up in event parameters or URLs. Watch for form pages that put answers into the URL, because GA4 records page URLs.
-
Review regularly. The OAIC frames privacy as an ongoing obligation. Whenever you turn on a new feature, such as enhanced conversions, revisit your policy and settings.
One point from the OAIC guidance is worth remembering: analytics data becomes personal information when a person is reasonably identifiable. A clean event with no personal data in it keeps you well clear of that line. If your business handles health, legal or financial enquiries, check your obligations with a privacy lawyer or your industry body before enabling any advanced data sharing.
Perspective: What we see on real client accounts
We’ve been building websites and running SEO for 12 years, and the same tracking problem shows up again and again. A business pays for SEO or ads, the monthly report shows ‘conversions’, and nobody can say which ones were real enquiries.
When we audit an account, we start with the form. Nine times out of ten, there’s an event firing on the wrong thing, or two forms sharing one event. Fixing that is a ten-minute job that changes how the whole campaign looks.
Our advice for small and mid-sized businesses is to keep it boring. One clear event for the main enquiry form, one for calls, a test after every site change, and a monthly check against your inbox and phone log. If GA4 says you got 40 leads and your team remembers 15 real enquiries, trust your team and go fix the tracking.
The same applies to AI search. As more people find businesses through AI answers, clean lead data tells you which pages and topics actually produce enquiries, so you can put effort where it pays. Tracking is the foundation, not the finishing touch.
Getting help with the setup
If you’d rather not spend a weekend inside Tag Manager, we can set it up as part of a website build or an SEO plan. Our Wix web design is a $590 one-off, with forms and tracking planned from the start. If you want ongoing search work with proper reporting, our SEO Essentials plans start at $170 per month, and our Lead Generation Plan is $990 per month. All of our contracts are no-lock-in, so you can see the numbers first.
Common GA4 lead tracking mistakes
A quick checklist to run through your own account:
-
Everything is a key event. Pick the few that matter.
-
No form identifier. You can’t tell which form produced the lead.
-
Thank-you page reachable directly. If anyone can type the URL, tests and bookmarks inflate your count. Make it show only after a real submission.
-
Internal traffic not excluded. Your own testing counts as leads.
-
Cross-domain gaps. If your booking tool lives on a different domain, sessions can break, and leads get credited to ‘direct’ or to the booking tool itself.
-
No review after site changes. A new theme, form plugin or page builder update can silently stop the tag firing. Check the numbers monthly, and if leads fall to zero overnight, suspect tracking before demand.
-
Personal data in parameters. Keep names and emails out of events.
If you’re comparing against pre-2023 benchmarks from Universal Analytics, don’t expect the numbers to line up. GA4 counts sessions and conversions differently, so treat anything from the UA era as a separate baseline rather than a like-for-like comparison.
FAQs
Do I need Google Tag Manager for GA4 lead tracking?
No, but it makes life easier. Some website builders and form plugins can send GA4 events directly. Tag Manager gives you more control, a preview mode for testing, and one place to manage every tag.
How long does it take for a key event to show in GA4 reports?
Events show in DebugView and the real-time report within moments, but standard reports can take a day or so to update. Mark the event as a key event once it has arrived at least once, and give reports time before you judge the results.
Is generate_lead the same as a conversion?
It’s a recommended event name for form submissions. It only becomes a key event, which is what GA4 now calls a conversion, once you mark it as one in Admin. You can mark other events, such as call clicks, as key events too.
Is GA4 lead tracking legal in Australia?
The OAIC says the Privacy Act doesn’t ban tracking pixels, but you must follow the Australian Privacy Principles. Keep personal details out of your events, explain your analytics use in your privacy policy, and review your setup regularly. For specific legal questions, speak to a privacy lawyer.
Sources
These are the pages this article draws on. Search the titles to find them on the publishers’ sites.
-
Google Analytics Help: How to measure key events with Google Analytics
-
Google Analytics Help: [GA4] Recommended events
-
Google Analytics Help: Enhanced conversions in Google Analytics
-
Google Analytics Help: Possible reasons for conversion differences in GA4 vs. UA
-
Google for Developers: Send Measurement Protocol events to Google Analytics
-
OAIC: Tracking pixels and privacy obligations