Version

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.

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 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.

flowchart LR a(Anonymous user opens app) a-->|track calls|z subgraph z [Anonymous activity] direction LR u(anonymous page view) y(anonymous event) end subgraph f [User profile] direction LR g(screen view) h(event) end z-->|User logs in: Identify call merges events to profile|f f-->i{Did events happen in past 72 hours?} i-->|yes|j(Events trigger automations) i-.->|no|k(Events do not trigger automations)