What happens after checkout?

Find the dominant customer paths immediately after a completed checkout.

Edit

Wait for the active Run to finish or be cancelled before changing lifecycle.

Current shared answer

Run #7 ; Analysis Version 5 ; Completed 23 Sept 2026, 05:15 CEST

Explore

Data window: 24 Aug 2026 – 23 Sept 2026 · Europe/Copenhagen Showing top 6 of 12 paths · 10,717 of 13,842 matches

Path preview from the current shared answer: 6 of 12 retained pathsBand width represents matching paths.AnchorNext event2 events laterCheckout completed to Checkout started, 4,156 matching pathsCheckout started to Support opened, 4,156 matching pathsCheckout completed to Checkout completed, 2,523 matching pathsCheckout completed to Payment failed, 2,523 matching pathsCheckout completed to Order viewed, 1,187 matching pathsOrder viewed to Product viewed, 1,187 matching pathsCheckout completed to Support opened, 1,020 matching pathsSupport opened to Checkout started, 1,020 matching pathsCheckout completed to Refund requested, 940 matching pathsRefund requested to Order viewed, 940 matching pathsCheckout completed to Payment failed, 891 matching pathsPayment failed to Refund requested, 891 matching pathsCheckout completed, 10,717 matching paths at AnchorCheckout completed10,717 · 77%Checkout started, 4,156 matching paths at Next eventCheckout started4,156 · 30%Support opened, 4,156 matching paths at 2 events laterSupport opened4,156 · 30%Checkout completed, 2,523 matching paths at Next eventCheckout completed2,523 · 18%Payment failed, 2,523 matching paths at 2 events laterPayment failed2,523 · 18%Order viewed, 1,187 matching paths at Next eventOrder viewed1,187 · 9%Product viewed, 1,187 matching paths at 2 events laterProduct viewed1,187 · 9%Support opened, 1,020 matching paths at Next eventSupport opened1,020 · 7%Checkout started, 1,020 matching paths at 2 events laterCheckout started1,020 · 7%Refund requested, 940 matching paths at Next eventRefund requested940 · 7%Order viewed, 940 matching paths at 2 events laterOrder viewed940 · 7%Payment failed, 891 matching paths at Next eventPayment failed891 · 6%Refund requested, 891 matching paths at 2 events laterRefund requested891 · 6%

Analysis composition

customer_event_stream

Data Source
main.customer360
event_time is within Last 30 days Timezone:Europe/Copenhagen
channel IN ('mobile', 'web')

Customer events

Event Model
Version 3
Checkout completed
  • event_name = 'checkout_completed'
  • AND payment_status IN ('paid', 'captured')
Any event draws from all 9 definitions

Customer sessions

Journey Profile
Version 3

Grouped by

customer_id

Ordered by

event_time event_id

Journey boundary

30 min inactivity

Pattern

Total path 1–3 events Overlapping matches

Measures

Matches

Occurrences found

Elapsed time

median

Team feedback