First: GA4 calls them key events
If you learned Google Analytics 4 a while ago, you will remember "conversions". In Google's current Analytics Help, an event that measures an action important to your business is called a key event. "Conversion" is now the term used in Google Ads: Google says you can create a Google Ads conversion from a Google Analytics key event, which gives you the same conversion counts in both places and lets you bid against it.
That matters on a lead-generation site, because the whole setup is one chain: an event fires, you mark it as a key event, and (if you advertise on Google) it becomes a conversion in Google Ads. The rest of this guide walks that chain.
A note on freshness: GA4 changes often, and terms have already changed once. Everything below was read from Google's documentation on 16 November 2026. Check the pages in the sources list if you are reading this much later.
Step 1: Decide what counts as a lead
Before touching any tag, write down what a lead is on your site. For most lead-generation sites it is one of a short list: an enquiry form submitted, a booking or callback request, a click-to-call, a message started on WhatsApp. Each one is a different action with a different meaning.
Google's documentation says that any event you collect can become a key event, and that Google Analytics lets you mark up to 30 events as key events on a standard property. So the limit is not the constraint. Your own clarity is. Pick the small number of actions that really mean "a person asked to talk to us", and leave everything else (scrolls, page views, downloads) as ordinary events.
Step 2: Send an event when it happens
There are two common ways to get a form submission into GA4.
Option A: Enhanced measurement. Google's enhanced measurement can collect form_start (the first time a user interacts with a form in a session) and form_submit (when the user submits a form) without code changes. Two points from Google's help page: the parameters (such as form_id, form_name, form_destination) can only be used in reports if you create custom dimensions for them, and you are required to ensure that no personally identifiable information is collected.
Our own judgement, not Google's: form_submit describes the moment of submitting. It does not, by itself, tell you the form was accepted by your server. If your form can fail after the click (a validation error, a failed request), test that a failed submission does not count as a lead.
Option B: A custom event from your site, through Google Tag Manager. Google's Tag Manager documentation describes the custom event trigger as the usual answer when a form's default behaviour has been altered (for example, when the form's submit event has been overridden). Your site pushes an event into the data layer when the lead is confirmed, and a Tag Manager trigger fires your GA4 event tag on it. The documented pattern is dataLayer.push({'event': 'your-event-name'}), with extra variables sent alongside if needed. If you use a regex on the event name, Google warns against the .* wildcard because it matches every event, including ones Tag Manager emits itself.
For a lead-gen site, Option B, firing only after the form has been accepted, is usually the cleaner signal. Whichever you choose, send one event per lead.
Step 3: Use generate_lead, and think about value
Google's recommended events list includes generate_lead, described as the event for when a user submits a form or a request for information. Google's events reference says to use it to track initial lead acquisition such as form submissions, newsletter sign-ups or demo requests, and to log it to understand the effectiveness of your marketing campaigns.
Its parameters, from Google's reference:
currency: a 3-letter ISO 4217 code. Required if you setvalue.value: the monetary value of the event. Google says it is typically required for meaningful reporting, and that if you mark the event as a key event, setting a value is recommended.lead_source: the source of the lead (Google's example is "Trade show").
The practical question is value. Many lead-gen businesses do not have a number that is true for every lead. Our advice: if you have a defensible figure (for example, an average value you have measured from your own CRM, with the currency set), send it. If you do not, do not invent one: an invented value flows into reports and into Google Ads bidding as if it were real. Send the event without a value and be clear in your reporting that it counts leads, not revenue.
Using Google's recommended event name also means your data lines up with Google's prescribed parameters, which Google says helps you get the most detail in reports and benefit from future features.
Step 4: Mark it as a key event
In GA4 Admin, under Data display, open Events and click the star next to the event, or create the event and use the Mark as key event toggle. Google's page gives the details that trip people up:
- You need to be a marketer or above to mark a new event, and an editor or above for an existing one, per Google's permission notes.
- New events may not appear straight away, but you can mark them ahead of time.
- Marking affects reports from the time of creation. It does not change historic data. Allow up to 24 hours for it to show in standard reports. Realtime reports update a few minutes after a user triggers it.
- Unmarking stops future key-event counting but does not erase past data.
The consequence: do not expect last month's leads to appear retroactively as key events after you mark the event today. Mark it before the campaign launches.
Step 5: Link it to Google Ads
If you run Google Ads, Google says you can create a conversion from a Google Analytics key event and manage it from the Ads or Analytics interface. Google lists the benefits: the same conversion counts in both products, reporting on non-Google and organic channels in the same campaign, the ability to bid against the conversion, and the ability to build remarketing audiences. Google also notes the Ads conversions do not appear in the standard GA4 reports; you evaluate them in Google Ads or in GA4's Advertising section.
Google adds that this feature may not be available to every property yet. If you do not see the option, ask your Google support contact or check eligibility before building a plan around it.
For the lead-form side of Google Ads, see our guide to choosing between Meta Ads and Google Ads for lead generation (published in the same series).
Step 6: Test it in DebugView
Never trust a tag you have not watched fire. Google's DebugView shows the events GA4 collects from a device in real time. You turn on debug mode for yourself by using Google Tag Assistant or Tag Manager's preview mode, or for all users by adding debug_mode: true to the config or event. One detail from Google's page: setting debug_mode to false does not disable it; you disable debug mode by removing the parameter.
Run these tests, in order:
- 1. Submit a valid enquiry. You should see exactly one
generate_leadevent. - 2. Submit an invalid enquiry (blank required field). You should see none.
- 3. Refresh the thank-you page, or press back and forward. Check you do not get a second event.
- 4. Test on mobile.
Google also notes that events are not visible in debug mode if you have implemented client-side privacy controls, or consent mode with users who have not given consent for Analytics cookies. If your test is silent, check your consent banner state before assuming the tag is broken.
Six mistakes that corrupt lead data
- 1. Sending personal data. Google's policies say no data may be passed to Google that Google could use or recognise as personally identifiable information, and Google lists email addresses and personal mobile numbers as examples. Lead-gen sites are exactly where it leaks: a thank-you URL like
/thanks?email=..., a form field value used as an event parameter, a name in a page title. Google says both the URL path and the parameters must be free of PII, and notes the same applies to custom dimensions, campaign parameters and event dimensions. Google's help describes a data redaction setting for removing email addresses (best effort) and chosen URL parameters. The fix is upstream: do not put personal data in URLs or event parameters. - 2. Forgetting cross-domain. If the form, booking engine or payment sits on a different domain, Google says that without cross-domain measurement each domain creates new cookies and IDs, so one visitor can look like two users in two sessions. Set up cross-domain measurement and use the same tag ID across the domains.
- 3. Counting the same lead twice. Page reloads, double-clicks on submit and two tags (a Tag Manager tag and a hard-coded one) are the usual causes. Test for it in Step 6.
- 4. Expecting history. Marking a key event does not backfill (Step 4).
- 5. Relying on custom parameters without custom dimensions. If you want to report on
form_nameorlead_source, Google says you can only use enhanced measurement parameters in reports if you create custom dimensions for them. - 6. Treating a GA4 count as your lead count. This is our judgement, not Google's: a GA4 key event is a measurement of a browser event. It will rarely match your CRM exactly (ad blockers, consent choices and failed submissions all create gaps). Compare the two occasionally, and use GA4 for the trend and attribution, and the CRM for the lead of record.
One more setting worth a look: Google's data retention page says that for standard properties you can set retention of user-level data (which also applies to key events data) to 2 or 14 months, and that this setting affects explorations and funnel reports, not standard aggregated reports. If you plan year-on-year lead analysis in explorations, check the setting before you need the data.
The checklist on one page
| # | Step | Done when |
|---|---|---|
| 1 | Define the lead | A short written list of actions that mean "asked to talk to us" |
| 2 | Send an event | Fires once per accepted lead, via enhanced measurement or a GTM custom event |
| 3 | Name and parameters | generate_lead; value and currency only if you have a defensible figure |
| 4 | Mark as key event | Star set in Admin before the campaign starts |
| 5 | Link to Google Ads | Ads conversion created from the key event (if you advertise there and the option is available) |
| 6 | Test | Valid submit = 1 event; invalid = 0; reload = no duplicate; mobile tested |
| 7 | PII check | No personal data in URLs, titles or event parameters |
| 8 | Cross-domain | Configured if the form or booking sits on another domain |
For how this data then feeds reporting, see our guide to the marketing analytics dashboard. Our marketing analytics and ROI reporting service covers tracking set-up and reporting.
Sources (as of 16 November 2026)
All opened and read on 16 November 2026.
- Analytics Help, "About key events" — https:/
/ support.google.com/ analytics/ answer/ 9267568 - Analytics Help, "Mark events as key events" — https:/
/ support.google.com/ analytics/ answer/ 13128484 - Analytics Help, "[GA4] Recommended events" — https:/
/ support.google.com/ analytics/ answer/ 9267735 - Google for Developers, "Event reference (GA4)",
generate_lead— https:// developers.google.com/ analytics/ devguides/ collection/ ga4/ reference/ events - Analytics Help, "Enhanced measurement events" — https:/
/ support.google.com/ analytics/ answer/ 9216061 - Tag Manager Help, "Custom event trigger" — https:/
/ support.google.com/ tagmanager/ answer/ 7679219 - Analytics Help, "Monitor events in DebugView" — https:/
/ support.google.com/ analytics/ answer/ 7201382 - Analytics Help, "Best practices to avoid sending Personally Identifiable Information (PII)" — https:/
/ support.google.com/ analytics/ answer/ 6366371 - Analytics Help, "Set up cross-domain measurement" — https:/
/ support.google.com/ analytics/ answer/ 10071811 - Analytics Help, "Data retention" — https:/
/ support.google.com/ analytics/ answer/ 7667196
Frequently Asked Questions
Are conversions and key events the same thing in GA4?
Which event should I use for a contact form?
Do I have to send a value with generate_lead?
Why do I see no events in DebugView?
Published by
Digitaso Media
Digital Marketing Agency
Digitaso Media is a full-stack digital marketing agency helping businesses generate predictable leads and sales through data-driven SEO, paid advertising, and conversion strategy.
About Digitaso Media →