> This page is part of the [Customer.io documentation](https://docs.customer.io). For the complete index, see [llms.txt](https://docs.customer.io/llms.txt).
> Last updated: July 15, 2026

# Track events

 There's a new version available!

These pages cover version 5 of our SDK, but a newer version is available. In general, we suggest that you update to the latest version to take advantage of new features and fixes.

*   Are you new to our SDKs? [Check out the latest docs.](/integrations/sdk/react-native/getting-started)
*   Otherwise, [learn about updating to the latest version](/integrations/sdk/react-native/whats-new/)

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.

## Track an event

The `track` method helps you send events representing your audience’s activities to Customer.io. When you send events, you can include event `properties`—information about the person 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 person in your workspace.

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.
*   `properties` (Optional): Additional information that you might want to reference in a message. You can reference data 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 `{{customer.first_name}}`.](/journeys/liquid/using-liquid) in the format `{{event.<attribute>}}`.

```javascript
import { CustomerIO } from "customerio-reactnative";

CustomerIO.track("event_name", { 
  propertyName: propertyValue 
});
```

 Perform downstream actions with semantic events

Some downstream actions don’t neatly map to our simple `identify`, `track`, and other calls. For these, we use “semantic events,” events that have a special meaning in Customer.io and your destinations. See [Semantic Events](#semantic-events) for more information.

### Anonymous activity

If you send a `track` call before you `identify` a profile, we’ll attribute the event to an `anonymousId`. When you identify the profile, we’ll reconcile their anonymous activity with the identified profile.

When we apply anonymous events to an identified profile, the previously anonymous activity becomes eligible to trigger automations in Customer.io.

## Semantic Events

Some actions don’t map cleanly to our simple `identify`, `track`, and other calls. For these, we use “semantic events,” events that have a special meaning in Customer.io and your destinations.

These are especially important in Customer.io for destructive operations like deleting a profile. When you send an event with a semantic `event` name, we’ll perform the appropriate action.

For example, if a person decides to leave your service, you might delete them from your workspace. In Customer.io, you’ll do that with a `Delete Person` event.

```javascript
CustomerIO.track("User Deleted)
```

Version[](https://github.com/customerio/customerio-reactnative/releases/tag/6.5.2 "See this release in GitHub")

6.5.2 (Current)5.3.04.11.03.9.12.5.1

*   *   [Track an event](#track-an-event)
        *   [Anonymous activity](#anonymous-activity)
    *   [Semantic Events](#semantic-events)

Copy page

Copy page [Download .md](/integrations/sdk/react-native/5.x/tracking/track-events.md) [Download React Native 5.x SDK bundle](/files/react-native-5.x-sdk-docs.md)

Is this page helpful?

![](https://docs.customer.io/images/export-success.png) ![](https://docs.customer.io/images/export-failure.png)

# How can we make it better?

Close

Do you need help from Customer.io support?  No  
 Yes

What part of Customer.io do you need help with? 

How can we improve this page?

Email (optional):  Please provide a valid email address

 I am not a bot

 

We appreciate your feedback!

Our support team will contact you as soon as possible