From campaign visits to leads: reading GA4 without the guesswork

Separate traffic, engagement, and intent

Sessions tell you about visits. Engaged sessions give you another view of activity. Neither metric is a lead by default. To measure a meaningful action, your website needs to send a specific event when that action actually succeeds.

For a lead form, Google recommends the generate_lead event. Send it after a successful submission—not when the button is clicked or the form is simply viewed. Respect the visitor’s analytics consent and never include their email address in the event payload.

An event needs both implementation and configuration

Naming an event in GA4 does not make your website send it. First implement the event, then verify that Google receives it. Realtime is useful for an immediate check; standard reports can take longer to process new data.

Mark a meaningful event as a key event in GA4 when you want to treat it as an important outcome. Avoid selecting broad events such as page_view simply to make a lead column nonzero. In Traceflow’s Connections page, choose which of the property’s key events should count as leads and save the selection.

• Submit a successful test form with analytics consent.
• Look for the event in GA4 Realtime.
• Mark the intended event as a key event in GA4.
• Choose that event in Traceflow’s lead-event settings.
• Check the campaign report after processing, using matching dates.

Know what the lead total means

Traceflow adds the counts of the lead events you select. These are event counts, not necessarily unique people or qualified opportunities. If one person triggers generate_lead and qualify_lead and you select both, the combined count can include both actions.

Choose events that match the question you are asking. For top-of-funnel form submissions, select the successful form event. For qualification, use the appropriate implemented event and interpret it separately. GA4 counting settings and repeated actions can also affect totals.

Do not confuse session reporting with attribution models

A campaign table grouped by session campaign or session source answers a session-scoped question. GA4 attribution reports can distribute credit for key events across touchpoints using attribution models. Those are different views, so their totals and groupings need not tell the same story.

Traceflow’s campaign explorer is not a complete multi-touch customer-journey or CRM revenue model. When comparing it with GA4, use matching date ranges, compatible dimensions, and the same selected events. Also allow for Google’s report processing delay.

Investigate an empty report in order

Start with the right property and date range. Check consent and the website tag, verify the final campaign URL, then confirm the event arrives in Google. Only after those checks should you investigate lead selection and reporting differences.

A missing lead count can be a configuration issue rather than poor campaign performance. Keep “not configured,” “not received,” and “received but not processed yet” separate before deciding a campaign failed.