Track events
Events represent things people do in your app so that you can track your audience's activity and metrics. Use events to segment your audience, trigger automations, and capture usage metrics in your app.
This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't send events before you identify people!
Track a custom event
After you identify a profile, you can use the track method to send events representing their activities to Customer.io. When you send events, you can include event data—information about the profile or the event that they performed.
In Customer.io, you can use events to trigger automations and broadcasts. Those automations might send someone a push notification or manipulate information associated with the profile in your workspace. You can reference the data in your event to segment A segment is a group of people in your workspace. Use segments to trigger automations, track membership over time, or fine-tune your audience. There are two types of segments: data-driven and manual. Data-driven segments automatically update when people start or stop matching criteria. Manual segments are static. A syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person's first name, you might use the variable {{customer.first_name}}.
Events include the following:
name: the name of the event. Most event-based searches in Customer.io hinge on the name, so make sure that you provide an event name that will make sense to other members of your team.attributes(Optional): The body of the event. You can reference attributes in messages and other workflow actionsA block in an automation workflow—like a message, delay, or attribute change.
using liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person's first name, you might use the variable
in the format{{customer.first_name}}.{{event.<attribute>}}.
CustomerIO.instance().track(
name = "purchase",
attributes = mapOf("product" to "socks", "price" to "4.99")
)Screen view events
Screen views are events that record the pages that your audience visits in your app. They have a type property set to screen, and a name representing the title of the screen or page that a profile visited in your app.
Screen view events let you trigger automations An automated process people enter when they meet your criteria. An automation has a trigger (who enters, and when), a workflow of messages and actions, and exit criteria (when they leave). A person's path through the workflow is their journey. A group of people who match a series of conditions. People enter and exit the segment automatically when they match or stop matching conditions.
Enable automatic screen tracking
When you enable automatic screen tracking, the SDK sends an event every time a person visits a screen in your app. You can turn on automatic screen tracking by appending autoTrackScreenViews(true) to CustomerIO.Builder.
When automatically tracking screen events, we capture the name of the screen with the following priority from highest to lowest:
- We check if the current
Activityhas alabelin the manifest file. If it does, the SDK will use the value forlabel. - We get the class name of the
Activityand use that value.
The SDK will take whatever value it receives and will strip the word Activity from it. Example: If you have an Activity with the manifest label or class name ProfileActivity, the SDK will track the screen view with the name Profile.
CustomerIO.Builder(
siteId = "your-site-id",
apiKey = "your-api-key",
appContext = this
)
.autoTrackScreenViews(true)
.build()If you want to send more data with screen events, or you don’t want to send events for every individual screen that people view in your app, you can send screen events manually.
Send your own screen events
Screen events use the .screen method. Like other events, you can add a map of attributes object containing additional information about the screen event or the currently-identified profile.
CustomerIO.instance().screen(
name = "baseballDailyScores",
attributes = mapOf("prevScreen" to "homescreen", "secondsInApp" to "120")
)