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 store anonymous activities on a profile An instance of a person. Profiles start journeys through automations, join segments, and more. You reference a person's profile attributes in messaging using the liquid key customer, like {{customer.email}}.
You can’t trigger automations or send messages like push notifications to anonymous users; however, if you’re on a premium or enterprise plan, you can send anonymous in-app messages.
When you identify a person, we merge anonymous activity with the identified person. And then the identified person’s 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 including their screen view. This triggers the automation you set up for people who visited the product page.
You can return a profile’s anonymous ID at any time by calling CustomerIO.instance().anonymousId.