Insights and tracking
The funnel, sessions and conversion rate
Storefront events from the theme line, checkout steps from the checkout and paid from the webhook make the funnel on Home and Insights.
Updated
Where the numbers come from
The theme line reports storefront events to LatchPay as soon as it is in your theme, even while the LatchPay checkout is switched off; the checkout reports its own steps; the payment webhook reports the paid step. Home shows Sessions, Conversion rate and the short storefront funnel; Insights shows the full funnel, top customers by lifetime spend after refunds, and abandoned checkouts. Tracking shows whether the theme line is live, the last event and the events stored.
The funnel stages
Sessions and product views (theme line)
A page view on any page; a product view on a product page, with the variant and price when the theme exposes them.
Added to cart (theme line)
From the Cart AJAX API your theme uses, or from the plain add-to-cart form.
Reached checkout, contact entered, payment attempted (checkout)
The LatchPay checkout opened; an email was typed; Pay now was pressed.
Paid (payment webhook)
Written only when Whop confirms the payment, never from a browser, one per session; test payments do not count.
Sessions and conversion
- A session is one browser session on your store, under a random first-party id the theme line keeps for that store.
- The funnel counts distinct sessions per stage for the selected range (Today to 12m, or a custom range).
- Conversion rate is paid sessions divided by all sessions in the range.
Why they differ from Shopify, Meta or GA4
LatchPay counts from its own first-party id and stops counting when a browser opts out with Global Privacy Control or Do Not Track. Ad blockers drop a share of browser events. Shopify, Meta and GA4 each count in their own way with their own time-outs and consent rules, so the numbers land close but not equal.
What is never stored
No IP address, no user agent, no name, no email and no query string is part of an event; account pages are stored as just "/account". Events are deleted after 13 months. The privacy notice describes it in full.