How the SDK works
The SDK must be initialized by calling Contentsquare().start() and requires Contentsquare().optIn() to begin collecting data.
Configuration
Section titled ConfigurationUpon 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.
Tracking
Section titled TrackingThe 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.
Sending data
Section titled Sending dataCheckout the Native Android SDK documentation for Sending data
Checkout the Native iOS SDK documentation for Sending data
Session definition
Section titled Session definitionA 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.