Analytics-Kotlin Implementation Guide

The Identify method lets you tie a user to their actions and record traits about them. This includes a unique user ID and any optional traits you know about them like their email, name, or address. The traits option can include any information you want to tie to the user. When using any of the reserved traits, be sure the information reflects the name of the trait. For example, email should always be a string of the user's email address.

1
fun identify(userId: String, traits: JsonObject = emptyJsonObject)
2

3
// If <T> is annotated with @Serializable you will not need to provide a serializationStrategy
4
fun <T> identify(userId: String, traits: T, serializationStrategy: KSerializer<T>)

1
analytics.identify("user-123", buildJsonObject {
2
    put("username", "MisterWhiskers")
3
    put("email", "hello@test.com")
4
    put("plan", "premium")
5
});

1
analytics.identify("user-123", Builders.buildJsonObject(o -> {
2
    o.put("username", "MisterWhiskers")
3
        .put("email", "hello@test.com")
4
        .put("plan", "premium");
5
}));
6

7
// or
8

9
analytics.identify("user-123", new YourJsonSerializable());

The Track method lets you record the actions your users perform. Every action triggers an event, which also has associated properties that the track method records.

1
fun track(name: String, properties: JsonObject = emptyJsonObject)
2

3
// If <T> is annotated with @Serializable you will not need to provide a serializationStrategy
4
fun <T> track(name: String, properties: T, serializationStrategy: KSerializer<T>)

1
analytics.track("View Product", buildJsonObject {
2
    put("productId", 123)
3
    put("productName", "Striped trousers")
4
});

1
analytics.track("View Product", Builders.buildJsonObject(o -> {
2
   o.put("productId", 123)
3
    .put("productName", "Striped Trousers")
4
});

The Screen method lets you record whenever a user sees a screen in your mobile app, along with optional extra information about the page being viewed.

You'll want to record a screen event whenever the user opens a screen in your app. This could be a view, fragment, dialog, or activity depending on your app.

Not all integrations support screen, so when it's not supported explicitly, the screen method tracks as an event with the same parameters.

1
fun screen(screenTitle: String, properties: JsonObject = emptyJsonObject, category: String = "")
2

3
// If <T> is annotated with @Serializable you will not need to provide a serializationStrategy
4
fun <T> screen(screenTitle: String, properties: T, category: String = "", serializationStrategy: KSerializer<T>)

1
analytics.screen("ScreenName", buildJsonObject {
2
    put("productSlug", "example-product-123")
3
});

1
analytics.screen("ScreenName", Builders.buildJsonObject(o -> {
2
    o.put("productSlug", "example-product-123");
3
}));
4

5
// or
6

7
analytics.screen("ScreenName", new YourJsonSerializable());

The Group method lets you associate an individual user with a group— whether it's a company, organization, account, project, or team. This includes a unique group identifier and any additional group traits you may have, like company name, industry, number of employees. You can include any information you want to associate with the group in the traits option. When using any of the reserved group traits, be sure the information reflects the name of the trait. For example, email should always be a string of the user's email address.

1
fun group(groupId: String, traits: JsonObject = emptyJsonObject)
2

3
// If <T> is annotated with @Serializable you will not need to provide a serializationStrategy
4
fun <T> group(groupId: String, traits: T, serializationStrategy: KSerializer<T>)

1
analytics.group("user-123", buildJsonObject {
2
    put("username", "MisterWhiskers")
3
    put("email", "hello@test.com")
4
    put("plan", "premium")
5
});

1
analytics.group("user-123", Builders.buildJsonObject(o -> {
2
    o.put("username", "MisterWhiskers")
3
        .put("email", "hello@test.com")
4
        .put("plan", "premium");
5
}));
6

7
// or
8

9
analytics.group("user-123", new YourJsonSerializable());

The Analytics Kotlin utility methods help you work with plugins from the analytics timeline. They include:

• Add
• Find
• Remove
• Reset

There's also the Flush method to help you manage the current queue of events.

The Add method lets you add a plugin to the analytics timeline.

fun add(plugin: Plugin): Analytics

1
val plugin = object: Plugin {
2
    override val type = Plugin.Type.Enrichment
3
    override val name = "SomePlugin"
4
    override var lateinit analytics: Analytics
5
}
6
analytics.add(plugin)

The Find method lets you find a registered plugin from the analytics timeline.

fun find(pluginName: String): Plugin

val plugin = analytics.find(SomePlugin::class)

The Remove methods lets you remove a registered plugin from the analytics timeline.

fun remove(pluginName: String): Analytics

analytics.remove("SomePlugin")

The Flush method lets you force flush the current queue of events regardless of what the flushAt and flushInterval is set to.

public fun flush()

analytics.flush()

The reset method clears the SDK's internal stores for the current user and group. This is useful for apps where users log in and out with different identities on the same device over time.

fun reset()

analytics.reset()

While Analytics Kotlin will automatically track deep links that open your app when the trackDeepLinks Configuration property is set to true. There are some situations when the app is already open that could cause a deep link open event to be missed.

The openUrl function allows you to manually track that a deep link has opened your app while your app was already open:

1
    override fun onNewIntent(intent: Intent?) {
2
        super.onNewIntent(intent)
3
    
4
        // Add a deep-link opened event manually.
5
        // This is necessary when your Activity has a android:launchMode of
6
        // 'singleInstance', 'singleInstancePerTask', 'singleTop', or any other mode
7
        // that will re-use an existing Activity instead of creating a new instance.
8
        // The Analytics SDK automatically identifies when you app is started from 
9
        // a deep link if the Activity is created, but not if it is re-used. Therefore 
10
        // we have to add this code to manually capture the Deep Link info.
11
        
12
        val referrer = "unknown" 
13
        analytics.trackDeepLinkOpen(referrer, intent)
14
    }

For a sample implementation see our Kotlin Sample App.

View the Analytics Kotlin changelog on GitHub.