Google Analytics 4: Measure Leads and Sales You Can Verify
dopweb
Updated November 4, 2026

A reporting dashboard says a campaign generated 20 leads. The sales inbox contains eight. Before changing the campaign, find out what those two systems counted. A useful Google Analytics 4 setup begins with an agreed definition of a lead and ends with a test in the system that actually receives it.
Define the event before tagging the button
For an estimate request, distinguish opening the form, attempting submission, and receiving confirmation from the server. Count the successful request as the lead. Keep the earlier steps as diagnostic events if they help explain abandonment. Use Google's recommended event names where they fit; avoid sending names, email addresses, or form contents as event parameters.
Follow a single test through the system
With the appropriate consent choices in place, submit a clearly identified test. In DebugView, check the event name and parameters, then verify receipt in the CRM. Refresh the confirmation screen: if the lead is counted again, repair the trigger before using the event to evaluate campaigns. Repeat on a phone and after an unsuccessful submission.
Interpret the report with its limits
Mark the important action as a key event. Compare acquisition sources using the same date range, scope, and outcome. Consent choices, blockers, and different attribution rules can create gaps; don't manufacture a correction factor to make two dashboards match. Document which system supplies the final sales figure. Google’s event implementation guide.
Related guides and services
Search and marketing
Web analytics · Web traffic
More from Dopweb
Dopweb homepage · Book a call