Getting Started
Your application’sbuild.gradle must have a compileSdk of 35+ and minSdk of 23+, and use Android Gradle Plugin (AGP) 8.1+.
- Apply the
kotlin-androidplugin in your app’sbuild.gradlefile.
- Or update to Android Gradle Plugin 8.4.0+.
Related Google issue regarding usage of Jetpack Compose dependency versions 1.6+.
Installing the Library
The library is distributed through Maven Central. Add the Userpilot module to yourbuild.gradle as a dependency and replace <latest_version> with the latest release version. Release notes are available here.
Initialize the SDK
Initialize Userpilot once in your Application class to ensure the SDK is ready as soon as your app starts. Replace<APP_TOKEN> with your Application Token from the Environments Page.
Note for Apps Using AndroidX Startup
If your application also usesandroidx.startup.InitializationProvider, you should not set tools:node="ignore" on this provider to disable it. Doing so will prevent the Userpilot SDK from being initialized correctly.
Instead, make sure to merge the provider declarations using: tools:node="merge"
This ensures that your custom initializers and the Userpilot initializer both get registered properly.
Identify Users (Required)
Identify unique users and companies (groups of users) alongside their properties. Once identified, all subsequent tracked events and screens will be attributed to that user. Recommended Usage:- On user authentication (login): Immediately call
identifywhen a user signs in to establish their identity for all future events. - On app launch for authenticated users: If the user has a valid authenticated session, call
identifyat app launch. - Upon property updates: Whenever user or company properties change.
- The
idkey is required in company properties to identify a unique company. - Userpilot supports String, Numeric, and Date types.
- Send date values in ISO8601 format.
- If you plan to use Userpilot’s localization features, pass the user property
locale_codewith a value that adheres to ISO 639-1 format. - Userpilot’s reserved properties have pre-determined types and improve the profiles interface in the dashboard:
- Use key
emailto pass the user’s email. - Use key
nameto pass the user’s or company’s name. - Use key
created_atto pass the user’s or company’s signup date.
- Use key
Track Screens (Required)
Tracking screens is crucial for unlocking Userpilot’s core engagement and analytics capabilities. Screen views are used to trigger eligible in-app experiences, improve targeting, and provide context for analytics by associating subsequent events with the currently active screen.- Auto Capture
- Manual Tracking
Userpilot SDK supports automatic screen tracking for Android applications, allowing screen views to be captured without manually sending screen events.When Auto Capture is enabled, the SDK automatically detects and tracks screens across your app lifecycle.
Kotlin
Track Events
Log any meaningful action the user performs. Events can be button clicks, form submissions, or any custom activity you want to analyze. Optionally, you can pass metadata with the event to provide specific context.Logout
When a user logs out, calllogout() to clear the current user context. This ensures subsequent events are no longer associated with the previous user.
Anonymous Users
If a user is not authenticated, callanonymous() to track events without a user ID. This is useful for pre-signup flows or guest user sessions.
Experiences
Trigger a specific experience programmatically using its ID. This API allows you to manually initiate an experience within your application.Configuration (Optional)
Example Usage