Offline events
Queue mobile events offline and flush them with original timestamps.
Last updated June 3, 2026
Mobile SDKs keep offline events for at most 30 days and preserve their original timestamps. Visitor IDs rotate after one year. An HTTP 410 erasure response clears matching queued events and rotates the active visitor and session.
Prerequisites
- A mobile SDK installed
- Local storage available
- Network access when the app comes back online
Steps
Use the built-in queue
Queueing is always enabled. React Native can override maxQueueSize; native SDKs use the fixed 1,000-request cap.
Record event timestamps
The SDK stores when the event happened, not when it was uploaded.
Flush on reconnect
Queued events send during the SDK's periodic flush or when flush is called explicitly.
Options / Configuration
| Option | Type | Required | Description |
|---|---|---|---|
| maxQueueSize | number | no | React Native queue cap; native SDKs use 1,000 |
| maximumAge | 30 days | fixed | Older queued events are discarded |
| visitorLifetime | 1 year | fixed | Expired device identities rotate automatically |
What happens next
Use Realtime to verify late arrivals show the original event time and delayed indicator.
Verify your setup
Verify your setup
Troubleshooting
Queued events never flush
Confirm local storage permissions, network access, and that the tracker remains active long enough to flush.
Was this page helpful?