Track qualified leads by recording the website enquiry in GA4 and the business qualification decision in your CRM, then connecting those records through a controlled measurement process. A form submission alone cannot tell you whether the person is a suitable prospective customer.
You do not need to begin with a complex integration. Start with definitions, reliable records and a report that distinguishes enquiries from opportunities. Add automated feedback only after you can explain what each event means and validate where it came from.
Agree on one qualification rule
Write a rule that a second team member can apply consistently. For a hypothetical service business, a qualified lead might be a genuine enquiry for an offered service, within the supported market, with enough information to progress to a sales conversation. Add budget or timing criteria only if the team actually uses them.
Keep “qualified,” “contacted” and “customer” separate. A person can fit your service before anyone has spoken to them. Someone can also answer a call without being a suitable buyer. Changing definitions halfway through a report creates a misleading trend.
Map the lead journey to events and records
Google’s recommended events include lead-generation stages for online and offline activity. These events require implementation; naming them in a plan does not connect a CRM automatically.
| Business milestone | Example GA4 event | Evidence to require |
|---|---|---|
| Enquiry accepted | generate_lead |
A successful request recorded by the form or lead system |
| Meets your qualification rule | qualify_lead |
A recorded assessment against agreed criteria |
| Fails qualification | disqualify_lead |
A reason recorded in the lead system |
| Sales contact occurs | working_lead |
A recorded contact activity |
| Becomes a customer | close_convert_lead |
A confirmed sales outcome |
This is an example measurement map. Adapt the evidence and implementation to your process while preserving the meaning of the recommended events. Do not send every stage as a new raw enquiry.
Make the website event describe success
Trigger the enquiry event after the request is accepted, rather than on any click of the submit button. Check failed validation, repeated clicks and confirmation-page reloads. If two separate installations report the same success, resolve the overlap.
A clearly labelled test should produce one accepted record in the lead system and the intended analytics event. Check GA4 DebugView during development and compare reporting after processing. Test the templates and consent states your visitors actually encounter. Our duplicate lead guide covers common reconciliation checks.
Keep a useful CRM record
Store a stable internal lead ID, creation time, available source information, campaign identifiers, landing page, lead status, status-change dates and the reason for disqualification. Give every lead a responsible owner. Keep missing attribution visible rather than filling it with a guess.
Use consistent campaign naming so a report can map the record to the right campaign. Preserve identifiers when the lead moves between systems. A spreadsheet can support an early process if access, updates and duplicate handling are controlled, although a CRM is easier to maintain as volume grows.
Connect records without exposing contact details
Keep names, email addresses, phone numbers and free-text enquiries out of ordinary GA4 event parameters and page URLs. Google prohibits sending personally identifiable information through standard Analytics collection; consult its guidance on avoiding PII.
Use an implementation designed for the permitted identifiers, consent requirements and destination. Do not treat hashing as permission to send arbitrary customer fields. Any specialist user-provided-data feature needs its own supported setup and applicable requirements.
When qualification occurs in the CRM, a developer or integration must send that outcome to the intended measurement destination. Verify the event time, matching logic, duplicate handling and supported data fields. You can still report qualified leads directly from the CRM while that integration is being built.
Build a report that follows one cohort
For lead-quality evaluation, group enquiries by the date they were created and follow their later outcomes. If January leads close in February, dividing February sales by February’s new enquiries mixes different groups. A separate operational report can show sales completed this month, provided it is labelled clearly.
Include media spend, raw leads, qualified leads, customers, qualification rate and the cost of each stage. State the currency, source, attribution basis and the time allowed for leads to mature. Platform-attributed totals and CRM outcomes may differ; see our reporting differences guide before treating a mismatch as data loss.
A small example of the decision this enables
Suppose a campaign spends $900 and creates 45 enquiries. Fifteen qualify and three eventually become customers. These hypothetical figures give:
- Cost per raw lead: $900 ÷ 45 = $20.
- Qualification rate: 15 ÷ 45 = 33.3%.
- Cost per qualified lead: $900 ÷ 15 = $60.
- Media cost per customer: $900 ÷ 3 = $300.
A $20 lead cost alone cannot tell you whether this is sustainable. Compare the $300 media acquisition cost with customer contribution and the other costs of acquiring and serving that customer. Recalculate after the cohort has had enough time to progress.
What should you implement first?
Start with one important form, one qualification rule and one weekly reconciliation. Fix missing or duplicated records before expanding the event map. Document ownership so a website change or CRM workflow update does not silently change the meaning of “lead.”
Pixel Pulse Media can help define the measurement plan through GA4 and conversion tracking setup and present it through Looker Studio reporting. Request a tracking review and describe your form, CRM and current reporting gap.