Skip to main content
Card class: Non-HeroCategory: Analytics

At a glance

The drop-off rate at every step of the GA4 ecommerce funnel: view_item → add_to_cart → begin_checkout → add_payment_info → purchase. Decomposes the cart-abandonment problem into specific failure points, surfacing whether the leak is at the product page (poor view-to-cart), the cart page (cart-to-checkout shock), the checkout form (checkout-to-payment friction), or the payment step (payment failure or last-second hesitation). The single most actionable card for diagnosing checkout-flow problems, because each drop-off location implies a different fix.
What it countsAt each pair of adjacent funnel steps, computes (1 - (events at step N+1 / events at step N)) × 100 to produce the drop-off percentage between those steps. Returns a four-row table: view-item-to-cart drop, cart-to-checkout drop, checkout-to-payment drop, payment-to-purchase drop.
Sample basisEvents per the GA4 standard ecommerce schema (view_item, add_to_cart, begin_checkout, add_payment_info, purchase). Each step is event-count rather than user-count, so the same user adding multiple items contributes multiple add-to-cart events.
Sampling thresholdGA4 standard properties sample above 10M events per query window; 360 above 1B. The connector requests runReport with property defaults. Sampled responses include samplingMetadatas flag.
Bot traffic filterFiltered. GA4’s bot filter applies; custom IP and internal-traffic filters apply.
Time zoneThe merchant’s GA4 property time zone, configured in Admin → Property → Property Settings.
Currency (revenue events)n/a, this card does not use revenue.
Healthy bands per stepview-to-cart drop: 70-90 percent (most product-page visitors don’t add). cart-to-checkout drop: 30-50 percent (some abandon at cart). checkout-to-payment drop: 15-30 percent (checkout-form friction). payment-to-purchase drop: 5-15 percent (payment-method failure or last-second hesitation).
Step semantics: view_item → add_to_cartThe product-page conversion. High drop here (>92 percent) signals weak product copy, low-quality images, missing reviews, or pricing surprise. The fix is product-page work, not checkout work.
Step semantics: add_to_cart → begin_checkoutThe cart-page conversion. High drop here (>50 percent) signals shipping-cost shock, account-creation friction, or missing trust signals on the cart page. The fix is cart-page work: clear shipping costs, guest checkout, trust badges.
Step semantics: begin_checkout → add_payment_infoThe form-completion conversion. High drop here (>30 percent) signals checkout-form friction: too many fields, slow page load, missing autofill support, or missing payment-method shortcuts. The fix is checkout-form simplification.
Step semantics: add_payment_info → purchaseThe payment-completion conversion. High drop here (>15 percent) signals payment-method failure (declines, 3DS abandonment) or last-second user hesitation (cart-summary shock). The fix is payment-vendor optimisation or final-step copy.
Time window30D vsP (30 days vs prior period).
Alert triggerAny step drop >2σ above the merchant’s 30-day baseline. The 2-sigma threshold catches genuinely anomalous drops while tolerating normal day-to-day variance.
Rolesowner, marketing

Calculation

Calculated automatically from your Google Analytics 4 data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A UK fashion brand on Shopify Plus running paid acquisition + email + organic. Snapshot for the 30-day window ending Tuesday 14 May 26.
Step transitionStep-N countStep-N+1 countDrop-off rateBand
view_item → add_to_cart84,00012,40085.2%Healthy (within 70-90%)
add_to_cart → begin_checkout12,4007,80037.1%Healthy (within 30-50%)
begin_checkout → add_payment_info7,8004,20046.2%Amber (above 30% threshold)
add_payment_info → purchase4,2003,64013.3%Healthy (within 5-15%)
What the funnel shape is telling us:
  1. The leak is concentrated at begin_checkout → add_payment_info. 46.2 percent of users who start checkout never enter payment information. That single step is dropping nearly half of intent-bearing users, while every other step performs in band. The diagnosis is checkout-form friction, not cart shock or payment failure.
  2. What makes this so actionable is what it isn’t. The view-to-cart conversion at 14.8 percent is healthy fashion-vertical performance; the product pages are doing their job. The cart-to-checkout drop of 37.1 percent is normal cart-abandonment shock; nothing unusual there. The payment-to-purchase drop of 13.3 percent says the merchant’s payment infrastructure works fine. The funnel pinpoints the broken step.
  3. Common causes of a 46 percent checkout-form drop. (a) Mandatory account creation before payment entry (costs 10-15 percentage points in this step). (b) Long form with email, shipping address, billing address (separate), phone number, etc. all required (costs 5-10 percentage points). (c) No autofill support on form fields (costs 5-8 points on mobile specifically). (d) No express-checkout buttons (Apple Pay, Google Pay, Shop Pay) above the form fields (costs 8-15 points). (e) Slow page load between begin_checkout and form display (costs 3-7 points per second of delay).
  4. The recovery playbook for this snapshot. (a) Test guest checkout: remove account creation, see if drop falls toward 30 percent. (b) Audit form length: target 6 or fewer required fields above the fold. (c) Implement Shop Pay (Shopify-native one-tap checkout); brand-typical lift on this step alone is 15-25 percentage points. (d) Add Apple Pay and Google Pay as express checkout options; lift another 5-10 percentage points on mobile. (e) Measure weekly during the optimisation window.
  5. Lost revenue at this step. The merchant has 7,800 users entering checkout and only 3,640 purchasing. At ~50 percent purchase conversion from begin_checkout (which the rest-of-funnel implies), the brand is losing roughly 1,800 of those 7,800 to step-3 friction specifically. At a £75 AOV, that’s £135K of revenue per 30-day window dropping at this single step. A 10 percentage-point reduction in step-3 drop (from 46 to 36 percent) recovers approximately £29K monthly without changing any other variable.
  6. The funnel-shape reading. A funnel that drops in band on every step is a brand with a structurally healthy checkout that needs cohort-level optimisation (segment, content, source). A funnel that drops out-of-band on one specific step is a brand with a structural defect in that step that’s worth fixing first. Always fix the structural defect before optimising the cohorts.
The diagnostic flow when this card flags amber:
  1. Identify the worst step. Each step’s drop is shown alongside its healthy-band threshold; flagged step(s) point directly at the cause class.
  2. Match the step to the cause class using the step semantics in the TLDR above. view-to-cart = product page; cart-to-checkout = cart page; checkout-to-payment = checkout form; payment-to-purchase = payment vendor or final-step copy.
  3. Cross-reference with Cart Abandonment Rate for the user-level rather than event-level view. Funnel and abandonment-rate together triangulate where the leak sits and how big it is.
  4. Pair with Checkout Completion Rate for the focused checkout-only measurement. Brands optimising checkout flow specifically should treat the checkout-completion-rate card as the success metric.
  5. Pair with Hotjar or FullStory session replays of the affected step. Watching 10-15 actual sessions abandoning at the flagged step often surfaces specific UX issues (rage clicks on a non-clickable element, dead clicks on a missing CTA) that the analytics view cannot show.

Sibling cards merchants should reference together

  • Add to Cart Rate for the headline view-to-cart step rate. The funnel-dropoff card decomposes; the add-to-cart-rate card is the single number for the first step.
  • Cart Abandonment Rate for the user-level total abandonment view. The funnel decomposes by step; the abandonment card is the user-level summary.
  • Checkout Completion Rate for the begin-checkout-to-purchase span specifically (steps 3+4 of the funnel rolled up).
  • Funnel Trend for the time-series view of how each step’s drop-off rate evolves week-over-week.
  • Funnel by Channel for the source-by-source view, surfacing whether specific acquisition channels have funnel shapes that differ from the blended view.
  • Funnel by Device for the mobile-vs-desktop split; mobile typically shows worse step-3 drops than desktop and the device card surfaces the gap.
  • Ecommerce Conversion Rate is the headline conversion metric this funnel ultimately drives. Step-by-step optimisation compounds into improved end-to-end conversion.
  • GA4 Alert: Conversion Drop fires when the end-to-end view-to-purchase rate degrades; the funnel diagnoses where in the path the degradation happened.

Reconciling against the vendor’s own dashboard

Where to look in Google Analytics 4’s own dashboard:
  • Explore → Funnel exploration is the direct equivalent. GA4’s funnel exploration accepts the same five-step ecommerce funnel definition and produces step-by-step drop rates. The Vortex IQ card automates this view with the standard ecommerce schema baked in.
  • Reports → Engagement → Events for the underlying event counts (view_item, add_to_cart, begin_checkout, add_payment_info, purchase) that the funnel computes drops between.
  • Reports → Monetization → Ecommerce purchases for the bottom-of-funnel context.
Why the Vortex IQ funnel may legitimately differ from GA4’s:
  1. Funnel-step inclusion rules. GA4’s funnel exploration lets the merchant configure each step’s matching condition; the Vortex IQ card uses GA4’s standard ecommerce event names without further filtering. Brands with custom event-naming (e.g. add_to_cart_pdp instead of add_to_cart) need to either rename their events to the standard or override the card’s step definitions in profile settings.
  2. Sampling thresholds. GA4 funnel exploration applies its own sampling rules separate from the Reporting API; sampled funnels can produce slightly different step counts than the equivalent Reporting API calls Vortex IQ uses.
  3. Event-count vs user-count. GA4’s funnel exploration defaults to user-count at each step (a user is counted once even if they fired the same event multiple times); Vortex IQ uses event-count to expose the actual event-firing volume per step. Brands seeing different drop rates between the two are seeing the user-vs-event difference, not a methodology error.
  4. Open-funnel vs closed-funnel. GA4 funnel exploration supports both open (users can enter at any step) and closed (users must enter at step 1) modes. The Vortex IQ card uses closed-funnel mode by default, which is the correct framing for ecommerce-flow analysis. Brands wanting open-funnel views can configure this in profile settings.
Cross-connector reconciliation:
  • GA4 funnel-dropoff vs Mixpanel funnel: definitional cousins; Mixpanel’s identity resolution can produce tighter user-cohort funnels than GA4’s session-based view. Brands with both wired find Mixpanel’s funnel typically shows 5-10 percentage points better at intermediate steps because of better user-stitching across sessions.
  • GA4 funnel-dropoff at step 3 vs FullStory rage-click data on the checkout page: useful triangulation. A high checkout-form drop in GA4 paired with elevated rage-click data on FullStory confirms UX friction at the form. Without rage-click confirmation, the drop could be due to genuine user hesitation (price shock at shipping calculation) rather than UX friction.
  • GA4 funnel step 4-to-5 (payment-to-purchase) vs Stripe or Shopify Payments decline-rate data: real reconciliation. The drop at this step should match the merchant’s payment-decline rate within attribution-window differences; large gaps indicate either tracking issues or 3DS abandonment that GA4 captures but the payment processor reports differently.

Known limitations / merchant FAQs

Why is my view-to-cart drop 90+ percent? That seems terrible. It isn’t. 70-90 percent view-to-cart drop is the healthy band for ecommerce. Most product-page visitors are browsers, comparison shoppers, or returning visitors checking on a previously-viewed item; only a fraction add to cart on any given session. The view-to-cart conversion (10-30 percent of viewers add) is one of the most studied ecommerce metrics and the band is well-established. Brands with sub-70 percent drop are usually undercounting view_item events, not converting unusually well. Which funnel step is the most fixable? Almost always begin_checkout → add_payment_info (the form-completion step). Cart-page friction (cart-to-checkout) is harder to fix because the cart page often has commercial constraints (showing shipping cost, requiring login). Payment-to-purchase friction is mostly outside merchant control (payment-vendor routing, 3DS abandonment). The form step is squarely under merchant control: number of fields, autofill support, express-checkout buttons, page-load performance. Optimisation work on this step typically delivers 8-15 percentage points of drop reduction within 60-90 days. My funnel shows the same step-rate week after week. Is the data working? Funnel rates are remarkably stable for established ecommerce brands; week-over-week changes of 1-2 percentage points are normal variance, not signal. The funnel-trend card surfaces the rolling pattern; brands looking for noise are looking too hard. The card flags when something has actually moved (>2σ from baseline). My GA4 ecommerce events fire from a third-party platform (e.g. Recharge for subscription products). Does that affect the funnel? Yes. Third-party-platform events sometimes fire with different schema than GA4’s standard (e.g. Recharge’s checkout events don’t always map cleanly to begin_checkout). The funnel may show artificially high drops at steps where the third-party platform’s events aren’t being captured. Audit the merchant’s GA4 event stream to confirm all five ecommerce events are firing from the relevant flows; missing events are the most common cause of funnel-shape anomalies. Can I customise the funnel steps for my brand’s specific flow? Yes, in profile settings. Brands with non-standard checkout flows (multi-page checkout, marketplace-style cart, subscription-only purchase paths) can override the default step definitions. The card will use the merchant-configured steps and apply the same drop-off computation logic. Why does the funnel sum not equal my conversion rate? End-to-end conversion rate (view_item → purchase) compounds the multiplicative effect of every step rate. A 15 percent view-to-cart × 60 percent cart-to-checkout × 50 percent checkout-to-payment × 85 percent payment-to-purchase = 3.8 percent end-to-end conversion. Brands sometimes confuse the additive view (sum of drops adds up to >100 percent because each drop is computed against a smaller denominator) with the multiplicative conversion. The end-to-end figure on the Ecommerce Conversion Rate card is the multiplicative compound; the funnel-dropoff card shows the per-step granularity. My funnel is healthy at every step but my revenue is still declining. Where do I look? Outside the funnel. A healthy funnel with falling revenue means the merchant is acquiring fewer view_item visits (top-of-funnel traffic decline) or the AOV is declining (cart-mix shift). Check Sessions for traffic volume trend and the merchant’s commerce-platform AOV cards for cart-value trend. The funnel is a conversion-quality measurement; declining revenue at constant conversion quality is a top-of-funnel or cart-economics issue, not a funnel issue. Can Vortex IQ trigger funnel-step alerts to my Slack channel? Yes via the standard Vortex IQ alert routing. Configure alert delivery in profile settings; the funnel-step 2σ alert delivers to the merchant’s chosen channels (Slack, email, Microsoft Teams) when triggered.

Tracked live in Vortex IQ Nerve Centre

Funnel Drop-off is one of hundreds of KPI pulses Vortex IQ tracks across Google Analytics 4 and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.