Custom Attributes are best for storing attributes about your users or information about low-value actions within your website. You should keep in mind that we don’t store time-series information for Custom Attributes, so you’re not going to get any graphs based on them.
Custom Attribute Data Types
Custom Attributes are extraordinarily flexible tools that allow for great targeting. The following data types may be stored as custom attributes:
Strings (Alpha-Numeric Characters)
String attributes are useful for storing user input, such as a favorite brand, a phone number, or a last search string within your application.
| SEGMENTATION OPTIONS | DROPDOWN FILTER | INPUT OPTIONS |
|---|---|---|
| Check if the string attribute exactly matches an inputted string | EQUALS | STRING |
| Check if the string attribute partially matches an inputted string OR Regular Expression | MATCHES REGEX | STRINGORREGULAR EXPRESSION |
| Check if the string attribute does not partially match an inputted string OR Regular Expression | DOES NOT MATCH REGEX | STRINGORREGULAR EXPRESSION |
| Check if the string attribute does not match an inputted string | DOES NOT EQUAL | STRING |
| Check if the string attribute exists on a user’s profile | BLANK | N/A |
| Check if the string attribute does not exist on a user’s profile | IS NOT BLANK | N/A |
Arrays
Array attributes are good for storing related lists of information about your users. For example, storing the last 100 pieces of content a user watched within an array would allow specific interest segmentation.
| SEGMENTATION OPTIONS | DROPDOWN FILTER | INPUT OPTIONS |
|---|---|---|
| Check if the array attribute includes a value which exactly matches an inputted value | INCLUDES VALUE | STRING |
| Check if the array attribute does not include a value which exactly matches an inputted value | DOESN’T INCLUDE VALUE | STRING |
| Check if the array attribute contains a value which partially matches an inputted value OR Regular Expression | MATCHES REGEX | STRINGORREGULAR EXPRESSION |
| Check if the array attribute has any value | HAS A VALUE | N/A |
| Check if the array attribute is empty | IS EMPTY | N/A |
Dates
Date attributes are useful for storing the last time a specific action was taken, so you can offer content specific re-engagement messaging to your users.
Warning:
We automatically record the last date a custom or purchase event occurred. Therefore, it should not be recorded in duplicate via a custom date attribute.
Date filters using relative dates (e.g. more than 1 day ago, less than 2 days ago) measure 1 day as 24 hours. Any campaign that you run using these filters will include all users in 24 hour increments. For example, "last used the app more than 1 day ago" will capture all users who “last used the app more than 24 hours” from the exact time the campaign runs. The same will be true for campaigns set with longer date ranges – so five days from activation will mean the previous 120 hours.
| SEGMENTATION OPTIONS | DROPDOWN FILTER | INPUT OPTIONS |
|---|---|---|
| Check if the date attribute is before a selected date | BEFORE | CALENDAR DATE SELECTOR |
| Check if the date attribute is after a selected date | AFTER | CALENDAR DATE SELECTOR |
| Check if the date attribute is equal to a selected date | EQUAL | |
| Check if the date attribute exists on a user’s profile | EXISTS | N/A |
| Check if the date attribute does not exist on a user’s profile | DOES NOT EXIST | N/A |
Integers (Standard and Incrementing) and Decimals (Floats/Doubles)
Numeric attributes have a wide variety of use-cases. Implementing integer custom attributes are useful for storing the number of times a given action or event has occurred without counting against your data cap. Standard integers and decimals have all sorts of usages, for example: recording shoe size, waist size, number of times a user has viewed a certain product feature, or category.
Tip:
Money spent in app should not be recorded by this method. It should be recorded via our purchase methods.
| SEGMENTATION OPTIONS | DROPDOWN FILTER | INPUT OPTIONS |
|---|---|---|
| Check if the numeric attribute is more than an integer or decimal value | MORE THAN | INTEGER or DECIMAL |
| Check if the numeric attribute is less than an integer or decimal value | LESS THAN | INTEGER or DECIMAL |
| Check if the numeric attribute is exactly an integer or decimal value | EXACTLY | INTEGER or DECIMAL |
| Check if the numeric attribute does not equal to an integer or decimal value | DOES NOT EQUAL | INTEGER or DECIMAL |
| Check if the numeric attribute exists on a user’s profile | EXISTS | N/A |
| Check if the numeric attribute does not exist on a user’s profile | DOES NOT EXIST | N/A |
Booleans (True/False)
Boolean attributes are useful for storing subscription statuses, and other simple binary data about your users. The input options that we provide allow you to find users that have explicitly had a variable set to a true/false value in addition to those that don’t have any record of that attribute recorded yet.
| SEGMENTATION OPTIONS | DROPDOWN FILTER | INPUT OPTIONS |
|---|---|---|
| Check if the boolean value is | IS | TRUE, FALSE, TRUE OR NOT SET, or FALSE OR NOT SET |
| Check if the boolean value exists on a user’s profile | EXISTS | N/A |
| Check if the boolean value does not exist on a user’s profile | DOES NOT EXIST | N/A |
Comments
0 comments
Please sign in to leave a comment.