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.

A session represents a single period of user interaction in the app. In Contentsquare, the SDK marks the start of a session when an app start or app show event is first detected.

A session ends when the time spent outside the app reaches 30 minutes. This is the default value which can be changed upon request.

If the app is put in the background or killed (intentionally by the user or by the OS) and the user comes back within the next 30 minutes, subsequent events are considered part of the same session.