These settings control what Vexo collects from your mobile app. To change them, open your app's Settings page and go to Mobile Tracking. When you're done, select Save tracking settings.
When this option is cleared, no device records session replays. An app that passes sessionReplay: false to vexo() never records, whatever this option says.
When this option is selected, every frame of a session replay is blurred on the device before it's uploaded. It's on by default. The SDK can't mask individual views yet, so keep blur on if your app shows sensitive content. For more, see App Store & Play Compliance.
When this option is selected, devices upload session replays only over Wi-Fi.
On a paid plan, you can set how long a replay can be:
On the free plan, replays record for up to 5 minutes, and you can't change the length.
The Event Tracking table lists each kind of event that your app sends, how many it sent in the last 30 days, and what it powers in your dashboard. For each row, under Keep, choose how much of it Vexo keeps:
| Event | Keep | Powers |
|---|---|---|
| App open/close | Always on | Downloads, Active users, Sessions, Retention |
| Custom | Always on | Custom events, Cohorts, Power users, Custom dashboards |
| Taps | On, Sample, or Off | Tap heatmaps, Replay timeline |
| Performance | On, Sample, or Off | Performance pages |
| Console | On, Sample, or Off | Replay timeline |
| Screens | On or Off | Popular screens, Screen flow, Funnels, User paths, Web routes, Referrers, UTM |
| Keyboard & rotation | On or Off | Replay timeline |
| Errors & ANRs | On or Off | Errors, Crash-free sessions |
| Network (fetch) | On, Sample, or Off | Network stats |
For Network (fetch), Sample applies only to successful requests. Vexo always keeps failed requests, such as a timeout or no connection, and responses with a 4xx or 5xx status, so you still see every network error. While Network is sampled, Network stats and the replay Network panel show only the requests that Vexo kept.
As you change rows, the table estimates how many events the app would have sent in the last 30 days at the new settings, for each row and in total. When you turn a row off, a warning says which dashboard pages will be empty. Lowering Taps, Performance, or Screens can also make sessions read shorter, because Vexo measures a session from its first event to its last. For Network (fetch), the estimate applies the sample rate to every request. Because Vexo keeps every failed request, the real count can be higher. The table also shows when the settings last changed.
Vexo applies these settings when it receives events, so they work with every SDK version. Events that a setting drops are never stored, so you can't recover them later. The settings apply to every event the app receives, including events from the web SDK. Turning off Network (fetch) also tells vexo-analytics 1.4.0 and later to stop capturing network requests on the device.
For how these settings affect your monthly events, see Turn off or sample event types in Usage and Limits.
While your app is in the foreground, the SDK reports frame health, a performance event, every 10 seconds. To send fewer performance events, set Report frame health every to a longer interval, from 5 to 60 seconds. This requires vexo-analytics 1.14.0 or later. Earlier versions report every 10 seconds.