Send events behavior

Events are recorded into a buffer, which is flushed to the server every 60 seconds and on app shutdown. This period is not configurable.

There might be occasions where the SDK fails to send a batch of events, for example, when the Analytics service is down or the player is offline. Events are stored in memory until they're successfully uploaded or the app is shut down. If there's still no internet connection when the app is shut down, and file system access is available, up to 5MB of events is cached to disk so that they can be uploaded during the next session.

Events are always uploaded with the data they had when they were recorded, including common parameters like platform and session ID. For example, if an event was recorded in a previous session but only flushed days later, it'll keep its association with its original session.

You can also force events to be uploaded immediately by calling the AnalyticsService.Instance.Flush() method. You won’t need to do this in normal use.