How to Track Qualified Leads with GA4, GSC and Your CRM

1. Define each stage
2. Give GSC, GA4 and the CRM distinct roles
3. Create an event specification
4. Record attribution and consent-aware identifiers
5. Send qualification outcomes
6. Build a weekly lead-quality report
7. Test duplicates, spam and failed forms
8. What the data cannot prove
9. Frequently asked questions

Write these definitions down before you build anything. Otherwise, every report will mean something different to sales and marketing.

• Contact click: someone taps a phone, email or WhatsApp link. It shows intent, not a lead.
• Enquiry: a form submits successfully, or a real conversation starts and is logged.
• Qualified lead: an enquiry that sales confirms meets your agreed criteria for fit and intent.
• Quotation: you sent a priced proposal.
• Won deal: the customer accepted and the work or order is confirmed.

Search Console’s Performance report aggregates data by property or by page, depending on the view (Search Console Help). Therefore, use it to find which pages and topics attract search traffic, and use GA4 and the CRM to judge which of that traffic produces leads.

GA4 has recommended events for lead generation. They include generate_lead, qualify_lead, disqualify_lead, working_lead, close_convert_lead and close_unconvert_lead (Google Analytics Help). Using these names also populates GA4’s lead acquisition report, which shows new, qualified and converted leads by channel (source).

Event dictionary

The trigger matters most. For example, generate_lead should fire on a confirmed successful submission, not on the button click. Check the current parameter list for each event in Google’s developer reference before you build, because recommended parameters can change.

To connect a CRM record back to a website visit, store a non-personal identifier with the lead. Commonly this is the GA4 client ID captured in a hidden form field, along with the landing page and UTM source. Follow your consent setup, so you only collect identifiers where the visitor’s choices allow it.

Never send personal information to GA4. Google’s policy prohibits passing data it could recognise as personally identifiable, including email addresses and phone numbers (Google Analytics Help). So names, emails, phone numbers and enquiry text belong in the CRM only, never in event parameters, page URLs or custom dimensions.

CRM status changes happen offline, after the visit. To bring them into GA4, use a supported method. The GA4 Measurement Protocol sends server-side and offline events, and Google describes it as a way to augment normal tagging, not replace it (Google for Developers). Alternatively, some CRMs offer a ready integration. For Google Ads bidding on qualified leads, use Google Ads’ own offline conversion options rather than relying on GA4 alone.

If you cannot connect the systems yet, don’t worry. A simple monthly export from the CRM, joined to landing page and source, still gives you a useful quality view.

A rate is only meaningful if the denominator is clear. In particular, keep contact clicks out of the enquiry count.

Worked example (illustrative numbers)

All numbers are hypothetical. Here, the qualified rate is 12 ÷ 40 = 30%. The 95 contact clicks are reported beside the funnel, not inside it. Break the same table down by source and landing page, and you can see which channels bring qualified leads, not just volume.

• Failed submit: submit with a required field empty. No generate_lead should fire.
• Double submit: tap submit twice quickly. Only one lead should be recorded.
• Spam: confirm your spam filter runs before the event fires, or mark spam as disqualified in the CRM.
• Returning user: submit a second enquiry from the same browser later. Decide whether it is a new lead or an update, and apply that rule consistently.
• Test data: exclude internal traffic and label test leads so they don’t inflate reports.

Use GA4’s DebugView while testing, and check each action once end to end.

Even a good setup has blind spots. For instance, consent choices, ad blockers and cross-device journeys mean GA4 will not see every visit. Phone calls and WhatsApp chats may never connect to a session. In addition, Search Console cannot attribute a lead to a query. So treat source data as strong evidence, not perfect truth, and look at trends over months.

Write your five stage definitions and the event dictionary above, then test each event once. If you would like help setting up measurement alongside your campaigns, see our Google Ads management service, our guide to Google Ads costs in India, or contact us to review your current setup.

• Google Analytics Help, Recommended events (checked 25 October 2026).
• Google Analytics Help, Lead acquisition report (checked 25 October 2026).
• Google Analytics Help, Best practices to avoid sending PII (checked 25 October 2026).
• Google for Developers, Measurement Protocol (GA4) (checked 25 October 2026).
• Search Console Help, Performance report (checked 25 October 2026).