The e-commerce event sequence
GA4's e-commerce events are not independent — they form an ordered journey: view_item_list, select_item, view_item, add_to_cart, view_cart, begin_checkout, add_shipping_info, add_payment_info, and purchase, with remove_from_cart and refund as branches. The items array threads through them so a product can be followed end to end. This page maps the canonical sequence and why ordering matters for funnels.
The canonical order
The standard retail journey runs view_item_list (a product list) to select_item (a click) to view_item (a product page) to add_to_cart, then view_cart, begin_checkout, add_shipping_info, add_payment_info, and purchase. remove_from_cart and refund are branches off the main path.
Each event shares the items array, so the same product appears consistently from impression to purchase.
Why ordering matters
Funnels rely on events arriving in a coherent order with consistent identifiers. If add_to_cart fires but view_item never does, the funnel cannot attribute the add to a product view. Keeping item_id stable across stages is what makes end-to-end product analysis possible — the sequence is only as good as its weakest, missing step.
- List → select → view → cart → checkout → purchase
- remove_from_cart and refund are branches
- Stable item_id threads the whole journey
How it appears in analytics and logs
A missing event in the sequence creates a funnel blind spot; consistent items parameters let you trace one product across every stage.
Diagnostic use case
Map the standard GA4 retail event order so you can build a complete shopping funnel and spot missing steps.
What WebmasterID can help detect
WebmasterID can record each retail stage first-party so the full purchase funnel is visible without third-party cookies.
Common mistakes
- Skipping mid-funnel events like view_cart.
- Changing item_id between stages, breaking traces.
- Treating each e-commerce event as independent.
Privacy and accuracy notes
The items array carries product data, not customer PII. Keep names, emails, and addresses out of every stage. Educational, not legal advice.
Related pages
- The view_item_list event
view_item_list is a GA4 recommended e-commerce event that fires when a visitor sees a list of products — a category page, search results, or a recommendation row. It carries an items array plus item_list_id and item_list_name so you can attribute impressions to a specific list. It measures product exposure: which lists put which items in front of people.
- 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.
- The purchase event and e-commerce
The purchase event records a completed transaction and anchors all e-commerce reporting: revenue, items, and conversion value. It carries a transaction id, a value and currency, and an items array describing what was bought. The discipline is to record the order, not the customer — product and revenue data belong in the event, personal identity does not.
- Event Explorer
Build the retail funnel end to end.
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.