Checkout Usability
Part of Checkout measurement
Measuring checkout completion by payment method
Calculate payment-method completion while keeping attempts, retries, method switches and pending outcomes distinct.
To measure completion by payment method, separate submitted payment attempts from checkouts that finish with a method. Record the method first submitted, any later method and the final order outcome. A method merely displayed to a shopper is neither a submitted attempt nor a completed order.
Choose the rate that answers the question
- Attempt success rate:successful submitted attempts using a method divided by submitted attempts using that method with a known final outcome. Preserve each attempt’s outcome, including failures followed by a retry.
- Same-method order completion:distinct checkouts that first submitted a method and later completed an order with that same method, divided by distinct eligible checkouts that first submitted it within the stated cohort and outcome window.
Show the numerator and denominator with each rate. Report pending or unknown outcomes separately and state when a cohort is mature enough to compare.
The first rate describes attempt handling; the second describes whether shoppers finished with the method they initially tried. Neither shows whether offering that method created additional orders: a buyer who used a wallet might otherwise have used a card.
Attempt Success Rate vs Same-Method Order Completion
- Attempt Success Rate
- Successful submitted attempts ÷ Submitted attempts with known outcome
- Same-Method Order Completion
- Distinct checkouts completing with first-submitted method ÷ Eligible checkouts in cohort
Preserve retries and method switches
Keep a checkout or order reference, an attempt reference, the method actually submitted, the submission time, each attempt’s outcome and the final order reference. A provider’s current payment status may no longer show that an earlier attempt failed, so retain attempt events or equivalent history.
| Path | Attempt view | Same-method order view |
|---|---|---|
| Card succeeds first time | One successful card attempt | Completed with the first submitted method. |
| Card fails, then succeeds on retry | One failed and one successful card attempt | Completed with the first submitted method; counted once. |
| Card fails, then wallet succeeds | Failed card attempt and successful wallet attempt | Excluded from card same-method completions; record the wallet as the final method. |
| Payment remains processing | Pending attempt | No confirmed completion yet under a paid-order definition. |
Keep later outcomes linked to their original cohort, and document how a report changes when an outcome arrives after its first run.
Checkout Path Handling: Retries and Method Switches
- Card succeeds first timeOne successful card attempt → Completed with first method
- Card fails, then succeeds on retryOne failed, one successful card attempt → Counted once as same-method completion
- Card fails, then wallet succeedsFailed card + successful wallet → Excluded from card same-method completions; final method is wallet
- Payment remains processingPending attempt → No confirmed completion under paid-order definition
Check what analytics can tell you
GA4 defines add_payment_info as submission of payment information. That event does not confirm provider acceptance.
Verify that your analytics implementation retains the joins between individual attempts and completed orders, and records the final payment method. Use dependable order and provider records, or an event design that retains those joins.
Keep method labels consistent across systems. Decide whether a card used through a wallet is reported by its customer-facing wallet, underlying card type, or both in separate fields.
Check the method actually used rather than inferring it from a displayed button. Where an option appears only to eligible shoppers, show its eligible exposure count before interpreting selection.
Key Implementation Checks for Payment Method Tracking
- Verify GA4 `add_payment_info` event captures submission, not provider acceptance
- Retain joins between individual attempts and completed orders
- Ensure consistent method labels across systems (e.g., wallet vs underlying card)
- Record actual method used, not inferred from displayed button
- Show eligible exposure count for options only shown to eligible shoppers
Use a difference to choose what to inspect
Compare like periods, order types and eligible customers. A low attempt-success rate could reflect a provider refusal, an interrupted external step or a missing outcome record. Inspect the underlying attempts before naming a cause.
A useful implementation review would trace a successful purchase, a retry, a method switch and a pending outcome through analytics, the order record and the provider record. Record which identifiers join.
Critical Metrics for Payment Method Analysis
- Attempt Success Rate
- Measures handling of payment attempts
- Same-Method Order Completion
- Measures whether shoppers finish with their initial method
- Pending or Unknown Outcomes
- Report separately; track maturity of cohort
