Checkout progress events in GA4
Checkout progress in GA4 is expressed through distinct recommended events rather than one staged event. Where Universal Analytics used a checkout_progress hit with a step number, GA4 names each stage: begin_checkout, then add_shipping_info, then add_payment_info, then purchase. This page explains how to model the multi-step checkout funnel using those events plus an optional shipping_tier and payment_type parameter.
What this means
Universal Analytics modeled checkout with a single checkout_progress hit carrying a step number. GA4 replaced that with named events for each stage, so the funnel is built from event names rather than a step parameter.
The recommended sequence is begin_checkout, add_shipping_info, add_payment_info, and finally purchase. Each is a documented recommended event with its own parameters.
Stage parameters
add_shipping_info accepts a shipping_tier parameter (for example a delivery speed label); add_payment_info accepts a payment_type. Both carry the items array and a value. Building an exploration funnel over these ordered events reveals where shoppers abandon, replacing UA's enhanced-ecommerce step funnel.
- begin_checkout: checkout starts
- add_shipping_info: shipping_tier label captured
- add_payment_info: payment_type label captured
How it appears in analytics and logs
Seeing each checkout stage as its own event means you can locate exactly where shoppers drop — between shipping and payment, or payment and purchase.
Diagnostic use case
Build a checkout funnel from GA4's discrete stage events instead of a single step-numbered checkout_progress hit.
What WebmasterID can help detect
WebmasterID can record each checkout stage as a first-party event so you can see funnel drop-off without third-party cookies.
Common mistakes
- Trying to send a single GA4 checkout_progress event with a step number.
- Putting card data in payment_type instead of a generic label.
- Skipping stages, so the funnel cannot show where drop-off occurs.
Privacy and accuracy notes
Stage parameters describe shipping tiers and payment types as labels, not card numbers or personal data. Never send payment instrument details. Educational, not legal advice.
Related pages
- The begin_checkout event
begin_checkout is a GA4 recommended e-commerce event that fires when a visitor starts checkout. It carries the items in the order plus currency, value, and an optional coupon. It marks the transition from cart to purchase flow and is the entry point for measuring checkout abandonment — the gap between starting checkout and completing a purchase.
- The add_shipping_info event
add_shipping_info is a GA4 recommended e-commerce event that fires when a visitor provides shipping information during checkout. It carries the order items, currency, value, and a shipping_tier label such as 'Ground' or 'Express'. It is a mid-to-late checkout step, often where unexpected shipping costs cause abandonment, and like all checkout events it must avoid recording the address itself.
- The add_payment_info event
add_payment_info is a GA4 recommended e-commerce event that fires when a visitor submits payment information during checkout. It carries the order items, currency, value, and a payment_type label (such as the card brand or wallet). It is a late-funnel step, just before purchase, and one where privacy discipline matters most: it must record that payment was entered, never the payment details themselves.
- Event Explorer
Build a checkout funnel from stage events.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.