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.

In Customer.io, you’ll see anonymous activity in the Activity Log, but we don’t surface anonymous profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.io. You reference a person’s profile attributes in liquid using customer—e.g. {{customer.email}}. in Customer.io. You won’t be able to find an “anonymous person” in your workspace, and an anonymous person can’t trigger campaigns or get messages (including push notifications) from Customer.io.

When you identify a person, and we merge anonymous activity with the identified person, the previously-anonymous activity can trigger campaigns 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 campaign 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.

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: Ientify call
merges events to profile|f f-->i{Did events happen
in past 72 hours?} i-->|yes|j(Events
trigger campaigns) i-.->|no|k(Events do not
trigger campaigns)
Copied to clipboard!
  Contents
Current release
 3.3.0
Is this page helpful?
Chat with AI