Attributes are used to define data associated to any of the following: the properties of a visitor, the characteristics of a visitor's session, and any event data collected in real-time. Common examples of Attributes include Email Address, Member ID, Product Category, Date of Last Visit, and Active Browser to name a few. Attributes are the foundation of your implementation, helping you to understand your customers' behavior and interaction with your brand.
In this article, you'll learn about the following:
Attributes are the building blocks of your solution. They define the data that flows from your sources of data through to your vendor integrations. They are used in rule definitions, audience creation, and connector settings. Attributes have the following properties, which you will set when you define them: Scope, Data Type, Enrichment, and Rule.
Scope refers to how long an Attribute persists in real time.
The following Scopes are supported:
Omnichannel Attributes are defined when you define your file imports. Read more about importing Omnichannel data.
Data Type refers to the format in which the Attribute value can be stored. Attributes come in a variety of types, from the basic Number and String, to the more powerful Tally and Badge.
The following data types are supported:
|Number||Stores numerical values such as order total, lifetime event count, or number of days since last visit.|
|String||Stores text values such as first/last name, address, favorite product, and page name.|
|Boolean||Stores only one of two values: 'true' and 'false'. Boolean can be used for indicating the status of a visitor action or visit.|
|Array of Numbers||Stores multiple numeric values as an array. The array may contain unique or duplicate numeric values.|
|Array of Strings||Stores multiple string values as an array. The array may contain unique or duplicate string values.|
|Array of Booleans||Stores multiple boolean (true/false) values as an array. The array may contain unique or duplicate boolean values.|
|Tally||Stores one or more key-value pairs.|
|Set of Unique Strings||Stores a collection of unique string values as a Set.|
|Date||Stores the date of a visitor event or particular visit.|
|Funnel||Tracks the status of every step in a multistep event, such as payment funnel and registration.|
|Timeline||Records all occurrences of a visitor action within a time range.|
|Badge||Assigns a visual mark or symbol to visitors who meet certain criteria or browsing behavior.|
|Visitor ID||Stores visitor's unique traits as their secondary identifier.|
This matrix shows which data types are available for each scope.
|Array of Numbers||✔|
|Array of Strings||✔|
|Array of Booleans||✔|
|Set of Unique Strings||✔||✔|
An Enrichment is the use of custom logic to transform an Attribute from a static value to a dynamic one. This can be used to create new data values or modify incoming data. Pre-built Enrichments are available for each Data Type. For example, the ability to increment or decrement a numeric value is available to Number Attributes. Read more about using Enrichments.
A Rule provides additional logic for the purpose of triggering an Enrichment.
Creating a new Rule through the Enrichments dialog box automatically applies it to the Enrichment.
This property is used to identify Attributes that contain data that should be omitted from UDH services that send data out of the system, such as 3rd party Connectors or DataAccess. For more information, refer to the Restricted Data article.
Navigate to Enrich > Attributes to view your Attributes. Filter the view with the available options in the side bar. Then click your desired Attribute to expand the details.
To add a new Attribute:
The name of an Event Attribute must match the name of the variable implemented.
For a Redshift database, column names must consist of only UTF-8 printable characters. ASCII letters in standard and delimited identifiers are case-insensitive and are folded to lower case. For additional details, please see Amazon Web Services - Names and identifiers.
To add an Enrichment:
You must save and publish your changes.
An imported Attribute is a variable that was originally created in the corresponding Tealium iQ profile. These variables are automatically detected and pulled in as Event-scoped Attributes. When you modify a Variable in Tealium iQ (and publish), the changes are instantly applied to the matching Attribute.
Imported Attributes are not editable. You must use Tealium iQ to manage them.
If the Attribute your trying to delete is currently in use by a Rule, Enrichment or an Audience, the delete action will fail. You must remove the dependent element and retry deleting.