Make visits count

How to read a conversion path without overreading it

Understand ordered funnel steps, drop-off and the limits of the simple conversion path in AbstractMetrics.

START HERE

The path counts users who complete recorded events in order. Use a large drop to choose a transition to test, not to diagnose why each visitor stopped.

A conversion path turns a list of event names into a sequence you can inspect. It can help answer a practical question: where should I try the customer journey myself? Its value comes from showing the order, not merely drawing progressively smaller bars.

Read the first step carefully

A closed funnel starts with people who meet the first step. Later counts describe those who continue through the defined sequence. They are not independent totals that can be joined after the fact. Google's funnel documentation explains the distinction between open and closed funnels.

The scope also matters. A path for Google organic activity on one website is not a path for every visitor across every marketing channel. Keep the date range and source labels next to the result.

Work through a fictional example

Suppose a path shows 200 users at product view, 60 at add to cart, 35 at checkout start and 20 at purchase. The largest numerical drop is between product view and add to cart: 140 users.

That makes the product-to-cart transition a useful place to inspect. It does not mean 140 people encountered an error. Some were researching, some may not have liked the product, some may have returned later, and the tracking itself may need checking.

Try the product page on a phone. Verify variant selection, availability information and the cart control. If those work, inspect whether the page answers the questions people actually bring to it.

Understand the current AbstractMetrics path

For a recorded purchase goal, the product uses a four-step ecommerce path when the required events exist: view item, add to cart, begin checkout and purchase. A supported form path uses form start and form submit. Other eligible goals use page view followed by the goal.

These are closed, ordered event paths with up to 30 minutes between adjacent steps. Other events may happen between steps. They are designed as a quick diagnostic. The dashboard is not an editor for every possible custom funnel, and a long sales cycle can fall outside this window.

Keep search totals outside the funnel

Search impressions and clicks are aggregate Search Console measures. They are not user events in the GA4 path. You cannot put impressions, clicks, sessions and purchases into consecutive bars and claim you followed the same people.

Use search data to understand discovery and the recorded funnel to inspect onsite activity. Combining the perspectives is useful without inventing individual keyword-to-purchase attribution.

Choose a test, then gather evidence

If the first step has only a handful of users, test the flow directly and allow more activity to accumulate. If the report is unavailable, check event availability and the API limitations. AbstractMetrics reports that state instead of constructing a funnel from separate totals.

After fixing a real obstacle, repeat the same path and scope. Compare the counts as well as completion proportions. A more attractive final bar is encouraging only when the measurement and traffic context still make sense.

What to watch afterwards

Repeat the same ordered path. Do not compare it with a differently defined funnel or treat drop-off as a known cause.

Take this to ChatGPT

Explain the recorded conversion path for my selected goal. State its scope and time window, identify the transition worth testing, and separate possible causes from what the funnel actually measures.

You choose what to share. Copying does not send anything or connect an account.

Sources and further reading

Official guidance checked on 16 October 2026. Examples and suggested workflows are our own.