Custom Attributes

Custom Attributes are best for storing attributes about your users, or information about low-value actions within your application. 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 upon them like the above example for Custom Events.

We get that Custom Attributes can be confusing, so read closely and check out our LAB course on Custom Events and Attributes!

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 STRING OR REGULAR EXPRESSION
Check if the string attribute does not partially match an inputted string OR Regular Expression DOES NOT MATCH REGEX STRING OR REGULAR 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 EXISTS N/A
Check if the string attribute does not exist on a user’s profile DOES NOT EXIST 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 STRING OR REGULAR 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.

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 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 prior 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 more than X number of days ago MORE THAN NUMBER OF DAYS AGO
Check if the date attribute is less than X number of days ago LESS THAN NUMBER OF DAYS AGO
Check if the date attribute is in more than X number of days in the future IN MORE THAN __NUMBER OF DAYS IN FUTURE
Check if the date attribute is less than X number of days in the future IN LESS THAN __NUMBER OF DAYS IN FUTURE
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. Incrementing 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.

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 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

Purchases / Revenue Tracking

Using our purchase methods to record in-app purchases establishes the Life-time Value(LTV) for each individual user profile. This data is viewable within our revenue page in time-series.

Segmentation Options Dropdown Filter Input Options
Check if the total number of dollars spent is greater than an integer or decimal value GREATER THAN INTEGER or DECIMAL
Check if the total number of dollars spent is less than an integer or decimal value LESS THAN INTEGER or DECIMAL
Check if total number of dollars spent is exactly an integer or decimal value EXACTLY INTEGER or DECIMAL
Check if the purchase last occurred after X date AFTER DATE
Check if the purchase last occurred before X date BEFORE DATE
Check if the purchase last occurred more than X days ago MORE THAN DATE
Check if the purchase last occurred less than X days ago LESS THAN DATE
Check if the purchase occurred more than X (Max = 50) number of times MORE THAN in the past Y Days (Y = 1,3,7,14,21,30)
Check if the purchase occurred less than X (Max = 50) number of times LESS THAN in the past Y Days (Y = 1,3,7,14,21,30)
Check if the purchase occurred exactly X (Max = 50) number of times EXACTLY in the past Y Days (Y = 1,3,7,14,21,30)
WAS THIS PAGE HELPFUL?