Documentation

Analytics

Optional usage analytics for Pro projects. Off by default until you enable it and add the module to your app.

Pro unlocks optional privacy-first analytics: enable in the Analytics tab, add a small module to your app, and see activity by city, country, and platform — random id per install, no cookies, no ad trackers when used as documented.

How it works

Upgrade the project to Pro.
Open the Analytics tab and click Enable analytics.
Follow the setup guide (agent or manual) to add a small kembo-analytics module alongside your auth SDK.
On app start, the module calls GET /api/v1/project and only tracks when analyticsEnabled is true.
Call kemboTrack() on navigation or key actions. Events appear in the dashboard within seconds.

What is collected

Event names (e.g. screen_view).
Platform (iOS, Android, web).
Coarse location — city and country when available from the edge.
A random identifier per install stored on the device (not linked to Kembo auth, email, or name).

What is not collected

IP addresses (not stored).
Advertising IDs or third-party trackers.
Cookies (web analytics uses the same per-install id in storage).
Raw paths with emails, UUIDs, or long numeric IDs — sanitized before storage.

Visitor counting

Unique visitors are estimated using a daily hash of the per-install device id. The raw device id is not stored server-side. Old events without a visitor hash may not count toward unique visitors until the app sends events with the updated module.

Privacy policy snippet

Paste text like the following into your App Store, Play Store, or web privacy policy when analytics is enabled. The dashboard Analytics tab provides a copy-ready snippet for your project.

We use Kembo Analytics to understand how our app is used. It collects usage statistics (such as screen views, platform, and coarse location: city and country). The app stores a random identifier on your device to count unique visitors; it is not linked to your Kembo account, email, or name. Our analytics provider keeps only a daily hash of that identifier and does not store IP addresses or account IDs. Kembo Analytics does not use cookies or advertising trackers.

Review the Data Processing Agreement and Privacy Policy for platform-level details.

Retention & k-anonymity

Events are retained for up to 365 days, then deleted automatically.
Country and city breakdowns with very low counts are rolled into "Other" to reduce re-identification risk.
You can disable analytics anytime from the dashboard. New events stop immediately; stored events follow the retention policy.

Dashboard charts

The Analytics tab shows:

Event volume over time (hourly or daily ranges).
Unique visitors for the selected period.
Breakdowns by platform, country, city, and top events.
A live feed of recent events.

Related guides

How it works

Upgrade the project to Pro.

Open the Analytics tab and click Enable analytics.

Follow the setup guide (agent or manual) to add a small kembo-analytics module alongside your auth SDK.

On app start, the module calls GET /api/v1/project and only tracks when analyticsEnabled is true.

Call kemboTrack() on navigation or key actions. Events appear in the dashboard within seconds.

Paste text like the following into your App Store, Play Store, or web privacy policy when analytics is enabled. The dashboard Analytics tab provides a copy-ready snippet for your project.

We use Kembo Analytics to understand how our app is used. It collects usage statistics (such as screen views, platform, and coarse location: city and country). The app stores a random identifier on your device to count unique visitors; it is not linked to your Kembo account, email, or name. Our analytics provider keeps only a daily hash of that identifier and does not store IP addresses or account IDs. Kembo Analytics does not use cookies or advertising trackers.