Skip to main content
Klaritics provides client SDKs for Android, iOS, Web, React Native, Kotlin Multiplatform, and Flutter. Every SDK uses the same initialization pattern: provide your project_id and server_host, then start logging events and user properties. This page covers the concepts shared across all platforms and links to platform-specific setup guides.

​
Supported platforms

Web

Browser and SPA integration via npm or script tag.

Android

Gradle-based Android apps using Maven coordinates.

iOS

Swift and Objective-C apps via Swift Package Manager.

React Native

Cross-platform JS apps for iOS and Android.

Kotlin Multiplatform

Shared Kotlin code across Android, iOS, and other targets.

Flutter

Cross-platform Dart apps for iOS and Android.
Sending data from servers, jobs, or other systems rather than an app? Use the External API.

​
Shared initialization

Every SDK requires two values to initialize:
  • project_id: your Klaritics project identifier, found on the Getting Started page of the dashboard
  • server_host: the URL of your Klaritics instance, for example https://analytics.yourcompany.com
The SDK does not start capturing events until both values are provided. We recommend verifying that the host is reachable at initialization time. Each SDK names these two values differently:

​
API at a glance

The mobile SDKs share one method set, modeled on the Kotlin Multiplatform SDK. The Web SDK follows it where it can, and uses its own names for user and session properties and page views. A dash means the method isn’t available in that SDK. Version history for every SDK is in SDK release notes.

​
Verify your integration

After you initialize the SDK in your app, send a few test events to confirm the setup end to end before you start building dashboards.
1

Trigger a few events in your app

Run your app in a debug build and perform real actions that call logAppEvent. Sign in, tap a button, open a screen, add an item to the cart. Aim for at least 5 to 10 events across a couple of user sessions.
2

Watch events land on the Getting Started page

Open the Klaritics dashboard and go to Getting Started. Newly received events for your project appear here in near real time, along with the platform they came from and the attributes attached to them.
3

Click Complete Setup

Once Klaritics has received enough events from your app, the Complete Setup CTA on the Getting Started page becomes active. Click it to mark your integration as complete and unlock the full dashboard.
4

Build your first dashboard

With events flowing, head to Saved Dashboards to pin charts, funnels, and retention charts, or start from a template to get a working analytics view in minutes.

​
Event and attribute naming

When you log events and attributes from your application, use plain names that describe what happened in your product, for example add_to_cart or product_clicked, with attributes like user_id or item.
Do not use $ as a prefix for events or attributes that you log. The Klaritics SDKs reserve the $ prefix for events and attributes that they add automatically, such as session and device metadata. Names you log that start with $ may collide with SDK-managed data.
For the full naming guidance, see Event and attribute naming.