Attributes

Overview

Attributes allow you to define characteristics that represent your user's or account's properties. Attributes can be used in the segment editor filter and target specific audiences. They allow you to:
  • Determine merge strategy
  • Define attribute mapping
  • Update names and descriptions

Creating an Attribute

Conceptually, user attributes are collection properties captured in any given source. For a collection field to be labeled as an "Attribute" you need to assign this state in the Schema editor.
Go to "Segmentation" tab and locate the "Attributes" product. Once clicked on the product, click on "Add new attribute" button.
Add a descriptive name for the to be created attribute.
Choose the attribute type: either "Users" or "Accounts".
Choose the attribute creation model:
  • Manual - for manual attribute creation
  • ML model - upload a Machine Learning model

Attribute mapping

Select the attribute that will be linked to this data item. Only collection fields that were checked in the schema editor as "Attributes" will appear in the list.
  • Merge strategy - will allow you define rules how attributes should be updated once user is identified (his profiles are merged) or new data is pushed to the attribute (for example user attribute location changed from United States to United Kingdom).
    • Most frequently used value - the value of the property that was used the most times
    • First stored value - if both user profiles have a value, the oldest value (with the oldest timestamp) is used for the attribute
    • Most recent value - keeps the value that was the last set
    • Keep all - the values from all attribute values are kept
  • Display - by checking this option, the profile property becomes available as a filter to create segments
  • Description - you can enter more details about the user attribute and what user information it carries.
After clicking the "Create attribute" button the event will be created.

Assigning user attributes

In the "Sources" schema editor, select fields that will be used as account attributes - these data objects should have information about the user (e.g., age, location, gender and etc.). If selected, these collection fields will be available to be used in the segment editor - to filter users by their attributes.