GA4 & Analytics

How to Build a GA4 Funnel Report That Actually Tells You Something

A GA4 funnel report is one of the most directly useful analyses you can run on a B2B site — it shows exactly where users drop off on the path to conversion and how that varies by traffic source, device, and user type. But misconfigured funnels produce numbers that are misleading in specific, dangerous ways. Here is how to build one that you can actually trust.

TL;DR

  • GA4 funnels live in Explorations — there is no funnel report in the standard reports section.
  • Open funnels count users who enter at any step. Closed funnels only count users who entered at step one. Most B2B use cases should start with open funnels.
  • The most important configuration detail is whether steps use AND or OR logic — this changes the funnel numbers significantly.
  • Segment comparison (organic vs paid, mobile vs desktop) is where funnel data becomes genuinely actionable.

Where funnel reports live in GA4

Funnel reports in GA4 are built in Explorations — under the Explore tab — not in the standard reports. This trips up people migrating from Universal Analytics, which had a Goals funnel visualization in the standard interface. In GA4, any funnel analysis requires an Exploration.

Go to Explore, create a new exploration, and select Funnel exploration as the technique. You will get a canvas with a funnel configuration panel on the right and a visualization area in the center.

Open vs closed funnels: get this right first

A closed funnel only counts users who enter at step one. A user who lands on your pricing page without first visiting your homepage is not counted. This is appropriate for measuring a deliberately designed sequential flow — a checkout process where step one is always adding to cart.

An open funnel counts users who enter at any step. A user who lands directly on your pricing page is counted as entering at the pricing page step. This is appropriate for most B2B site analyses, where users arrive at different points in their journey and you want to understand drop-off from wherever they are, not just from a defined starting point.

GA4 defaults to closed funnels, which produces deflated numbers for most B2B analyses. Enable the "Make this funnel open" toggle for most use cases.

Defining funnel steps correctly

Funnel steps can be defined using event conditions (a specific event fires), page conditions (user views a specific page or URL pattern), or combinations. For a B2B lead generation funnel, a typical step configuration:

  • Step 1: Event is session_start (any visit begins)
  • Step 2: Event is page_view AND page_location contains "/services" or "/pricing"
  • Step 3: Event is page_view AND page_location contains "/contact"
  • Step 4: Event is form_submit or your custom conversion event

The AND vs OR logic within a step matters significantly. If step two uses AND to combine two page conditions, only users who visited both pages will match. If it uses OR, users who visited either page will match. For a funnel step that represents "visited any solution page," use OR across multiple page conditions.

Step 5: Apply segment comparisons

A funnel without segments tells you aggregate drop-off rates. Segments are where funnel data becomes actionable. The most useful comparisons for B2B sites:

Organic search vs paid search. If paid search traffic converts at 0.8% and organic converts at 2.1%, the funnel will often show you where the difference emerges — paid search users drop off at the pricing page at much higher rates, suggesting price sensitivity or a mismatch between ad promise and page content.

Mobile vs desktop. B2B sites almost universally convert better on desktop. The funnel comparison shows whether the gap is in the early stages (mobile users never get to pricing) or the late stages (mobile users reach the contact form but do not submit). These are different problems with different solutions.

New vs returning users. Returning users in B2B contexts are often in a more advanced research stage. A funnel that shows returning users converting at five times the rate of new users confirms a multi-touch buying journey — which has implications for how you invest in content that brings people back.

Reading the funnel visualization

GA4's funnel visualization shows three numbers at each step: the count of users who reached that step, the percentage who moved to the next step, and the abandonment rate. The key metric is the completion rate between steps — the drop-off percentages.

High drop-off at a specific step is a signal worth investigating but not necessarily a problem to fix in isolation. A 70% drop-off from "pricing page view" to "contact form view" might indicate a pricing page problem — or it might indicate that 30% of people who see your pricing are genuinely interested, which is actually high for a B2B audience. Context and comparison matter more than the absolute numbers.

Common configuration mistakes

Using the wrong date range. For B2B sites with 30- to 90-day buying cycles, a 7-day funnel date range will show artificially low conversion rates — users who started the journey within the window did not finish it within the window. Use 30- to 90-day date ranges for funnel analyses that include conversion steps.

Counting sessions instead of users. GA4 funnels default to users, but some configurations count sessions. A user who visits the pricing page in three separate sessions would be counted three times in a session-based funnel. Use users for most B2B funnel analyses — you want to understand how many individuals are moving through the journey.

Not accounting for direct navigation. Users who know your URL and navigate directly to the contact page will land in step three or four of the funnel without passing through earlier steps. In an open funnel, they are counted as entering at step three. In a closed funnel, they are excluded entirely. Neither is wrong — they are different questions about different user behaviors.

Want funnel data you can actually make decisions from?

I configure GA4 to track the events your funnels need — form submissions, page milestones, demo requests — and build the Explorations that turn that data into answers.

Get a quote