Attributes allow you to define characteristics representing your user's or account's properties. They can be used in the segments, journeys, experiments, scores, playbooks as defining criteria or as personalization tags on messaging templates or playbook messages.

Logic behind attributes

Attributes are based on data items that you import to Intempt via sources. The main difference between a property "email" in the source collection vs. an attribute that is created based on the property is that the attribute is "above" source level - it is a meta object that unifies user's or account's data.

The main reason why we created attribute logic was to avoid data siloes when using multiple data sources. Imagine this example - you have the same email property from a Shopify source and from a web source. Users might have different emails tracked from these sources. Which property should you prioritize?

This is the problem we are solving with attribute mapping functionality. With Intempt attributes, you can create a single attribute that has a logic to unify values across multiple similar properties (like email fields for Shopify and web source) so you can have a unified way to use user and account properties for all targeting or personalization cases.

Accessing attributes

The attributes list page can be accessed via the Audiences section. Here you can:

  • Access the list of created attributes
  • Search for the created attributes
  • Filter the attributes
  • Create new attributes
  • Edit name
  • Delete

How to create an Attribute

Go to Attributes and click "Create attribute".

Choose the attribute type:

  • Users (if you are creating user-level property)
  • Accounts (if you are creating company-level property)

Merge strategy

You can define rules on how attributes should be updated once the 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

The main idea of the merge strategy is to allow you to define a logic of which property should be prioritized when a new data item is received.

Most frequently used value. Consider this example for email address - user submitted [email protected] 6 times and [email protected] 2 times. Intempt will use the email address that was used most frequently [email protected] (user might use multiple emails to sign up).

First stored value. Important in cases when you want to track the user's first option, relevant in cases when you track the user's original location.

Most recent value. We recommend using this option most frequently as it represents the most up-to-date user's or account information. Any data item that was submitted most recently will be used as an attribute value for this merge strategy.

Attribute mapping

Attribute mapping allows you to select one or more properties across multiple data sources and use it to create a unified record of a user or account trait. Imagine a situation when you have different user names in your iOS app, JS source, and Shopify. Which one to prioritize? Select the properties via attribute mapping and we will create a unified attribute record based on your chosen merge strategy.