---
title: How the SDK works - Capacitor
description: Understand how the Contentsquare SDKs load, track, and send data
lastUpdated: 28 April 2026
source_url:
  html: https://docs.contentsquare.com/en/capacitor/how-the-sdk-works/
  md: https://docs.contentsquare.com/en/capacitor/how-the-sdk-works/index.md
---

> Documentation index: https://docs.contentsquare.com/llms.txt
> Use this file to discover all available pages before exploring further.

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

## Configuration

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

## Tracking

The SDK monitors the application lifecycle events and the view hierarchy, and generates analytics data from the behavior of the app, the content of the screen and the interaction of the user. 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.

## Sending data

📚 [Native Android SDK documentation for Sending data](https://docs.contentsquare.com/en/android/how-the-sdk-works/#sending-data) 📚 [Native iOS SDK documentation for Sending data](https://docs.contentsquare.com/en/ios/how-the-sdk-works/#sending-data)

## Session definition

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.