Klaviyo allows you to harness the data collected about your customers to power data-driven marketing choices that will grow your brand. That being said, it's important to understand the data that's being pulled into your account. In this article, you will learn what the different data types entail.
Where Data Types Appear in Klaviyo
When creating a segment or configuring a flow filter using Properties about someone, you will notice a dropdown menu that appears after you choose a dimension for your condition. This dropdown menu relates to the data type of the value you input.
The following data types are available to select:
A text input is any finite sequence of characters (i.e., letters, numerals, symbols, and punctuation marks). It is always used to represent plain text, even when it includes numbers or is formatted like a date.
You can think of a text input as what might appear within quotation marks in a paragraph — regardless of content in the quotation marks, whatever is inside of the quotation marks exists as a finite sequence of characters. Text inputs could be a favorite color, shopping preferences, or an email address. Below is a signup form that gathers preference information that will be translated into text properties.
A number is a numeric value without a decimal. When you import numeric values into Klaviyo, we will automatically recognize the value as a number (vs. text).
Number inputs could reference someone’s age, the number of emails received, or how many times a customer has purchased from you. Below is a segment that shows customer engagement by interaction with the number of emails that have been clicked on or opened in the last month.
A date is used for any date-time value. Unlike a number, Klaviyo will only automatically recognize a date value as a date if it is formatted a certain way (i.e., YYYY-MM-DD HH:MM:SS).
Dates could reference someone’s birthday, the day they first signed up for your newsletter, or an anniversary with a partner. Below is a signup form collecting birthday information as a date.
The boolean data type can only represent two values: true or false. An example of boolean data is the property stored when someone has accepted marketing from you. Below is an example of a customer profile who consented to marketing.
A list is any array of values, e.g. ["Offer1", "Offer2"]. In Klaviyo, lists are used when the goal is to collect an array of words or phrases, where every single item in the array can be identified individually.
One common use case for this is when different tags are being collected under a single property, such as the Shopify Tags property. When Klaviyo stores a property as a list, this allows you to use the property in a segment or filter and then include as many available tags as you'd like — you have the ability to choose from any value stored as part of the list.
Another common use case is when Klaviyo captures a Placed Order metric through an integration and the data we receive along with this placed order includes an Items property. This single Items property will need to include all items purchased in the order.
To achieve this, the property is always synced and stored as an array (a list) in Klaviyo. This allows us to store the Items property while including a series of values (i.e., each item purchased in the single order), where each value in the array can be identified individually.
Additional Data Types for List Uploads
When uploading a list of profiles into Klaviyo, two additional data types appear before the import is complete. These data types are String and Consent, as shown below.
String is the same as the Text data type. When creating a segment, you can segment based on string data using the text data type.
Consent refers to whether or not the profiles you are uploading or adding properties to have actively agreed to receive marketing from your business. The acceptable values for this data type are: email, SMS, web, and push. Your value therefore detail which channel of communication your customer has opted-in to receive.
For more information on consent, please see Consent in Profiles.