Anonymous activity

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

When you identify a person, and we merge anonymous activity with the identified person, 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 person, and their previously-anonymous screen view triggers the automation you set up for people who visited the product page.

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