Attributes

An Attribute is a set of key-value pairs made up of strings, numerics, and booleans that help you and the Sprig to know more information or data about your users as an audience or cohort. Specifically Attributes provide more context about the user in order to gain a better understanding of who they are when they come to your application. Listed below are examples of Attributes as a set of key-value pairs.

Attribute KeyAttribute Value
User LanguageSpanish, English, Hindi, Arabic, Bengali, Portuguese, Russian, Chinese
User CountryCanada, United Kingdom, India, United States, Brazil, Australia, Germany, France
Plan TypeFree, Professional, Standard, Advanced, Enterprise
Feature Cohort StagePaid Alpha, Paid Beta, Paid Production, Free Small, Free Large

Sprig supports categorical, discrete, ordinal Attributes. There can be up to 100 discrete values for any given key. In the example above on Plan Type as the Attribute key, there are 5 distinct Attribute values (Free, Professional, Standard, Advanced, and Enterprise). Attributes cannot be deleted unless the entirety of the data for a given visitor is also deleted. This means that you must be careful when considering an update to the key-value pairs of a given Attribute. As an alternative to deleting, you may consider creating a new Attribute instead of trying to update the original Attribute.

Avoid placing a data set that is not discrete. Listed below are examples of attributes that are either not discrete or are discrete but with a range of values over 100.

  • Unique IDs
  • Device IDs
  • Timestamps for unique events or interactions

Purpose of Attributes

Attributes can be used to refine the target users and also filter the response data.

FilteringAttributes, like Events, can be used in a study to target and help refine the cohort of users you wish to study. Unlike Events, Attributes cannot fire or trigger a Study; they can only Filter.
Study ResponseAttributes can also be used as filters to drill into the study response data (once responses are collected and if at least one of the Respondents had (a) value(s) set for a given Attribute when the study was delivered the responses contain the Attribute’s values)

Managing Attributes

Installation and Setup

Filtering - further target a cohort of users on a given study.

Response "More Filters" - refine or view responses to the study.

Spring UI

Read Only

Read Only

Web SDK

:white-check-mark:

:white-check-mark:

Mobile SDK

:white-check-mark:

:white-check-mark:

Integrations and Connections

Filtering - further target a cohort of users on a given study.

Response "More Filters" - refine or view responses to the study.

API

:white-check-mark:

:white-check-mark:

CSV Import

:white-check-mark:

:white-check-mark:

GTM

:white-check-mark:

:white-check-mark:

Segment

:white-check-mark:

:white-check-mark:

mParticle

:white-check-mark:

:white-check-mark:

Do you have feedback about managing Attributes? Tell us more.