In GA4, separate lead stages from contact clicks
Make an event represent a confirmed action, not an assumption. Google recommends lifecycle event names such as generate_lead, qualify_lead, working_lead and close_convert_lead; see the recommended events list. Do not send personally identifiable information to Analytics; review Google's PII guidance.
A simple lifecycle map
| Stage | Recording condition | Measurement value |
|---|---|---|
| Form submitted | Saved successfully once | generate_lead |
| Commercially qualified | Sales applies a written definition | qualify_lead |
| Active opportunity | Need, owner and next action exist | working_lead |
| Closed | Trusted CRM or sales record is updated | close_convert_lead |
Your GA4 implementation may use different event names, but a page refresh must not record the same lead again. Track a phone or WhatsApp click as a separate interaction; a click does not prove a call took place or an inquiry was submitted.
Data-quality checks
Use a test request with no real personal data. Submit a valid form and verify it is stored and creates one event. Submit an incomplete form and verify there is no success event. Test the consent behavior that applies, inspect DebugView and reports after processing, then reconcile event counts against stored inquiries for a defined period. Explain gaps such as browser blocking or consent withdrawal.
Never put email, phone or message text in event names, URLs, parameters or UTM tags. Use a non-identifying random reference only if the system needs clear deduplication, and document retention and access. Align qualification stages between marketing and sales. A staged measurement setup can be scoped through Google Ads and conversion management.
