How the SDK works

The SDK auto-starts at application launch, attaches to the current process, and intercepts the events and gestures needed to capture analytics data.

Once started, our SDK fetches its configuration from our servers. Then, depending on the segmentation size (defined by our team when you sign a contract) and the user consent status, it will start collecting analytics data from system and user events it detects from the runtime.

The SDK monitors the application lifecycle events, the view hierarchy, and generates data from the behavior of the app, the content of the screen and the user interactions. These events are then locally stored, and eventually sent to our servers in batches. We then aggregate that data to create usable visual information into our Web Application, which you use to gather insights.

See Session Replay Initialization to learn how Session Replay data collection works.

Analytics data are sent in batches of maximum 50 events. Requests are triggered when network conditions allow for the server to be reached and:

• The current batch of events has reached 50
• Or the app is put in background

Our requests use lowPriority ↗.

See Session Replay Requests to learn more about how Session Replay data is sent.

See Send Crash data to learn more about how crash data is sent.

A session is one continuous period of user interaction. It starts upon app launch and persists through state changes, including putting the app in the background or terminating and restarting it. As long as users interact at least once every 30 minutes, it remains the same session.