How the SDK works

Contentsquare SDK requires the application to be wrapped into a ContentsquareRoot widget. After that, the SDK works by automatically launching when the app starts.

Upon initialization, our SDK fetches its configuration from our servers. Depending on the segmentation size defined in your contract, it will start collecting data from system and user events detected during runtime.

The SDK monitors application lifecycle events and the view hierarchy, generating analytics data from app behavior, screen content, and user interaction. These events are stored locally and eventually sent to our servers in batches. We aggregate this data to create actionable visual insights in our Web Application, enabling you to gather insights.

Checkout the Native Android SDK documentation for Sending data

A session represents a single period of user interaction in the app. In Contentsquare, a session ends when the user has spent a certain amount of time outside the app. The SDK checks this when an app start or app show event is detected. This time spent outside the app, ending a session is set to 30 minutes by default. But it can be changed if it is requested.

If the app is put in the background or killed (intentionally by the user or by the OS) but the user comes back within 30 minutes, it will not end the session. These events are considered to be part of a session.