Data Types

read

When you are creating a segment or configuring a flow filter using the Properties about someone option, you will notice a drop-down menu that appears after you choose a dimension for your condition. This drop-down menu relates to data type of the value you are inputting.

2017-05-24_12-21-54.png


The following data types are available to select:

  • String
  • Number
  • Date
  • Boolean
  • List

String

A string is any finite sequence of characters (i.e., letters, numerals, symbols and punctuation marks). A string is always used to represent plain text, even when the string includes numbers or is formatted like a date. You can think of String as what might appear within quotation marks in a paragraph; the content doesn't matter, but whatever is inside of the quotation marks exists as a finite sequence of characters.

You can think of string as what might appear within quotation marks in a paragraph; the content doesn't matter, but whatever is inside of the quotation marks exists as a finite sequence of characters.

Number

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. a string).

Date

A date is used for any datetime value. Unlike a number, Klaviyo will only automatically recognize a date value as a date if the date is formatted in a certain way (YYYY-MM-DD HH:MM:SS).

Boolean

The Boolean data type can only represent two values: true or false.

List

A list is any array of values, e.g.  ["Offer1", "Offer2"]. In Klaviyo, the lists are used when the goal is to collect an array of words or phrases, where each 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 metric 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 one property, Items, but have that property include a series of values (i.e. each item purchased in the single order), where each value in the array can be identified individually.

Was this article helpful?
1 out of 1 found this helpful