Working with user "endpoints"

An endpoint is a unique identifier that represents a specific device or platform used by one of your users.

Examples of endpoints include email addresses, mobile phone numbers, iOS and Android mobile application push tokens, a random hash representing a browser session and many more.

Endpoints tell Vero exactly which device or platform to message.

Why endpoints?

In today's world users engage with businesses via multiple devices and channels. Vero 2.0 has been designed from the ground-up to support any messaging channel.

Endpoints provide a way to capture this reality elegantly: a single user will have multiple endpoints.

Data Vero stores about your endpoints

Vero 2.0 does not store any user-level data included in an audience you load (such as first names, last names, etc.) however Vero 2.0 does store information about endpoints and profile id values.

As soon as an audience is imported, Vero 2.0 will scan each audience member and find or create an internal record for each user profile, stitching profiles based on the provided id and endpoint values (such as email, phone_number or similar). Read more about identity stitching here.

Vero is designed to be the source for truth for your messaging subscriptions and the records of messages you send.

Whenever you send a campaign to an audience, Vero will keep a record of all of the endpoints that were messaged along with a record of all of their message interactions.

Learn more about how Campaign subscriptions are handled.