The generate_lead event
generate_lead is a GA4 recommended event that fires when a visitor expresses interest in a product or service — typically a form submission for a quote, demo, or contact. It can carry currency and value to express an estimated lead worth. It is the core conversion event for lead-generation sites, but a raw lead count says nothing about lead quality.
What this means
generate_lead is a GA4 recommended event for lead generation. It fires when a visitor submits a form expressing interest — a contact request, demo booking, or quote enquiry. You may include `currency` and `value` to assign an estimated worth to the lead. GA4 reports it like any conversion-eligible event.
It is the primary success signal for sites whose goal is enquiries rather than direct sales.
Volume is not quality
A lead count alone is a vanity metric: a campaign can flood you with low-intent or junk submissions that never become customers. Connect generate_lead to downstream qualification — marketing-qualified and sales-qualified stages — to judge sources by qualified leads, not raw count. Keep the contact's actual details out of analytics; record only that a lead happened and its estimated value.
- Fires on a lead/enquiry form submission
- Optional currency and value for estimated worth
- Raw lead count says nothing about lead quality
How it appears in analytics and logs
A generate_lead event means a visitor submitted interest. A source producing many leads that never qualify is producing volume, not value — pair the count with downstream qualification.
Diagnostic use case
Mark lead submissions as a conversion on lead-generation sites, then tie lead volume to sources while remembering that volume is not quality.
What WebmasterID can help detect
WebmasterID can record lead-submission events first-party without storing the contact details, so lead conversion is measurable while personal data stays in your CRM.
Common mistakes
- Treating raw lead count as success without qualification.
- Storing contact PII in the event parameters.
- Sending value without currency.
Privacy and accuracy notes
generate_lead should record that a lead occurred and an optional estimated value, not the contact's name, email, or phone. This is educational, not legal advice.
Related pages
- The form_submit event
A form_submit event records that a visitor submitted a form — a signup, contact, or checkout form. It is one of the highest-value events because it usually maps to an intent or conversion. The hard rule is that the submitted field values (name, email, message) must never enter analytics: you record that a form was sent and which one, not what was typed.
- The sign_up event
sign_up is a GA4 recommended event that fires when a visitor creates an account. It carries a method parameter naming the registration mechanism, such as 'Google', 'email', or 'Apple'. It is a key activation event for products with accounts, marking the move from anonymous visitor to registered user — distinct from logging in, which returning users do repeatedly.
- Conversion events (key events)
A conversion event is an ordinary event you have marked as important — a purchase, a signup, a qualified lead. GA4 now calls these 'key events'. Nothing about the event changes; marking it tells the platform to count it as a conversion and build conversion reports around it. The decisions that matter are which events to mark, and whether to count once per session or every time.
- CTA tracking
Track lead and enquiry submissions first-party.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.