We've changed how the Jumbo Lottery Platform (JLP) tracks user sessions for non-native app checkouts so that a single journey across the mobile app and the mobiel web is now counted as one connected session, rather than being split in two.
Why this matters
When a supporter buys a ticket in the iOS app the payment is completed via the mobile web due to App Store limitations. Until now, the app activity and the web activity were treated as two separate sessions. That artificially inflated session counts and made sessions look shorter than they really were, so any journey that crossed between app and web didn't reflect what supporters were actually doing.
Now, when a supporter moves between the app and mobile web as part of the same journey, the events from both are tied to the same session in Amplitude.
What's new
One session across app and web
When the website opens as a result of in-app activity (for example, heading to the checkout page to complete a purchase), the app passes its current session details through to the mobile web. The web page reads those details on load and continues the same session instead of starting a fresh one. This works in both directions: a supporter moving from app to web, or from web back into the app, keeps the same session throughout.
More accurate session reporting
Because app and web events are now grouped under a single session, the numbers you see in Amplitude better reflect real supporter behaviour:
- Session counts are no longer inflated by a single journey being split across platforms
- Session lengths reflect the full journey rather than being cut short at the app-to-web handover
- A supporter going from app to web to finish a purchase no longer registers as a brand-new session when they land on the web
No impact on standalone sessions
Sessions that don't cross between app and web are completely unaffected. If a supporter starts on the web or in the app on its own, session tracking behaves exactly as it always has.
Who this impacts
This is an analytics improvement, so there's nothing supporters or operators need to do. It mainly benefits anyone using JLP analytics to understand supporter journeys, giving you cleaner session data for any flow that moves between the mobile app and the web.
Note: There's a rare edge case where a supporter stays on the web page for longer than the app's session timeout. Carrying the session back into the app in that situation is being handled separately and isn't part of this change.