Distinguish contact intent from observed outcomes
Define the business question before editing tags. Google documents generate_lead for a created inquiry, qualify_lead for meeting qualification criteria and close_convert_lead for a later conversion outcome. A documented event name does not mean that your website sends it.
On this website, generate_lead represents a server-confirmed successful contact-form receipt recorded once. Contact clicks indicate intent; navigation does not establish a CRM or sales outcome.
On smaller screens, scroll the table horizontally to read all columns.
| Event | What it establishes | What it does not establish |
|---|---|---|
| whatsapp_click | A contact-link click | Conversation or qualification |
| generate_lead | Confirmed inquiry receipt under the implementation | Project fit or a signed contract |
| qualify_lead | A recorded qualification milestone | An automatic sale |
| close_convert_lead | A defined completed business outcome | Cash collection if only a contract is defined |
Primary reference: Google Analytics: recommended lead-generation events
Trace the current implementation before adding a tag
Map the user action through the data layer, GTM and GA4. If the application and another tag both send the same outcome, another implementation may increase duplication. Correct its source rather than introducing a parallel container.
Document how confirmed success is passed to the thank-you journey. Refreshing or returning to that page must not generate another inquiry, and a direct visit does not establish that a submission occurred.
Validate the event across the complete submission journey
Run the following behavior checks in a test environment, inspect the receiving record and verify the expected event count before releasing configuration changes.
On smaller screens, scroll the table horizontally to read all columns.
| Case | Expected additional generate_lead | Reason |
|---|---|---|
| Rejected or failed submission | 0 | No confirmed receipt |
| One successfully stored submission | 1 | A confirmed new inquiry |
| Thank-you refresh after success was recorded | 0 | No new inquiry |
| Direct thank-you visit | 0 | No submission result |
| WhatsApp click only | 0 | Separate contact-intent event |
Send useful context, not personal records
Use relevant context such as language, placement, content type and available campaign information. Do not send names, email addresses, phone numbers, messages or URLs containing those values to GA4. Inspect query strings, page titles and event parameters.
Do not assign a default monetary value simply to display return. Any approved estimated business value needs a documented definition and source; an inquiry value is not contract revenue.
Primary reference: Google Analytics: avoid sending personally identifiable information
Use custom dimensions only for a defined reporting need
Check whether a predefined dimension already answers the question. For additional categorical context such as button placement, first verify that the agreed event parameter is collected, then register an event-scoped dimension through Custom definitions with the required account access.
An illustrative parameter is button_placement with a bounded set of values such as header and footer, rather than a different value per person or inquiry. Creating the definition does not compensate for a missing event parameter; validate collection before relying on the report.
Primary reference: Google Analytics: event-scoped custom dimensions
Interpret acquisition with the correct reporting unit
Sessions, users and inquiries are different units. Session source is not necessarily first-user source. A visit classified as an AI referral does not itself establish a recommendation or a human prospective customer.
Review relevant landing pages alongside actual inquiries and aggregate CRM outcomes. Reporting windows, scope, consent and processing differences can explain discrepancies; not every difference calls for another Analytics implementation.
Review key events after validating the underlying action
Select events that represent important business actions. Marking an event as a key event does not fix its definition or duplication and cannot manufacture an outcome. Google’s documentation explains the role of key events in measuring important actions.
Review counts after the implementation date while keeping contact intent, qualification and sales separate. A deployment from hours ago cannot establish an uplift, and a historical zero does not disprove inquiries received outside the measured form.
Primary reference: Google Analytics: about key events
Frequently asked questions
Choose the next step for your project review
- Compare CPQL and advertising spend per contract
- Review calculation definitions and limits
- Read the GPR Property experience in context
Share the project brief, target market and available budget. For existing campaigns, include aggregate spend, lead quality and follow-up outcomes for the same period to define the scope and deliverables.
Explore the service and discuss your project