Skip to main content
Klaritics provides client SDKs for Android, iOS, Web, React Native, and Flutter. Each SDK uses the same client-facing class name, Klaritics, and the same initialization pattern: provide your app_id and server_host, then start logging events. 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 following RN packaging conventions.

Flutter

Cross-platform Dart apps following Flutter packaging conventions.

​
Shared initialization

Every SDK requires two values to initialize:
  • app_id: your Klaritics application identifier
  • server_host: the URL of your self-hosted Klaritics instance (for example, https://analytics.yourcompany.com)
The SDK does not initialize until both values are provided. Verifying that the host is reachable at initialization is recommended.

​
Client-facing class name

The class you call in your application code is always Klaritics. Do not use KlariticsSDK, KlariticsCore, or any other variant.

​
Event and attribute naming

SDK-generated events use a $ prefix (for example, $app_opened). SDK-sent attributes that are not already part of the chunk model also use a $ prefix (for example, $custom_user_id). Do not add an organization-specific prefix. For full details, see Event naming rules.

​
What is not included

Screen tracking is not part of the current SDK setup. For web apps, URL-based page tracking is configured from the Klaritics dashboard.