The User Journey report gives you the complete, cross-source timeline for a single user in one view: every impression, click and event tied to them, including activity that happened before they were attributed to a source. This makes it the go-to report when you need to reconstruct exactly what a user did and when - whether you're answering a support question, QA-testing an SDK integration, or investigating a suspicious conversion.
How to Generate a User Journey Report
Go to Reports > User Journey
Select the App
Select the Store App
Select the Date range (and time range, if you need to narrow to a specific window)
User (optional) - search for or pick a specific user to see their individual journey. Leave this empty to see journeys across all users matching your other filters.
Sources (optional) - filter to one or more of:
Clicks
Installs & Events
Impressions
Cohort Filters (optional) — click + Add Filter to narrow the report down further.
Click Generate Report
💡Leaving User empty is useful for scanning activity broadly, but the report is most powerful when you're tracing one specific user, drop in their ID to pull their entire cross-source history in one place.
Table vs. Timeline View
Once generated, you can view the report as a Table or a Timeline. Switch between the two using the toggle at the top of the report.
Table
The table view lists every event chronologically, with one row per event. Columns include:
Time — when the event occurred
Source — whether the row is a Click, Event, or Impression
Event — the specific event name (e.g. Open, Install, Invalid)
Offer — the offer associated with the event
Publisher — the publisher/traffic source
Country
Device
OS
💡 Rejected or invalid events (shown as Invalid under Event) appear in the report too, not just successful ones. This makes the report especially useful for fraud and QA investigations, since you can see exactly what was rejected and where in the sequence it happened.
Timeline
The timeline view plots the same events visually along a chronological axis, useful for quickly spotting gaps, bursts of activity, or the exact sequence of events leading up to a conversion.
Use Cases
Investigating a support query about a missing conversion
A publisher reports that a user completed an offer but the conversion wasn't credited. Search for the user in the User field, generate the report, and review their full timeline, click, install, and event, to see exactly where the attribution chain broke down or whether the event was rejected and why.
QA-testing a new SDK integration
After integrating the SDK into a new app build, filter by your test User and Store App, then generate the report to confirm impressions, clicks, and events are all landing in the expected order before releasing to production.
Fraud investigation
When a player or user is flagged by fraud detection, pull their User Journey report to see their complete pre- and post-attribution activity in one place, useful supporting evidence alongside the dedicated fraud reports.