Online Store Checkout Funnel
Field Supply's checkout funnel tracks a June shopping journey from product views through completed orders. The chart shows that many visitors do not add an item to cart, while most shoppers who submit payment complete the order. These observations can guide a product-page review and a payment-flow health check. Ensure all events use the same visitor or session identity and account for consent, bot filtering, and duplicate events. The funnel should be segmented by device, geography, and acquisition channel before making a broad change. A mobile-specific issue can disappear in an all-traffic aggregate. Review the underlying definitions and totals before using this view to make an operational decision.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
E-commerce checkout review
Key decisions
- Improve product pages: Product view to cart is the largest early drop.
- Review checkout: Compare checkout starts with payment submissions.
- Audit payment: Investigate the final completion gap.
When to reuse this
Use for one store, a defined period, and a consistent shopper identity rule.
Frequently asked questions
Why start with product view?
What should payment submitted mean?
Why segment this funnel?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.