Anonymous activity

Before you identify a profile, calls you make to the SDK are associated with an anonymousId. When you identify that profile, we reconcile their anonymous activity with the identified profile.

In Customer.io, you’ll see anonymous activity in the Activity Log, but we don’t surface anonymous profiles in Customer.io. You won’t be able to find an “anonymous profile” in your workspace, and an anonymous profile can’t trigger automations or get messages (including push notifications) from Customer.io.

When you identify a profile, and we merge anonymous activity with the identified profile, the previously-anonymous activity can trigger automations and cause your audience to receive messages.

For example, imagine that you have an ecommerce app, and you want to message people who view a specific product. An anonymous user looks at the product in question, goes to a different page, and then logs into your app. When they log in, we merge their anonymous activity with their identified profile, and their previously-anonymous screen view triggers the automation you set up for people who visited the product page.

You can return a profile’s anonymous ID at ay time by calling CustomerIO.shared.anonymousId.