This article documents the standard filter options provided by Customer Data Platform (CDP) out-of-the-box. For any filter specifically configured or customized for your tenant, please refer to your tenant-specific documentation.
Rules types and comparisons
Audience filter rules and refinements help you to specifically define and segment out your audience. The filter rules are built to be human readable, yet flexible in what boundary conditions can be input to define the filter comparison. Depending upon the data type of the rule, there are some variations in what values you can enter and how it is displayed in the Actions interface.
Below is the list of rule data types, what comparisons (i.e. operators) are possible per data type, and an example of the rule in use. CDP’s Actions Campaigns are executed in Impala, so the examples may reference Impala SQL functions.
Activity-base rules
For activity-based rules the comparisons you can use vary based on the rule. They typically use numerical values, and you can choose whether those values represent days or hours. For example, “Browsed a product in timeframe [60] [Days]”.
Text-based rules
These rules apply to the String data type.
Operator | Description | Example |
---|---|---|
Equal to | Returns customer records where the source text exactly matches the input text. This operator is case sensitive. | “State equal to [CA]” is translated to customersummary.State = ‘CA’ |
Not equal to | Returns customer records where the source text does not exactly match the input text. This operator is case sensitive. | “State not equal to [CA]” is translated to customersummary.State != ‘CA’ |
Contains | Returns customer records where the source text contains the input text. This operator is not case sensitive. | “State contains [CA]” is translated to instr(lower(customersummary.State),’ca’) != 0 |
Does not contain | Returns customer records where the source text does not contain the input text. This operator is not case sensitive. | “State does not contain [CA]” is translated to instr(lower(customersummary.State),’ca’) = 0 |
Is empty | Returns records where the source text is NULL or is an empty string. | “State is empty” is translated to customersummary.State IS NULL OR customersummary.State = ‘’ |
Is not empty | Returns records where the source text is not NULL and is not an empty string. | “State is not empty” is translated to customersummary.State IS NOT NULL AND customersummary.State != ‘’ |
In | Returns records where the source text exactly matches one of the input texts. This operator is case sensitive. | “State in [CA, MA]” is translated to customersummary.State IN (‘CA’,’MA’) |
Not in | Returns records where the source text does not exactly match any of the input texts. This operator is case sensitive. | “State not in [CA, MA]” is translated to customersummary.State NOT IN (‘CA’,’MA’) |
Number-based rules
These rules apply to Integer and Decimal data types.
Operator | Description | Example |
---|---|---|
Equal to | Returns customer records where the source number exactly matches the input number. | “Total Revenue equal to [100]” is translated to customersummary.TotalRevenue = 100 |
Not Equal to | Returns customer records where the source number does not exactly match the input number. | “Total Revenue not equal to [100]” is translated to customersummary.TotalRevenue != 100 |
Greater than | Returns customer records where the source number is greater than, but not equal to, the input number. | “Total Revenue greater than [100]” is translated to customersummary.TotalRevenue > 100 |
Greater than equal to | Returns customer records where the source number is greater than or equal to the input number. | “Total Revenue greater than equal to [100]” is translated to customersummary.TotalRevenue >= 100 |
Less than | Returns customer records where the source number is less than, but not equal to, the input number. | “Total Revenue less than [100]” is translated to customersummary.TotalRevenue < 100 |
Less than equal to | Returns customer records where the source number is less than or equal to the input number. | “Total Revenue less than equal to [100]” is translated to customersummary.TotalRevenue <= 100 |
Between | Returns customer records where the source number is greater than or equal to the input floor but less than the input ceiling. For numbers, the lower bound is inclusive and the upper bound is exclusive. | “Total Revenue between [100] and [200]” is translated to customersummary.TotalRevenue >= 100 AND customersummary.TotalRevenue < 200 |
In | Returns customer records where the source number exactly matches one of the input numbers. | “Total Revenue in [100, 200]” is translated to customersummary.TotalRevenue IN (100,200) |
Date-based rules
These rules apply to Date and Datetime/Timestamp data types.
Due to the compatibilities of some underlying technologies, within CDP dates and datetimes are stored as unix epoch timestamps. For example, March 4th, 2019 in Sunnyvale, CA is bounded by 1551686400000 (March 4, 2019 12:00:00 AM GMT-08:00) and 1551772799999 (Monday, March 4, 2019 11:59:59.999 PM GMT-08:00). Perhaps not relevant to this context, but the wide use of unix epoch timestamps is the cause of the 2038 problem. Do not worry we use a 64-bit architecture that should last us another 292 billion years.
When date operators have a lower and upper bound, generally both the lower and upper bounds are inclusive.
Operator | Description | Example |
---|---|---|
Equal to | Returns customer records where the source date exactly matches the input date. | “Last Transaction Date equal to [3/4/2019]” PST is translated to customersummary.LastTransactionDate >= March 4, 2019 12:00:00 AM PST AND customersummary1.LastTransactionDate <= March 4, 2019 11:59:59.999 PM PST is translated to customersummary.LastTransactionDate >= 1551686400000 AND customersummary1.LastTransactionDate <= 1551772799999 |
After | Returns customer records where the source date is after the input date. | “Last Transaction Date after [3/4/2019]” PST is translated to customersummary.LastTransactionDate > March 4, 2019 11:59:59.999 PM PST is translated to customersummary.LastTransactionDate > 1551772799999 |
Before | Returns customer records where the source date is before the input date. | “Last Transaction Date before [3/4/2019]” PST is translated to customersummary.LastTransactionDate < March 4, 2019 12:00:00 AM PST is translated to customersummary.LastTransactionDate < 1551686400000 |
In the last | Returns customer records where the source date is within the specified [Weeks/Days/Hours/Minutes] of the current date and time. | “Last Transaction Date in the last [3] [Days]” is translated to customersummary.LastTransactionDate > (currentDateTimeInMilliseconds - (3d * 24h/d * 60m/h * 60s/m * 1000ms/s)) is translated to customersummary.LastTransactionDate > (unix_timestamp()*1000 - 259200000) |
At least… ago | Returns customer records where the source date is at least [Weeks/Days/ Hours/Minutes] before the current time. | “Last Transaction Date at least [3] [Hours] ago” is translated to customersummary.LastTransactionDate < (currentDateTimeInMilliseconds - (3h * 60m/h * 60s/m * 1000ms/s)) is translated to customersummary.LastTransactionDate < (unix_timestamp()*1000 - 10800000) |
Between | Returns customer records where the source date is in between the specified dates. For dates, both the lower bound (i.e. date floor) and upper bound (i.e. date ceiling) are inclusive. | “Last Transaction Date between [2/4/2019] and [3/4/2019]” PST is translated to customersummary.LastTransactionDate >= February 4, 2019 12:00:00 AM PST AND customersummary.LastTransactionDate < March 4, 2019 11:59:59.999 PM PST is translated to customersummary.LastTransactionDate >= 1549267200000 AND customersummary.LastTransactionDate < 1551772799999 |
In the range of… ago | Returns customer records where the source date is within the specified lower bound and upper bound of [Weeks/Days/Hours/Minutes] before the current time. | “Last Transaction Date in the range of [2] and [10] [Weeks] ago” is translated to customersummary.LastTransactionDate >= (currentDateTimeInMilliseconds - (10w * 7d/w * 24h/d * 60m/h * 60s/m * 1000ms/s)) AND customersummary.LastTransactionDate < (currentDateTimeInMilliseconds - (2w * 7d/w * 24h/d * 60m/h * 60s/m * 1000ms/s)) is translated to customersummary.LastTransactionDate >= (unix_timestamp()*1000 - 6048000000) AND customersummary.LastTransactionDate < (unix_timestamp()*1000 - 1209600000) |
In the next | Returns customer records where the source date is is within the input [Weeks/Days/Hours/Minutes] after the current time. | “Credit Card Expiration Date in the next [3] Weeks” is translated to customersummary.c_creditCardExpirationDate > currentDateTimeInMilliseconds AND customersummary.c_creditCardExpirationDate <= (currentDateTimeInMilliseconds + (3w * 7d/w * 24h/d * 60m/h * 60s/m * 1000ms/s)) is translated to customersummary.c_creditCardExpirationDate > (unix_timestamp()*1000) AND customersummary.c_creditCardExpirationDate <= (unix_timestamp()*1000 + 1814400000) |
In the future range of | Returns customer records where the source date is within the specified lower bound and upper bound of [Weeks/Days/Hours/Minutes] after the current time. | “Credit Card Expiration Date in the future range of [2] and [10] [Weeks]” is translated to customersummary.c_creditCardExpirationDate >= (currentDateTimeInMilliseconds + (2w * 7d/w * 24h/d * 60m/h * 60s/m * 1000ms/s)) AND customersummary.c_creditCardExpirationDate <= (currentDateTimeInMilliseconds + (10w * 7d/w * 24h/d * 60m/h * 60s/m * 1000ms/s)) is translated to customersummary.c_creditCardExpirationDate >= (unix_timestamp()*1000 + 1209600000) AND customersummary.c_creditCardExpirationDate <= (unix_timestamp()*1000 + 6048000000) |
Entering values in the rules/refinements
Depending on the rule type and the comparator you selected, you can enter different types of values in the rule/refinement. For instance, you will get a simple text box for numerical rules, but you will get a date picker (screenshot below) for any date filter that requires entering actual dates (and not number of days) :
Lookups
For most of the text-based rules, CDP provides a “lookup” functionality. This
functionality is available for the in
and not in
operators.
To use this feature:
Sign in to your CDP user interface and navigate to Actions > Campaigns.
In Audience, select a text-based rule that supports lookup. For example, Closest Store Name.
Use
in
ornot in
as the operator.Hover your cursor over the icon, as highlighted in the following screenshot.
Click the Select multiple values at once icon.
The system displays a drop-down list of values.
Note
If the lookup feature is not available for the rule, you can specify the values manually.
Select all the applicable values and click OK.
Specify the other details and save your campaign.
If you don’t see a lookup for a text-based rule you are using and you need one, contact your CDP team.
Entering multiple values
Text-based rules and the “in” comparator allow you to enter multiple values to be searched for. The way this works is by selecting a value in the lookup, then selecting another (or typing a value, then type “Enter”, then enter another value, etc…) :
If you already have the list of value somewhere else (Excel file, text file with a list of values), you can also click the small “stack” button next to the box where you enter values, and it will open a pop-up window allowing you to copy-paste your values (reach values separated by a new line) :
Rules
Here are the standard rules that come out-of-the-box with every CDP implementation.
Note
If not specified, rules do not have refinements.
All transaction-based calculations are made considering only “Shipped/ Returned” transactions by default.
Folder | Name | Description | Example values |
---|---|---|---|
Buying Stats | Average Annual Transactions | The number of transactions your customers made per year, on average,
throughout their lifetime. If they are non-buyers, the customers
have a value of | - |
Buying Stats | Average Annual Transactions - Group | The number of transactions your customers made per year, on average, throughout their lifetime. For easier use, the transactions are grouped into buckets. | - |
Buying Stats | Average Discount Rate | The average rate of discount the customers have used in their lifetime. | “0%”, “10-15%”, “>30%”, “Non Buyer” |
Buying Stats | Average Order Value - Group | The average value of the customers’ transactions in their lifetime. | “25-50”, “200-300”, “300-400”, “Non Buyer” |
Buying Stats | Channel Mix - 13-24 Months | The sales channels that your customers purchased between 13 and 24 months ago. | “Unidentified”, “Other Channel Buyer”, “Non Buyer” |
Buying Stats | Channel Mix - Last 12 Months | The sales channels that your customers purchased in the last 12 months. | “Unidentified”, “Other Channel Buyer”, “Non Buyer” |
Buying Stats | Channel Mix - Lifetime | The sales channels that your customers purchased in their lifetime. | “Unidentified”, “Other Channel Buyer”, “Non Buyer” |
Buying Stats | Discount - Lifetime | The total discount amount used by your customers in their entire lifetime. | - |
Buying Stats | First Transaction Date | The date of your customers’ first transaction. | - |
Buying Stats | First Transaction Date - Digital | The date of your customers’ first transaction in the Digital sales channel. | - |
Buying Stats | First Transaction Date - Physical | The date of your customers’ first transaction in the Physical sales channel. | - |
Buying Stats | First Transaction Revenue | The revenue of your customers’ first transaction. | - |
Buying Stats | First Transaction Revenue Group | Same as First Transaction Revenue, but grouped into buckets for ease of use. | “50-75”, “75-100”, “100-150”, “200-300” |
Buying Stats | First Transaction Sales Channel | The transaction channel in which your customers made their first purchase. The default value is “Unknown”. | - |
Buying Stats | Last Transaction Date | The date of your customers’ last transaction. | - |
Buying Stats | Last Transaction Date - Digital | The date of your customers’ last transaction in the Digital sales channel. | - |
Buying Stats | Last Transaction Date - Physical | The date of your customers’ last transaction in the Physical sales channel. | - |
Buying Stats | Last Transaction Interval | The interval, in days, between your customers’ last transaction and the previous one. | - |
Buying Stats | Last Transaction Interval Group | Same as Last Transaction Interval, but grouped into buckets for ease of use. | “One Time Buyer”, “3-6 Months”, “7-12 Months”, “Non Buyer” |
Buying Stats | Last Transaction Sales Channel | The transaction channel in which your customers made their last purchase. The default value is “Unknown”. | - |
Buying Stats | Months Since First Transaction - Group | The number of months since your customers’ first transaction. | “7 Months”, “8 Months”, “24+ Months” |
Buying Stats | Months Since Last Transaction | The number of months since your customers’ last transaction. | “7 to 12 Months”, “13-24 Months”, “More than 24 Months”, “Non Buyer” |
Buying Stats | Months Since Last Transaction - Group | Same as Months Since Last Transaction, but grouped into buckets for ease of use. | “7 to 12 Months”, “13-24 Months”, “More than 24 Months”, “Non Buyer” |
Buying Stats | Product Category Count | The number of categories your customers purchased from you in their lifetime. | - |
Buying Stats | Product Category Count - Group | Same as Product Category Count, but grouped into buckets for ease of use. | - |
Buying Stats | Product Count | The number of distinct products your customers purchased in their lifetime. | - |
Buying Stats | Product Count - Group | Same as Product Count, but grouped into buckets for ease of use. | - |
Buying Stats | Revenue - 13-24 Months | The total amount of revenue generated by your customers between 13 and 24 months ago (ie “2 years ago”). | - |
Buying Stats | Revenue - 13-24 Months - Group | Same as Revenue - 13-24 Months, but grouped in buckets for ease of use. | “0-100”, “200-300”, “300-400”, “400-500” |
Buying Stats | Revenue - Last 12 Months | The total amount of revenue generated by your customers in the last 12 months (ie “last year”). | - |
Buying Stats | Revenue - Last 12 Months - Group | Same as Revenue - Last 12 Months, but grouped in buckets for ease of use. | “0-100”, “200-300”, “300-400”, “400-500” |
Buying Stats | Revenue - Lifetime | The total revenue generated by your customers’ transactions in their lifetime. | - |
Buying Stats | Revenue - Lifetime - Group | Same as Revenue - Lifetime, but grouped in buckets for ease of use. | - |
Buying Stats | Revenue Decile - 13-24 Months | The total amount of revenue generated by your customers between 13 and 24 months ago (i.e. “2 years ago”), grouped by deciles, with decile 1 being the biggest spenders and decile 10 being the lowest spenders. | “1”, “2”, “3”, “4” |
Buying Stats | Revenue Decile - Last 12 Months | The total amount of revenue generated by your customers in the last 12 months (i.e. “last year”), grouped by deciles, with decile 1 being the biggest spenders and decile 10 being the lowest spenders. | “1”, “2”, “3”, “4” |
Buying Stats | Revenue Segment - 13-24 Months | An easier way to use “Revenue decile”:
| “1 - High Value”, “2 - Medium Value”, “3 - Low Value”, “Non Buyer” |
Buying Stats | Revenue Segment - Last 12 Months | An easier way to use “Revenue decile”:
| “1 - High Value”, “2 - Medium Value”, “3 - Low Value”, “Non Buyer” |
Buying Stats | Revenue Trend Segment | A segmentation representing the progression of revenue for your customers between 13-24 months ago and the last 12 months. It characterizes whether they spent less (“Downward”), the same (“Stable”), or more (“Upward”) in the last 12 months than in the 13-24 months ago period. If a customer was acquired in the last 12 months, then she gets marked as “New Buyer” instead. “Reactivated” customers are buyers who made a purchase in the last 12 months, did not make a purchase in the previous 13-24 months, but did make a purchase before 24 months ago. “2 Period Inactive” customers are buyers who did not make a purchase in the last 24 months but made a purchase before 24 months ago. “Lapsed”customers are buyers who made a purchase in the last 13-24 months but not make a transaction in the last 12 months. | “Stable”, “Upward”, “Downward”, “Non Buyer”, “New Buyer”, “Reactivated”, “2 Period Inactive”, “Lapsed” |
Buying Stats | Sales Channel Count | The total number of organizations (i.e. transaction channels) your customers have purchased from in their lifetime. | - |
Buying Stats | Second to Last Transaction Date | The date of your customers’ penultimate (second to last) transaction. | - |
Buying Stats | Transaction Count - 13-24 Months | The total number of transactions your customers made between 13 and 24 months ago (i.e. “2 years ago”). | - |
Buying Stats | Transaction Count - 13-24 Months - Group | Same as Transaction Count - 13-24 Months, but grouped in buckets for ease of use. | - |
Buying Stats | Transaction Count - Last 12 Months | The total number of transactions your customers made in the last 12 months (i.e. “last year”). | - |
Buying Stats | Transaction Count - Last 12 Months - Group | Same as Transaction Count - Last 12 Months, but grouped in buckets for ease of use. | - |
Buying Stats | Transaction Count - Lifetime | The total number of transactions your customers made in their lifetime. | - |
Buying Stats | Transaction Count - Lifetime - Group | Same as Transaction Count - Lifetime, but grouped in buckets for ease of use. | - |
Buying Stats | Transaction Count with Discount | The number of transactions with a discount amount greater than $0, across your customers’ lifetime. | - |
Campaign Activity | Were included in an CDP legacy Campaign | Filter out individuals who were previously included in an CDP legacy campaign. This filter references data stored in CampaignHistory. | - |
Campaign Activity | Were included in an CDP legacy Campaign and variant | Filter out individuals who were previously included in an CDP legacy campaign and variant. This filter references data stored in CampaignHistory. | - |
Coupon History | Received a coupon | Filter out individuals who received a coupon. | - |
Customer Attributes | Address Type - Residential or Business | A flag to mark whether the address is a business or residential address. Parcel delivery to residential addresses is more expensive than to business addresses. You can use the return value of this function to filter out one type of address or the other, or determine the best carrier for the delivery. (United States Only)
| “R”, “B”, “U” |
Customer Attributes | Address Certified | A flag to mark whether the address has been certified by the CDP Data Quality Engine (this is the USPS CASS certification) :
| “True”, “False”, “Unknown” |
Customer Attributes | DPV Confirmed | This is the DPV Confirmation results that we get from USPS for US addresses. The new filter is called “DPV Confirmed”, and can take the values “Y” (when the address is DPV confirmed) and “N” (when the address is not certified). | “Y”, “N” |
Customer Attributes | Age | The age of the customers. This is coming from your standard customer feed. | - |
Customer Attributes | Behavior based cluster | The behavior-based cluster to which the customers belong. This is part of the machine-learning models provided by CDP. The default value is “Unknown”. | “Discount shoppers”, “Core buyers”, “High-value customers” |
Customer Attributes | Likelihood to buy | The likelihood to buy of the customer, in deciles (decile 1 is the highest likelihood to buy, decile 10 is the lowest). This is part of the machine-learning models provided by CDP. | “1 - High”, “2 - Medium” |
Customer Attributes | Birth month | The birth month of the customers. This is coming from your standard customer feed. | “1”, “12”, “8” |
Customer Attributes | Birth year | The birth year of the customers. This is coming from your standard customer feed. | “1988”, “1989”, “1974” |
Customer Attributes | City | The city in which the customers live. This is coming from your standard customer feed. The default value is “Unknown”. | “Huntsville”, “Omaha”, “St Simons Is” |
Customer Attributes | Closest store | The closest store for your customers. The default value is “Unknown”. | “Inkanta Hacienda Santa Barbara”, “Hakata Hankyu”, “Maison Mode Chengdu” , “DFS” |
Customer Attributes | Country | The country in which your customers live. This is coming from your standard customer feed. The default value is “Unknown”. | “USA”, “Canada”, “France” |
Customer Attributes | Distance to closest store | The distance, in miles, between your customers and the store closest to where they live. This filter can work only for US, Canada and UK addresses (for both stores and customers). | “23.5”, “40.3”, “5” |
Customer Attributes | Distance to closest store - Group | Same as Distance to closest store, but grouped into buckets for ease of use. The default value is “Unknown”. This filter can work only for US, Canada and UK addresses (for both stores and customers). | “20-30”, “30-40”, “40-50”, “50+” |
Customer Attributes | Distance to a store | Select any customer living within [N] miles of store [ABC], e.g. : select all customers with distance to store [San Francisco store] is less than [20] miles. This can be used to send them an email about an event going on in a specific store. This has a few limitations for obvious reasons : we support distances of up to 40 miles (greater distances are considered useless by most retailers, since not a lot of people would make such a long trip), and we compute the distance to the 20 closest stores for each customers, so if there are more than 20 stores within a 40 miles radius around a given customer, we will only compute the distance to the closest 20. This filter can work only for US, Canada and UK addresses (for both stores and customers) | “San Francisco store” and “20” |
Customer Attributes | Email domain | The domain of your customers’ email address. The default value is “Unknown”. | “gmail.com”, “aol.com”, “yahoo.com” |
Customer Attributes | Email Status | The validity of the email address of your customers :
| “V”, “X”, “U” |
Customer Attributes | Gender | Your customers’ gender, as provided by your standard customer feed or as deduced by the CDP Data Quality Engine. The default value is “Unknown”. | “Female”, “Male”, “Unknown” |
Customer Attributes | Customer Status | A flag to distinguish customers that are buyers from the non-buyers. Customers who have ever made a purchase are considered buyers. | “Buyer”, “NonBuyer” |
Customer Attributes | Propensity to buy | Your customers’ propensity to buy in the next 30 days, as computed by CDP’s propensity to buy predictive model. This classifies Buyers into deciles, with Decile 1 being the most likely to buy and Decile 10 being the less likely to buy. | (Not available yet) “1 - High”, “2 - Medium”, “9 - Low”, “Non-Buyers” |
Customer Attributes | Propensity to convert | Your customers’ propensity to convert in the next 30 days, as computed by CDP’s propensity to convert predictive model. This classifies Non-Buyers into deciles, with Decile 1 being the most likely to convert and Decile 10 being the less likely to convert. | (Not available yet) “1 - High”, “2 - Medium”, “9 - Low”, “Non-Buyers” |
Customer Attributes | Propensity to engage | Your customers’ propensity to open/click an email campaign in the next 30 days, as computed by CDP’s propensity to engage predictive model. This classifies Email recipients into deciles, with Decile 1 being the most likely to open/click and Decile 10 being the less likely to open/ click. | (Not available yet) “1 - High”, “2 - Medium”, “9 - Low”, “Non-Buyers” |
Customer Attributes | State | The state in which your customers live. The default value is “Unknown”. | “MI”, “AL”, “GA” |
Customer Attributes | Zipcode | The zipcode in which your customers live. The default value is “Unknown”. | “17921”, “03773”, “75001” |
Customer Attributes | NCOADateUpdate | This is the date at which the record last went through NCOA processing. This is currently in a UNIX epoch format (e.g. “1507060487001”), but we will soon release a “human-readable” translation (e.g. YYYYMMDD format) of that filter. | “1507060487001”, “in the last 3 days” |
Customer Attributes | MoveType | This is the type of move that was registered within the USPS NCOA database. The possible values are : I for Individual Match, F for Family Match, B for Business Name Match. | “I”, “F”, “B” |
Customer Attributes | MoveDate | This is the date at which the move was registered with USPS in the NCOA database. This is in the format “YYYYMM”, e.g. “201401” is a move that was registered on January 2014 (the actual move could have happened earlier or later, the NCOA database cannot provide that information). | “201401” |
Customer Preferences | Is Identified Buyer | A flag to mark the customers that have been identified in the system (with an email address, or similar contact information). | “Identified”, “Not Identified” |
Customer Preferences | Call campaigns opt-out | This will replace the “Preferences” filter in the future. This filter allows you to select customers that are opted-in/opted-out of your Call campaigns.
| “Y”, “N”, “U” |
Customer Preferences | Direct mail campaigns opt-out | This will replace the “Preferences” filter in the future. This filter allows you to select customers that are opted-in/opted-out of your Direct Mail campaigns.
| “Y”, “N”, “U” |
Customer Preferences | Email campaigns opt-out | This will replace the “Preferences” filter in the future. This filter allows you to select customers that are opted-in/opted-out of your email campaigns.
| “Y”, “N”, “U” |
Customer Preferences | Primary brand | The brand that your customers purchased the most in their entire lifetime. The default value is “Unknown”. | “The North Face”, “Patagonia”, “Dakine” |
Customer Preferences | Primary device type | The device that your customers used the most for their purchases in their lifetime. The default value is “Unknown”. | “COMPUTER”, “MOBILE”, “Unknown” |
Customer Preferences | Primary organization | The organization through which your customers made most of their purchases in their lifetime. The default value is “Unknown”. | “Internet”, “Inkanta Hacienda Santa Barbara”, “Hakata Hankyu”, “Maison Mode Chengdu”, “DFS” |
Customer Preferences | Primary store | The store through which your customers made most of their purchases in their lifetime. The default value is “Unknown”. | “Inkanta Hacienda Santa Barbara”, “Hakata Hankyu”, “Maison Mode Chengdu” , “DFS” |
Email Activity | Date of last email clicked | The date of the customers last click on one of your email campaigns. | - |
Email Activity | Date of last email opened | The date at which the customers last opened one of your email campaigns. | - |
Email Activity | Date of last email sent | The date of the last email you sent to your customers. | - |
Email Activity | Email click count between 31 and 60 days ago | The number of clicks on email campaigns’ links between 31 and 60 days ago (ie “2 months ago”) | - |
Email Activity | Email click count between 31-60 days ago - group | The same concept, but grouped into buckets for ease of use. | “1”, “2”, “3”, “4”, “10”, “10+” |
Email Activity | Email click count in the last 30 days | The number of clicks on email campaigns’ links in the last 30 days (ie “last month”). | - |
Email Activity | Email click count in the last 30 days - group | The same concept, but grouped into buckets for ease of use. | “1”, “2”, “3”, “4”, “10”, “10+” |
Email Activity | Email open count between 31 and 60 days ago | The number of emails opened by your customers between 31 and 60 days ago (ie “2 months ago”). | - |
Email Activity | Email open count between 31-60 days ago - group | The same concept, but grouped into buckets for ease of use. | “1”, “2”, “3”, “4”, “10”, “10+” |
Email Activity | Email open count in the last 30 days | The number of emails opened by your customers in the last 30 days (ie “last month”). | - |
Email Activity | Email open count in the last 30 days - group | The same concept, but grouped into buckets for ease of use. | “1”, “2”, “3”, “4”, “10”, “10+” |
Email Activity | Emails sent between 31 and 60 days ago | The number of emails sent to your customers between 31 and 60 days ago (ie “2 months ago”). | - |
Email Activity | Emails sent between 31 and 60 days ago - group | The same concept, but grouped into buckets for ease of use. | “1”, “2”, “3”, “4”, “10”, “10+” |
Email Activity | Emails sent in the last 30 days | The number of emails sent to your customers in the last 30 days (ie “last month”). | - |
Email Activity | Emails sent in the last 30 days - group | The same concept, but grouped into buckets for ease of use. | - |
Email Activity | Performed an event with message | Select customers who received/opened/clicked/other event on a campaign with a message (all email campaigns events are supported provided that they tie to a message, and it also applies to any custom event type configured for you if that event ties to a marketing message). E.g. : you can select customers who “performed an event [emailOpen] where message name is [Abandoned Cart]”, but you cannot select customers who “performed an event [emailUnsubscribe]” because the emailUnsubscribe event generally doesn’t tie to a specific message (especially in the case of people unsubscribing from a preference center for instance). The event type can be specified by using event type values (listed on the right). Note that no web events are available there because they are not tied to marketing campaigns. You can then select the timeframe in which this event should have happened, and you can refine further by customer attributes/summaries, or by the campaign’s message name and/or subject. |
|
Email Activity | Performed an event in a time period | Select customers who performed any event in the timeframe of your choosing. The event can be specified by using event type values. The standard event type values are listed in the column on the right. You can refine this filter further, in particular by :
|
|
Email Activity | Performed a number of events in a timeframe | Same as Performed an event in a time period, but you can select the number of times the selected event type should have happened within the selected timeframe. This filter can be refined as well. | Performed the event “emailOpen” greater than 3 times in the last 30 days |
Household | Belongs to a household | This filter is a bit special : it enables you to select all customers that belong to a household that fulfills certain conditions. Those conditions are defined by you, using refinements on that filter (this filter doesn’t have any primary filtering value : it basically selects every customers unless you add refinements to filter on the household attributes, e.g. AOV of the entire household, Lifetime value of the entire household, etc…) | Belongs to a household where the (household) AOV is greater than “$500” |
Purchase Activity | Made a transaction | Selects customers who made a transaction in a specific timeframe. You can refine this rule further by adding refinements. | Made a transaction after 08/01/15 where Average Order Value (AOV) lower than $50 |
Purchase Activity | Made a number of transactions in a timeframe | Same as Made a transaction, but you can select the number of transactions the customer should have made in the selected timeframe. This filter can be refined as well. | Made greater than 5 transactions in the last 30 days. |
Purchase Activity | Placed first order | Selects customers who made their first transaction in a specific timeframe. You can refine this rule further by adding refinements. | Placed first order in the range of 7 to 14 days ago where Likelihood To Buy equal to “2 - Medium” |
Purchase Activity | Placed last order | Selects customers who made their last transaction in a specific timeframe. You can refine this rule further by adding refinements. | Made last transaction in the last 60 days where Transaction Revenue greater than $200 |
Purchase Activity | Purchased a product | Selects customers who purchased a product in a specific timeframe. You can refine this rule further by adding refinements. | Purchased a product before 08/01/16 where Organization Name equal to “San Francisco Store” and Transaction Item Revenue greater than $100 |
Purchase Activity | Purchase a number of products in a category | Same as Purchased a product, but you can select the number of products that the customer should have purchased in the selected timeframe. This filter can be refined as well. | Purchased 5 products in the last 30 days. |
Purchase Activity | Customers who spent certain amount in a timeframe | Select customers based on the amount of revenue they spent within a specific timeframe e.g. “spent more than $300 in the last 30 days…”. This filter can be refined further. | Spent more than $300 in the last 30 days where subtype in Shipped, Returned |
Purchase Activity | Customers who spent certain amount in a transaction | Select customers based on the amount of revenue they spent within a single transaction, in a specific timeframe e.g. “spent more than $500 in a single transaction in the last 30 days…”. This filter can be refined further. | Spent more than $500 in a single transaction in the last 30 days where Organization Type is Physical |
Web Activity | Browsed a product | Selects customers who browsed a product in a specific timeframe. You can refine this rule further by adding refinements. In particular, you can refine by :
| Browsed a product in the last 10 days where Product Name equal to “ProductABC” and Category Name equal to “CategoryXYZ” |
Web Activity | Customers who abandoned their cart | Selects customers who abandoned a cart in a specific timeframe. You can refine this rule further by adding refinements. In particular :
We recommend that when you use this filter that you also exclude individuals who performed a checkout event in the same time period. This is required when transactions are not delivered to CDP in real time, but experience a 24 hour lag. | Abandoned their cart 2 days ago and Likelihood to Buy equal to “1 - High” |
Web Activity | Date of first web visit | The date of the customers’ first visit to your website. | - |
Web Activity | Date of last web visit | The date of the customers’ last visit to your website. | - |
Web Activity | Days since first web visit group | Same as Date of first web visit, but grouped into buckets for ease of use. | “0”, “8-15”, “16-30”, “31-60” |
Web Activity | Days since last web visit group | Same as Date of last web visit, but grouped into buckets for ease of use. | “0”, “8-15”, “16-30”, “31-60” |
Web Activity | Web visit count between 31 and 60 days ago | The number of website visits between 31 and 60 days ago (ie “2 months ago”). | - |
Web Activity | Web visit count between 31 and 60 days ago - group | Same as Web visit count between 31 and 60 days ago, but grouped into buckets for ease of use. | “1-5”, “5-10”, “10+” |
Web Activity | Web visit count in the last 30 days | The number of website visits in the last 30 days (ie “last month”). | - |
Web Activity | Web visit count in the last 30 days - group | Same as Web visit count in the last 30 days, but grouped into buckets for ease of use. | “1-5”, “5-10”, “10+” |
Refinements
Refinements contain all the attributes (standard & custom) related to the entities that a rule is tied to. For instance, the rule “Purchased a product” is tied to a customer, a product (and therefore a product category), a transaction and a transaction item (and therefore an organization). Refinements do not contain customer activity elements given that they already filter on top of such elements.
The list of filters that support refinements can be found in the preceding section, but here is a quick summary:
Folder | Name | Objects whose attributes you can use to refine | Example |
---|---|---|---|
Purchase Activity | Made a transaction | Customer, Transaction, Organization | Made a transaction after 08/01/15 where Average Order Value (AOV) lower than $50 |
Purchase Activity | Placed first order | Customer, Transaction, Organization | Made first order in the range of 7 to 14 days ago where Likelihood To Buy equal to “2 - Medium” |
Purchase Activity | Placed last order | Customer, Transaction, Organization | Made last transaction in the last 60 days where Transaction Revenue greater than $200 |
Purchase Activity | Purchased a product | Customer, Organization, Product, Product Category, Transaction, Transaction Item | Purchased a product before 08/01/16 where Organization Name equal to “San Francisco Store” and Transaction Item Revenue greater than $100 |
Purchase Activity | Made a number of transactions in a timeframe | Customer, TransactionSummary, Organization | Made greater than 5 transactions in the last 30 days where Organization Name equal to “San Francisco store” |
Purchase Activity | Purchase a number of products in a category | Customer, Organization, Product, Product Category, TransactionSummary | Purchased 5 products in the last 30 days where Category Name equal “Accessories” |
Purchase Activity | Customers who spent certain amount in a timeframe | Customer, TransactionSummary, Organization | Spent more than $300 in the last 30 days where subtype in Shipped, Returned |
Purchase Activity | Customers who spent certain amount in a transaction | Customer, TransactionSummary, Organization | Spent more than $500 in a single transaction in the last 30 days where Organization Type is Physical |
Web Activity | Browsed a product | Customer, Event, Product, Product Category | Browsed a product in the last 10 days where Product Name equal to “ProductABC” and Category Name equal to “CategoryXYZ” |
Web Activity | Customers who abandoned their cart | Customer, Event | Abandoned their cart 2 days ago and Likelihood to Buy equal to “1 - High” |
Email Activity | Performed an activity with message | Customer, Message | Performed an activity “emailClicked” where Message Name equal to “Abandoned Cart” |
Email Activity | Performed an event | Customer, Event | Performed the event “cartUpdated” in the last 30 days where User Client equal to A |
Email Activity | Performed a number of events in a timeframe | Same as Performed an event, but you can select the number of times the selected event type should have happened within the selected timeframe. This filter can be refined as well. | Performed the event “emailOpen” greater than 3 times in the last 30 days where Message Name equal to “Abandoned Cart” |
Household | Belongs to a household | Household summary | Belongs to a household where Average Order Value is greater than “$500” |
Including past audiences
This feature allows you to include easily customers that were extracted in a previously executed CDP campaign. Simply use that filter, and select via the drop-down (or start typing to reduce the list of values, then select the value) the campaign you want to look at, then select a timeframe to specify in which executions of the campaign the customer should have been included into. If this campaign had an A/B test setup (SFTP or SendGrid campaigns only), you can even specify which variant the customer has to be part of to be selected.
Note
This is not based on data we receive from your ESP or other sources, this data is updated in real-time every time you execute a campaign (after the campaign has been successfully extracted from CDP).
This feature is in BETA right now, please check with your CDP team whether this can be enabled for your tenant. Please note that this feature will start tracking past audiences only from the point it has been turned ON (and it will not go “back” to fetch previous campaign executions).
Next steps
The next article covers the way to setup your campaign to send specific data elements as “content” : selecting content
You can also go directly to the article listing all the content elements you can use in your campaigns : List of standard content elements