ROLLER checkout events, in order | Activate Games Analytics Knowledge Base

Every event in this list comes from ROLLER inside the checkout, is relayed by the bridge, and carries venue_slug, venue, and on purchase, roller_amount_charged, value, transaction_id, and items.

Order	Event	What it means	Watch out for
1	`view_item_list` or `begin_checkout`	The slide-out opened.	Which one fires first depends on the venue's ROLLER configuration. About half the venues open on the product list (`view_item_list` first) and half on a step that fires `begin_checkout` first. Neither is wrong, but you cannot use `begin_checkout` alone as "slide-out opened" across all venues. Use "any checkout event" instead.
2	`view_item`	Visitor opened a specific product or session.
3	`add_to_cart` / `remove_from_cart`	Cart changed.	Some products (large groups) skip straight to checkout.
4	`checkout_progress`	Visitor moved to the next step.	Fires several times per booking.
5	`initiate_checkout`	Visitor has items and clicked through to enter their details. ROLLER's name is `checkout_button_clicked`.	Can fire more than once if the visitor goes back to add more. Count users, not events.
6	`purchase`	Paid.	`value` is the full booking (price times quantity across items). `roller_amount_charged` is what was charged today, usually a deposit. Revenue is `value`.

A note on click_booknow: it is a website event, not a ROLLER one, and it fires whether or not a location was selected. About a quarter of Book Now clicks do not open the slide-out for that reason. Use it as interest, not as checkout opens.

What counts as a conversion for ad platforms: Initiate Checkout is initiate_checkout, not begin_checkout and not click_booknow. Purchase is purchase with value. The attached one-pager walks through why.