Track shopping behavior funnel

Track shopping behavior funnel in Google Analytics — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
I need the shopping behavior funnel for the last two months: product view, add-to-cart, begin…
I need the shopping behavior funnel for the last two months: product view, add-to-cart, begin checkout, and purchase. Show counts and conversion rates between each step overall and for mobile vs desktop. Export the funnel counts and a short note on any step with conversion below 5%.

Improve — make it easier to accept

+
Before I share the funnel with the product team, make bottlenecks obvious: surface the weakest step…
Before I share the funnel with the product team, make bottlenecks obvious: surface the weakest step as a headline metric, show the percentage drop and absolute user loss, list the top three product pages with the biggest drop-off at that step, and call out suspected UX causes such as missing CTAs or slow pages. Suggest one quick A/B test to validate the fix.

Decide — diagnose the stuck moment

+
The funnel shows a sharp drop from begin checkout to purchase on mobile this week. The engineering…

Begin checkout to purchase conversion is tiny on mobile

The funnel shows a sharp drop from begin checkout to purchase on mobile this week. The engineering manager says checkout code wasn’t touched; our payments vendor reports no outages. I can’t tell if this is a gateway decline, a form validation bug, or a spike in fraud declines. What is the likeliest diagnosis and what two logs or reports should I request now to confirm it?

Become — change the pattern

+
Over the past six months we chase a new funnel leak every sprint and run short A/B tests that never…

We keep chasing different funnel leaks each sprint

Over the past six months we chase a new funnel leak every sprint and run short A/B tests that never stick. I need a pattern change so we stop firefighting and start fixing root causes. What recurring measurement and decision habit should we adopt so we identify the real persistent bottlenecks and assign clear owners for fixes?

Next to this one

Other web analytics work people do in Google Analytics.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.