GA4 Funnel Audits: What Actually Counts as a Lead
Summary
A catch-all form event — every submission from newsletters to contact pages to popups — inflated our funnel and misled Google Ads. Auditing events against real outcomes and importing only genuine lead events as conversions lowered cost per real lead and made the GA4 funnel match what the database showed.
Quick answer
Don’t trust event names — audit events against outcomes. List every form-related event and where it fires, classify each as business lead, intermediate step, or noise, keep only true lead events as Ads conversions, and build your funnel on the lead event broken down by device, source and geography.
Every analytics setup has a moment where you realize the numbers feel too good — or too confusing. A common culprit: the funnel is counting events that are not actually leads. In this article we explain how to audit your GA4 events, why generic form events mislead optimization, and what the right definition of a “lead†does for your campaigns.
The problem with generic form events
Many stores track a catch-all form event — every form submission, from newsletter signups to contact pages to checkout-adjacent popups, fires the same event. This creates two problems:
- Inflated conversion counts. Optimization sees “conversions†that include low-intent actions, so Google Ads spends toward the wrong signal.
- Opaque funnels. You cannot tell which page and which action actually produced a business lead, so you cannot improve the pages that matter.
How we audit the funnel
Instead of trusting event names, we audit events against outcomes:
- List every form-related event that fires on the site and where it fires.
- Map each event to a real outcome. A contact request that reaches your team is a lead; a newsletter double-opt-in may or may not be. A form that simply validates input is not.
- Pick the events that genuinely represent a lead — the ones whose submissions land in your actual business pipeline.
- Break the funnel down by dimension — device, geography, source — for the lead event specifically, not for the catch-all.
- The cost per real lead went down — the optimizer had a signal it could trust.
- The funnel in GA4 matched what the database actually showed, so reporting and reality agreed.
- Device and geography insights for the lead event revealed opportunities that the catch-all had hidden.
- List all form events and where they fire.
- Classify each: business lead, intermediate step, or noise.
- Keep only true lead events as Ads conversions.
- Build your funnel on the lead event, broken down by device, source and geography.
- Re-audit when you add forms, popups or new landing pages.
In our own stores, the difference was stark. A broad form event made the funnel look healthy; the genuine lead event exposed where real buyers actually dropped off. The two told opposite stories about which pages to fix.
Why this changes your ads
Google Ads optimizes toward whatever conversion you give it. If your imported “conversions†are dominated by low-intent actions, the algorithm finds more of the wrong people. Once we imported only the genuine lead events as conversions:
A practical audit checklist
The takeaway
The events you count determine what you optimize. Audit them against real outcomes, drop the catch-alls from your conversion definition, and both your GA4 funnel and your Google Ads will finally be working from the same, true picture of what a lead is.
Frequently asked questions
Why is a catch-all form event a problem?
It inflates conversion counts — optimization sees “conversions” that include low-intent actions and spends toward the wrong signal — and it makes funnels opaque: you can’t tell which page and which action actually produced a business lead.
What counts as a genuine lead event?
An event whose submissions land in your actual business pipeline. A contact request that reaches your team is a lead; a newsletter double-opt-in may or may not be; a form that simply validates input is not.
What changes when you import only genuine leads as conversions?
The cost per real lead goes down because the optimizer finally has a signal it can trust; the GA4 funnel matches what the database actually shows; and device and geography breakdowns of the lead event reveal opportunities the catch-all had hidden.