GA4 Lead Generation Tracking Setup: Events, Key Events and CRM Stages

Need this done for you? GrowthSparx offers a fixed-scope lead tracking and attribution setup: GA4, Google Ads, Meta, WhatsApp, calls and CRM wired into one dashboard, usually live in 2–3 weeks.

Benchmark reference: the public 2025–2026 numbers behind this guide (Meta and Google CPC/CPM in India, CPL ranges by industry, landing-page conversion, real estate funnel rates, WhatsApp API pricing) are collected and graded in our India lead generation benchmarks 2026 report.

What lead events should GA4 track?

Write the event plan before opening Tag Manager. Google publishes a set of recommended lead events (Google Analytics Help): generate_lead ("submits a form online or submits information offline"), working_lead (contacted by a representative), qualify_lead (fits the criteria to become qualified), disqualify_lead, close_convert_lead (became a customer) and close_unconvert_lead. Use these names rather than inventing your own; they come with defined parameters and keep reports consistent across properties.

The plan we start most Indian lead-gen sites with:

Two rules behind this plan. First, separate intent (a tap) from a lead (contact details received) from an outcome (sales accepted it). Merging them into one "conversion" is why many GA4 properties report far more leads than the CRM receives. Second, nothing personal goes into GA4: Google's policy forbids passing data it could recognise as personally identifiable, including "email addresses, personal mobile numbers" (PII guidance).

How do you set up generate_lead correctly?

Fire on confirmed success, not on the submit click. A submit-button click fires even when validation fails, the phone number is nine digits, or the server times out. The most reliable trigger is a data layer push your developer adds to the form's success handler:

window.dataLayer = window.dataLayer || [];
dataLayer.push({
  event: 'generate_lead',
  lead_source: 'website_form',
  form_name: 'site_visit_request',
  project: 'sector-150-3bhk',
  value: 1500,
  currency: 'INR'
});

If you cannot edit the site code (a page builder or WordPress plugin), the fallbacks in order of reliability are: a thank-you page URL, a success-message element visibility trigger, then GTM's Form Submission trigger with Check Validation on. Our form tracking guide for GA4 and GTM walks through each trigger type.

Parameters. Google's event reference lists currency, value and lead_source for generate_lead; currency is required whenever value is set, in three-letter ISO format (INR). Add your own parameters only if you will report on them, and register each as an event-scoped custom dimension in Admin, or it will not appear in standard reports.

Value. A lead value lets GA4 and Google Ads compare channels by value, not count. Worked example (illustrative): if 10% of form leads become qualified, and a qualified lead is worth ₹15,000 to you, a form lead is worth 0.10 × ₹15,000 = ₹1,500. That is the 1500 in the code above. Recalculate quarterly from your CRM.

How do you configure it in Google Tag Manager?

1. Variables: create Data Layer Variables for lead_source, form_name, value and currency.
2. Trigger: Custom Event, event name generate_lead.
3. Tag: Google Analytics: GA4 Event, your measurement ID (or the Google tag), event name generate_lead, event parameters mapped to the variables above.
4. Consent: if you run a consent banner, confirm the tag respects analytics consent settings.
5. Preview: submit a real test lead in Tag Assistant; check one generate_lead with all parameters.
6. Publish with a version name such as "GA4 lead events v1 – generate_lead, call, WhatsApp".

Do not also create generate_lead from the GA4 interface with "Create event" based on form_submit. Two sources of the same event is the commonest cause of doubled lead counts; see fixing duplicate conversions in GA4 and Google Ads.

How do you track call and WhatsApp leads in GA4?

Calls. Create a Click – Just Links trigger where Click URL starts with tel:, and a GA4 Event tag click_to_call with a cta_location parameter from a data attribute on each button. This counts taps, not connected calls. For answered calls, call duration and the caller's source, you need a call-tracking number service; see call tracking for Indian businesses.

WhatsApp. Same pattern, with Click URL matching wa.me or api.whatsapp.com, event whatsapp_click. Enhanced measurement already logs these as an outbound click with link_url and outbound parameters (enhanced measurement events), but a dedicated event is easier to report and mark as a key event. Connecting the tap to the chat and the CRM lead is a separate problem, solved with a reference code in the prefilled message; the full method is in WhatsApp lead tracking with GA4 and CRM.

Keep taps as secondary key events. Some taps never become a conversation (the dialler or app opens and the visitor changes their mind), so counting them as leads overstates performance; measure your own tap-to-conversation rate before deciding how to weight them.

How do you mark key events and set values?

1. In Admin → Data display → Events, find generate_lead and click the star to mark it as a key event (Editor access needed). Do the same for qualify_lead and close_convert_lead once they start arriving.
2. Standard properties can mark up to 30 key events, Analytics 360 up to 50 (Google Analytics Help). You will not need many; five to seven is typical for lead gen.
3. For an event that does not carry a value, you can set a default key event value when creating it.
4. In Admin → Attribution settings, keep the key-event lookback at 90 days (the default; 30 and 60 are options) if your buyers take weeks to decide (attribution settings).
5. To bid on GA4 data, create Google Ads conversions from the key events. Google notes that Google Ads conversions do not appear in standard GA4 reports. For lead gen, we prefer importing CRM outcomes directly into Google Ads with enhanced conversions for leads and using GA4 for cross-channel reporting, so the same lead is not counted twice in Google Ads.

How do you send CRM lead stages into GA4?

GA4 cannot see what happens after the form. The Measurement Protocol lets your server send those events, and Google describes its purpose as to "augment automatic collection", not replace it (Measurement Protocol guide).

1. Capture the client ID at submission: read the _ga cookie (the part after GA1.1., e.g. 1234567890.1728000000) into a hidden field and store it on the CRM lead.
2. Create an API secret in Admin → Data streams → your stream → Measurement Protocol API secrets. Keep it on the server.
3. On each stage change, POST to https://www.google-analytics.com/mp/collect?measurement_id=G-XXXXXXX&api_secret=XXXX:

{"client_id": "1234567890.1728000000",
 "events": [{"name": "close_convert_lead",
  "params": {"currency": "INR", "value": 120000}}]}

Google allows backdating events by up to 72 hours; older timestamps are moved to 72 hours ago. So run the sync at least daily, and send each stage once (keep a "sent to GA4" flag on the lead). The lead now has generate_lead from the browser and qualify_lead from the CRM under the same client ID, which is what makes channel-level qualified rates possible in GA4.

Which GA4 reports show lead performance?

Compare GA4's generate_lead count with the CRM's new-lead count weekly. A gap of a few per cent is normal (consent refusals, ad blockers); a gap of 30% means a tracking fault.

GA4 lead tracking QA checklist

For DebugView, use Tag Assistant or GTM preview, or set debug_mode on the tag. Google notes events will not appear if consent mode is active and analytics consent was not given, so accept cookies on your test device (DebugView help). For a wider audit covering Google Ads, Meta and the CRM, use our lead tracking audit checklist.

Sources

• Google Analytics Help: Recommended events: lead generation event names and when to trigger them.
• Google Analytics developer reference: Recommended events: generate_lead parameters; currency required with value.
• Google Analytics Help: Mark events as key events: steps, 30/50 limit, Google Ads conversions.
• Google Analytics Help: Enhanced measurement events: form_start, form_submit, outbound click.
• Google Analytics Help: Avoid sending PII: no emails or mobile numbers.
• Google Analytics Help: DebugView: enabling debug mode; consent caveat.
• Google Analytics: Measurement Protocol, send events: endpoint, API secret, client_id, 72-hour limit.
• Google Analytics Help: Attribution settings: key event lookback windows.