Integrations

There are two ways to send data into Klaritics. Most products use both: SDKs for what users do in the app, and the External API for what happens on your servers.

Client SDKs

Track events from inside your web and mobile apps. The SDK handles sessions, device IDs, and batching for you.

External API

Send events and user properties over HTTPS from backend services, jobs, warehouses, and CRMs.

Which one to use

	Client SDKs	External API
Runs in	Your web or mobile app	Your servers
Use it for	User actions inside the app	Server-side events, backfills, data from other systems
Credential	`project_id`	`project_id` plus an API key
Safe to ship to end users	Yes	No — the API key must stay server-side
Sessions and device IDs	Handled by the SDK	You send `user_id` / `device_id` yourself
End-user IP	Captured automatically	You must send `source_ip`

Keep identifiers consistent across both. An event sent through the External API should use the same user_id your app passes to the SDK, so both streams describe the same person.

Get Started

Cohorts

Product Analytics

Data

Behavior Analytics

Charts

Default Templates

Saved Charts

Saved Dashboards

Settings

Deployment

Reference

Integrations

Client SDKs

External API

Which one to use

Available SDKs

Web

Android

iOS

React Native

Flutter

Kotlin Multiplatform

Client SDKs

External API

​Which one to use

​Available SDKs

Web

Android

iOS

React Native

Flutter

Kotlin Multiplatform

Which one to use

Available SDKs