This article describes the visitor ID attribute and how to use it.
In this article:
Before you begin, familiarize yourself with the following:
Identifying your visitors is a critical step in making full use of Tealium AudienceStream CDP. When certain qualifying visitor events occur, such as a user registering or completing a purchase, there is an opportunity to uniquely identify that visitor using an event attribute such as
customer_id. When one of these identifying attributes is provided in the data layer across multiple sessions, AudienceStream can combine the visitor attributes from those sessions into one master visitor profile using a process called visitor stitching. Visitor stitching uses a visitor ID attribute to identify users across sessions and devices.
A visitor ID attribute is configured in AudienceStream to uniquely identify visitors. When you create a visitor ID attribute, you add an enrichment to set the value to a user identifer, which is an event attribute, such as
customer_id. For visitor stitching to work properly, you must choose a unique user identifier, create a rule to determine when to identify a visitor, and verify that the chosen attribute is unique for each visitor.
Visitor stitching is disabled by default. Contact your account manager to enable it.
The visitor ID attribute is available in the following scope: Visitor.
A visitor ID attribute must meet the following system requirements:
"a1a1a1a1a1") is invalid.
UTF-8 character sets are supported.
The system automatically validates these requirements. You do not need these rule conditions in your visitor ID attribute configuration.
A visitor ID attribute should follow these best practices:
email@example.com, which would be treated as two different IDs in AudienceStream.
@symbol. You may also want to check the string for other values such as,
not setor any text that would not be a valid value for a visitor ID attribute.
See Creating a Visitor ID Attribute for a guide to creating the most accurate visitor ID attribute possible.
Set the value for a visitor ID attribute during a qualifying event, which is an event that occurs when a customer provides a reliable, unique means of identification, such as registering an account or completing a purchase.
A visitor ID attribute should not be a marketing activation ID (such as a gid). These third-party identifiers can be stored as visitor attribute for use in connectors, but are not recommended as visitor IDs.
This enrichment stores a user identifier for a visitor in a visitor ID attribute. For example, when a user registers or signs up, your system might generate an internal ID that is added to the data layer as
customer_id. Use this enrichment to set a visitor ID attribute to
customer_id when the
user_register event occurs.
After a visitor ID attribute is set, it cannot be updated.
WHEN: User Register event occurs (rule)