For additional background on how Localytics collects data, see Analytics Key Concepts from our User Guide.
The process for data making its way from a device to the Localytics dashboard is as follows:
- User interacts with your app.
- Data is recorded in real-time and recorded locally on the device.
- When the session is closed, an
upload()call is made. The upload operation transmits the locally-stored data to Localytics' systems via an API call is made.
- Localytics receives the data and the data passes through a number of processing steps.
- Data is displayed on the Localytics dashboard.
Once Step (3) is completed – meaning that the user has finished the session and an
upload() call has been made – the amount of time it takes for that data to show up in the dashboard is generally a few minutes (we conservatively suggest 10 minutes). That's the amount of time it takes the data to pass through our processing pipeline.
The notable exception to this rule is if behaviors occur while a device is offline, or if the upload can't complete due to idiosyncratic conditions like network speed or a user hard-closing the app. In these cases, Localytics will preserve the locally-stored data (step 2) and then upload that data (step 3) at the next available opportunity, i.e.next session start.
This exception sometimes generates questions or confusion. For example: If I look at data for a given date right now and then again evaluate data for the same date several days from now, why might the results be different?The answer is that some users will interact with your app on that original date 1 (step 1) and Localytics will store records of this activity locally with timestamps for that day (step 2), but the actual transmission of that data (step 3) happens at a later time.
If data are not uploaded at the end of a session, the information (up to 10K Events) will be stored on the device for up to 28 days.