Data Index

The Data Index is where you find a description of all Traits & Events that are stored in your Refiner environment.

What are User Traits?

You can think of Traits as a high level description of all the data that can be found in your Refiner environment. If you think about all your Refiner data as a giant spreadsheet, there would be one column for each Trait.

When are traits created?

Traits are created automatically for you whenever we receive user data for your Refiner environment.

  • When you identify a user, a trait is created for each data attribute that you include in the identifyUser call.
  • When we receive a new survey response, a trait is created for each survey question if no matching trait can be found
  • Computed traits are automatically generated when new user data is available, for example “User first seen”, “Last survey submission”, “Total survey submissions”, etc.

You can also create traits manually if needed. For example if you want start building segments before connecting an actual data source to your environment.

How are traits linked to survey responses?

All data in your Refiner account is represented by a Trait – user data that you provide, automatically computed traits, as well as survey response data provided by your users.

When we receive a survey response from a user, we’ll check for each question if a matching Trait is already present in your environment. We’ll try to find a matching Trait by looking at the Question Identifier of each question and its data type (string or number).

Once responses are stored in your Refiner environment, you’ll be able to use them in data-driven segments and exports it in the exact same way as other user data.

Supported Data Types

Refiner supports the following data types:

  • Strings – 255 characters max length)
  • Integer numbers – ranging from -2147483647 to 2147483647
  • Dates – ISO date format or Linux timestamp

Difference between User and Account Traits

The primary data object in Refiner are user profiles and their survey responses. Refiner does however also support the grouping of user profiles into “accounts”.

Account traits are typically only created when you are using our Segment integration, or when you explicitly provide and account object when identifying users with our Web-client or our API. By default, all data in your Refiner environment is linked to user records.

What are “Finite Datasets”

Finite dataset means that there is a limited and well defined number of possible values. For example, a list all countries or the activation status of a user, are both finite datasets. The opposite of a finite dataset are continuous datasets, such as arbitrary strings (e.g. “first name”) or numbers (e.g. “login count”).

When a dataset is set to “Finite”, you’ll have access to different kind of filters when creating a data-driven segment.

Refiner tries to figure out automatically if a field holds a finite or continuous dataset, based on the name of the field (e.g. “country”, “role”, …). If Refiner didn’t get it right, you can change switch a data field from finite to continuous and vice versa anytime.

User Events

User Events are created whenever you track event data with our Web-Client, Mobile SDKs, our Rest API, or one of our integrations.

Event data can be used to create Data-Driven Segments. In the list of all tracked events you can see how often an event is used in a segment. Events that are used in at least one segment can’t be deleted.

Was this helpful? Let us know with a quick a vote