Audience Builder Criteria Glossary

Audience Builder allows for highly specific reporting and segmenting based on user data. This glossary includes definitions of each criterion that is available for you to use in Audience Builder.

Note that fields and values are case-sensitive, and that you can use Boolean OR logic within Value fields via the pipe symbol ( | ). For example, if you wanted to query for either 191 or 192, you would enter the value: 191|192.
 

 


User Vars

For a list of all var names in use across any group of users, see “Export Var Usage Data” on the page Export Lists and User Profile Data.

 

is

  • For Zephyr variables saved on User Profiles. Find users for whom the variable (in the Field) value (in the Value) matches.

is_criteria

  • Field: the variable to match (case-sensitive)
  • Value: the value of the variable

Please see Setting Variables for details on setting values on your subscribers.

“is” also works on variable values in an array and keys of an object. These variable data types can only be set via the API.

is not

  • Checks that the variable is not a match.
  • Note that if the variable doesn’t exist, this is also a “null” or non-match. To return only users who a) have the variable set on their profile b) variable value is not a match, also use the “exists” criterion. For example:

is not_query

is at least

  • For number type variables. For example: survey_score or age.
  • Note that with the “is at least” criteria you are including the number you are querying.

atleast_query

In the above example, the birth_date variable is set on each user containing the day of the month of their birth. The results would return anyone who was born on the 14th-31st of the month (it would include the number queried).

is at most

  • For number “type” variables. For example: survey_score or age.
  • Note that with the “is at most” criteria you are including the number you are querying.

is greater than

  • For number “type” variables. For example: survey_score or age.
  • Note that with the “is greater than” criteria you are NOT including the number you are querying in the report or list you are creating.

isgreaterthan_query

In the above example, the results would return anyone who had a survey_score greater than 7.

is less than

  • For number “type” variables. For example: survey_score or age.
  • Note that with the “is less than” criteria you are NOT including the number you are querying in the report or list you are creating.

exists

  • Find subscribers on whom a certain variable is set (ie that variable ‘exists’ on their user profile).

exists_criteria

In the above example, this query would pull any user who has “first_name” as a variable on their user profile.

does not exist

  • Returns subscribers who do not have that variable saved on their user profile

doesnt_exist_query

In the example above, subscribers who do not have the variable “first_name” would be returned.

contains

    • Checks the value of a variable to see if it contains certain characters. For example, to find users whose signup source contains “google”

contains_query

  • The “contains” criteria can also be used to segment by variable values that are in an array.

“contains” does not check integers (i.e. contains 3). If you wish to search for a number value, consider saving the var as a string. Otherwise, use the “is less/greater” than criteria.

The pipe symbol | cannot be used to indicate “OR” within the value field for this criteria. To query multiple different values, add another separate criteria row to the query for each additional value.

does not contain

  • Checks the value of a variable to see if it does not contain certain characters. For example, to find users who do not have a first name that contains ‘Sam’, search for Field : First_Name and Value : Sam.
  • The “does not contain” criteria can also be used to segment by variable values that are in an array.

“contains” does not check integers (i.e. contains 3). If you wish to search for a number value, consider saving the var as a string. Otherwise, use the “is less/greater” than criteria.

The pipe symbol | cannot be used to indicate “OR” within the value field for this criteria. To query multiple different values, add another separate criteria row to the query for each additional value.

Engagement

engagement level is

  • Search by users’ level of engagement at the time of your query

engagement level is at least

  • The level of engagement with no engagement level under the selected Value

Screen Shot 2016-10-21 at 5.45.45 PM

In the example above, if you were to choose “new” it would return users who are new, passive, active, and engaged.

engagement level is at most

  • Level of engagement with no higher engagement level above the selected Value

Screen Shot 2016-03-27 at 9.03.46 PM

In the example above, results will return subscribers with engagement levels of dormant and disengaged.

Date Vars

is before date

  • Finds users on whom the specified variable is a date that is strictly before the criterion date
  • Variable must be either Unix timestamp or match one of the following forms: yyyy-mm-dd, yyyymmdd, yyyy-mm, yyyy
  • yyyy-mm assumes the first day of the given month, yyyy assumes January 1 of the given year
  • Criterion date can be selected in the UI via exact time, a date selector, or relative time. (if relative time is used, time is relative to the time of query submission, and not to the time it is actually processed)

Screen Shot 2016-03-26 at 8.49.56 PM

is since date

  • Same as “is before date”, except checks that the variable is on or after the criterion date

is on date

  • Same as “is before date”, except checks that the variable date is on the same day as the criterion date

is anniversary of date

  • Same as “is before date”, except checks that the variable date is on the same day of the year as the criterion date.  Note this matches anniversary dates in both directions. For example, if the criterion date is 2014-03-31, it will match both 2012-03-31 and 2015-03-31. If the year is not known, or you do not wish to check against a year, save the var as “0000-MM-DD”, replacing the Year value with four zeros.

anniversary_query

The above example will query a list of users whose birthday (yay!) is 30 days from today’s date. If built as a smart list, it will update each day.

Interest

interest is greater than or equal to

Find users who are interested in a certain interest tag by a certain magnitude more than the rest of your known users.

  • In the Value field, enter the tag name.
  • Under the Criteria drop-down, enter a multiplier of interest beyond that of your average user. For example, if you entered a value “gingham” and the number 2, you will identify your users who have exhibited 2 times the interest (or greater) in gingham, compared to your average user.

Screen Shot 2016-10-21 at 5.52.50 PM

no interest or interest is less than

Find users who are less interested in a certain interest tag than the rest of your known users or have shown no interest in the tag at all.

  • In the Value field, enter the tag name.
  • Under the Criteria drop-down, enter a multiplier of interest. For example, if you entered a value “puppies” and the number 1, you will identify your users who have a less-than-average interest in puppies.

Screen Shot 2016-10-21 at 5.54.36 PM

Geographic

Users’ geographic locations are automatically recorded each time they click a link within one of your emails. You can use this data to create geolocation-segmented lists in Audience Builder.

Screen Shot 2016-10-21 at 6.21.24 PM

Audience Builder provides the following location-frequency categories as criteria. The user matches or fails to match these criteria based on their relative number of clicks that occurred within a given region: Majority Resident (50%), Frequent (25%), Occasional (10%), Ever Visited (1%).

When Majority Resident is selected, if there is no majority location, the user’s most common location is used.

It’s important to note that locations are determined by the subscriber’s IP address when they click-through an email. If a subscriber has never clicked-through any of your mail, Sailthru cannot determine their location, and the user will not meet any of these criteria, regardless of the region entered.

Also keep in mind that while Sailthru uses the previously described method to identify geolocation, you can also collect user locations on your own as vars. For example, on your signup form, you can request that the user enter a home “City”, “State”, etc. This section does not apply to such custom var data, but only to the geolocation data that is logged by Sailthru.

Use the following reference, along with the page Geolocation Codes and Syntax, to formulate your geolocation queries in Audience Builder.

geolocated city

  • Based on the IP address from which a subscriber clicks through your email
  • Search users by city

geolocatedcity_query

Enter multiple cities, states, or countries (dependent on the criteria) separated by the | symbol (“or” in boolean logic).

geolocated state

  • Search users by US state
  • Based on the IP address from which a subscriber accesses your email
  • Use the “|” symbol as an OR to query multiple states

geolocatedstate_query

geolocated country

  • Search users by country
  • Based on the IP address from which a subscriber accesses your email

Screen Shot 2016-10-21 at 5.57.11 PM

The above query would pull users located in the US or Canada into your report or list.

geolocated zip

  • Search users by (US) zipcode
  • Based on the IP address from which a subscriber accesses your email

Screen Shot 2016-10-21 at 5.58.46 PM

The above example would pull users who at least 25% of the time they click-through their email, their zipcode is “90210”.

geo radius

  • Search users by their proximity to a zip code or a city center. We collect geolocation based on the the location where a user most clicks from. NOTE: This only works for US-based cities or zip codes.
  • You may search in two ways:
    1. Using geolocation data collected by Sailthru
      • To activate, check the box “Use geo-location”
      • The user must have opened an email for this data to be collected
      • The data is based on the IP address where the user opens email
      • This data may be either a zip code or a city in “City, State” format (e.g. New York, NY)

      Screen Shot 2016-03-27 at 9.11.09 PM

    2. Using a variable that you previously set on your users based on data you have collected.
      • To activate, uncheck the box “Use geo-location,” and then enter your variable in the Field.
      • The variable name can be whatever you wish (e.g. “zip_code” or “zipcode”
      • See Setting Variables. You must enter this variable in “Field” (e.g. “zip_code”)

      Screen Shot 2016-03-27 at 9.11.57 PM

geo mobile radius

Based on each user’s last-recorded location when using your app (if integrated with the Sailthru Mobile SDK), find users who have a given proximity to a certain city center or zip code.

Profile Keys

key exists

  • Please see API user call for details of user keys. This Criterion currently allows for ‘email’ in Field.

key_query

key does not exist

Identify users who do not have a certain key associated with their profile: either an e-mail address or an extid (external, client-specified ID).

Email Address

email domain is

  • Query by subscribers’ email domain(s). (i.e. gmail.com or yahoo.com)

domainis_query

The above example would return subscribers who receive email at gmail.com OR yahoo.com.

email matches

  • Query by subscribers’ email addresses, using * as a wildcard

Screen Shot 2016-10-21 at 6.25.57 PM

The above example would return subscribers whose email address ends in ‘@gmail.com’.

email does not match

  • Query by subscribers’ email domain(s). (i.e. gmail.com or yahoo.com)

Screen Shot 2016-10-21 at 6.24.44 PM

The above example would return all email addresses beginning with ‘support@’. Multiple wildcards can be used. For example, querying *a* would return all emails containing the letter a.

Subscription Status

is valid (not optout/hardbounce)

  • Returns subscribers who have not opted out or hardbounced

first signed up on

  • Enter an exact date to return subscribers who signed up for your emails on that day.

You can also enter “today” or “yesterday” as an accepted value.

Screen Shot 2016-03-27 at 9.13.32 PM

first signed up before

  • Enter a date to return subscribers who signed up before that day
  • Use an exact date or “-x days” if looking for dynamic criteria

Screen Shot 2016-04-22 at 10.36.30 AM

first signed up since

  • Enter a date to return subscribers who signed up on and after that day

Screen Shot 2016-03-27 at 9.14.26 PM

signed up for source list on

Users who signed up (for the Natural List you are using as the Source List) on an exact date or a certain amount of days in the past (for example: “-7 days” means ‘signed up exactly 7 days ago’). “today” and “yesterday” are also acceptable values.

Screen Shot 2016-10-21 at 6.32.06 PM

signed up for source list before

Users who signed up (for the Natural List you are using as the Source List) before an exact date or a certain amount of days in the past (for example: “-7 days” means ‘signed up more than a week ago’). “today” and “yesterday” are also acceptable values. NOTE: The date you query will not be included.

signed up for source list since

Users who signed up (for the Natural List you are using as the Source List) since an exact date or a certain amount of days in the past (for example: “-7 days” mean signed up within the past week’). “today” and “yesterday” are also acceptable values. NOTE: The date you query will be included.

Screen Shot 2016-10-21 at 6.31.14 PM

has opted out of template

  • Find subscribers who opted out of a specific transactional template

has opted out of mass mail only

  • Find subscribers who opted out of campaigns only (optout_blast)

has opted out of mass mail

has opted out of all email

  • Subscriber has opted out of all mail (optout_all)

opted out on

  • Find subscriber who opted out (either optout_all or optout_blast; this does not include a list removal) on the date specified

opted out before

  • Find subscribers who opted out before the date specified. The query will not include optouts that occurred on the date entered.

Screen Shot 2016-10-21 at 6.33.01 PM

For example: a value of 12/1/2012 would return users who opted out on 11/30 and earlier.

This checks for optout_all or optout_blast; this does not include a list removal.

opted out after

  • Find subscribers who opted out after the date specified. The query will include optouts that occurred on the date entered.

Screen Shot 2016-03-27 at 9.15.08 PM

This checks for optout_all or optout_blast; this does not include a list removal.

Purchase

first purchased

Search a time for the first purchase a subscriber made on your site. (Requires Purchase API integration.)

Search for users who completed this event according to the following time-based criteria:

  • ever – event occurred any time in the history of the user account
  • never – event has never occurred for the user
  • since – event occurred between the specified date and today (inclusive)
  • not since – event did not occur between the specified date and today (inclusive)
  • in the last – event has occurred since ‘the current time of day, X days ago’
  • not in the last – event has not occurred ‘since the current time of day, X days ago’
  • between (relative dates) – event occurred between X and Y days ago, based on the current time this query is submitted. For example, ‘between 2 to 4 days ago’ is translated to ‘between 48 and 96 hours ago’, that is, “the current time of day 4 days ago through that time 2 days ago”.
  • between (exact dates) - event occurred between the specified dates (inclusive of the dates specified)

Screen Shot 2016-10-21 at 6.34.57 PM

The above query would pull users who made their first purchase within the past 30 days.

last purchased

Search a time period for the last purchase made by users. (Requires Purchase API integration.)

Search for users who completed this event according to the following time-based criteria:

  • ever – event occurred any time in the history of the user account
  • never – event has never occurred for the user
  • since – event occurred between the specified date and today (inclusive)
  • not since – event did not occur between the specified date and today (inclusive)
  • in the last – event has occurred since ‘the current time of day, X days ago’
  • not in the last – event has not occurred ‘since the current time of day, X days ago’
  • between (relative dates) – event occurred between X and Y days ago, based on the current time this query is submitted. For example, ‘between 2 to 4 days ago’ is translated to ‘between 48 and 96 hours ago’, that is, “the current time of day 4 days ago through that time 2 days ago”.
  • between (exact dates) - event occurred between the specified dates (inclusive of the dates specified)

Screen Shot 2016-10-21 at 6.36.10 PM

The above query would pull users who made their last purchase (could be their first, second, third, etc. purchase) within the past 30 days.

made a purchase on

  • Requires Purchase API
  • Find all users who have made a purchase on a specific date

made a purchase before

  • Requires Purchase API
  • Enter a date to return users who purchased an item before that date
  • The value may be dynamic. For example, you could use ‘-7 days’ for the past week

Screen Shot 2016-10-21 at 6.37.46 PM

made a purchase since

  • Requires Purchase API
  • Enter a date to return users who purchased an item after that date
  • The value may be dynamic. For example, you could use ‘-7 days’ for the past week

has an incomplete purchase

  • Requires Purchase API enabled
  • Find users with items currently in their shopping cart who have not completed checkout

has purchased at least

  • Requires Purchase API enabled
  • Searches users who have made at least a certain number of purchases

Screen Shot 2016-10-21 at 6.38.31 PM

The above query would pull any purchasers who have made at least 1 purchase into your report or list.

has purchased at most

  • Requires Purchase API enabled
  • Searches users who have made at most a certain number of purchases

has purchased

  • Requires Purchase API enabled
  • Search for purchases by item title (case insensitive) or id. The id parameter may hold an SKU or other unique id for the item, depending on how you have configured the Purchase API.

has purchased with tags

  • Search for purchases based on any purchase tags you have passed on a product (case insensitive)
  • Requires Purchase API implementation, please see “tags” parameter

Screen Shot 2016-10-21 at 6.43.07 PM

had incomplete purchase

Search user who had an incomplete purchase within a specified time period. (See the incomplete parameter in the Purchase API.)

Search for users who have this event on their profile according to the following time-based criteria:

  • ever – event occurred any time in the history of the user account
  • never – event has never occurred for the user
  • since – event occurred between the specified date and today (inclusive)
  • not since – event did not occur between the specified date and today (inclusive)
  • in the last – event has occurred since ‘the current time of day, X days ago’
  • not in the last – event has not occurred ‘since the current time of day, X days ago’
  • between (relative dates) – event occurred between X and Y days ago, based on the current time this query is submitted. For example, ‘between 2 to 4 days ago’ is translated to ‘between 48 and 96 hours ago’, that is, “the current time of day 4 days ago through that time 2 days ago”.
  • between (exact dates) - event occurred between the specified dates (inclusive of the dates specified)

Note: Will not find incomplete purchases (i.e. cart additions) made in the past 30 minutes. This is to conform with industry standards avoid sending cart abandon messages during active shopping sessions.

Screen Shot 2016-10-21 at 6.43.46 PM

total purchase value is at least

  • Requires Purchase API enabled
  • Search users who have made a purchase that is at least a certain amount over their lifetime

Screen Shot 2016-10-21 at 6.47.06 PM

total purchase value is at most

  • Requires Purchase API enabled
  • Search users who have made a purchase that is at most a certain amount over their lifetime

net revenue value is at least

  • Requires Purchase API and Return API are enabled
  • Search users who have purchased at least a certain amount over their lifetime, after their return losses have been subtracted out.

net revenue value is at most

  • Requires Purchase API and Return API are enabled
  • Search users who have purchased at most a certain amount over their lifetime, after their return losses have been subtracted out.

largest purchased item price is at least

  • Requires Purchase API enabled
  • Find out the largest purchase made by each subscriber, search by at least a certain amount (USD only)

Screen Shot 2016-10-21 at 6.47.38 PM

largest purchased item price is at most

  • Requires Purchase API enabled
  • Find out the largest purchase made by users. Search by a maximum amount. (USD only.)

purchase order var is

    • Find user based on order purchased using purchase var
    • For this to work, your account must be receiving user purchase information using our purchase API call

unnamed-2

The above example would query users who have placed at least one order with the purchase order variable “promotion” set to the value of “fall-sale-2016.”

purchase item var is

    • Find user based on item purchased using purchase item var
    • For this to work, your account must be receiving user purchase information using our purchase API call

Purchase Item Var

The above example would query users who have purchased at least one item with the purchase item variable “designer” set to the value of “vera-wang.”

 

Email Actions

last clicked

Search for users who last clicked a link within an email according to the following time-based criteria:

  • ever – event occurred any time in the history of the user account
  • never – event has never occurred for the user
  • since – event occurred between the specified date and today (inclusive)
  • not since – event did not occur between the specified date and today (inclusive)
  • in the last – event has occurred since ‘the current time of day, X days ago’
  • not in the last – event has not occurred ‘since the current time of day, X days ago’
  • between (relative dates) – event occurred between X and Y days ago, based on the current time this query is submitted. For example, ‘between 2 to 4 days ago’ is translated to ‘between 48 and 96 hours ago’, that is, “the current time of day 4 days ago through that time 2 days ago”.
  • between (exact dates) - event occurred between the specified dates (inclusive of the dates specified)

Screen Shot 2016-10-21 at 6.49.07 PM

last opened

Search for users who last opened an email according to the following time-based criteria:

  • ever – event occurred any time in the history of the user account
  • never – event has never occurred for the user
  • since – event occurred between the specified date and today (inclusive)
  • not since – event did not occur between the specified date and today (inclusive)
  • in the last – event has occurred since ‘the current time of day, X days ago’
  • not in the last – event has not occurred ‘since the current time of day, X days ago’
  • between (relative dates) – event occurred between X and Y days ago, based on the current time this query is submitted. For example, ‘between 2 to 4 days ago’ is translated to ‘between 48 and 96 hours ago’, that is, “the current time of day 4 days ago through that time 2 days ago”.
  • between (exact dates) - event occurred between the specified dates (inclusive of the dates specified)

Opens are identified by the loading of a beacon image within an email message or clicking of a link within an email message. If a user opens an email with images disabled in their email client and does not click a link, the open is not recorded.

Screen Shot 2016-10-21 at 6.49.46 PM

opened

Searches subscribers who opened a certain amount of email message(s) within a time period.

Uses the same Value parameters as Messaged.

Opens are identified by the loading of a beacon image within an email message or clicking of a link within an email message. If a user opens an email with images disabled in their email client and does not click a link, the open is not recorded.

Screen Shot 2016-10-21 at 6.50.18 PM

The above example would query users who have opened at least three times in the past three months.

clicked

Searches subscribers who clicked a certain amount of email message(s)

Uses the same Value parameters as Messaged and Opened

Screen Shot 2016-04-22 at 10.31.27 AM

 

reads email using

Find subscribers based on what browser and/or mobile device(s) they have ever used to read your email.

This can also be used to segment all users who read your email on any mobile device, if you include all mobile device types in the query.

Screen Shot 2016-03-27 at 9.29.58 PM

 

  • Enter any of the following devices exactly as written below. To match at least one of multiple criteria (using an ‘OR’ statement), separate all using a pipe (“|”).
    • iPad
    • iPhone
    • Android
    • Android Tablet
    • BlackBerry
    • Windows Phone
    • Windows Tablet
    • Nook
    • Other Tablet
    • Other Phone
    • Firefox
    • Chrome
    • Safari
    • Opera
    • Opera Mini
    • Internet Explorer
    • Thunderbird
    • Gmail
    • Outlook
    • Xbox
    • Nintendo
    • Playstation
    • Tesla Model S
    • Other
  • For example, to match users who have used any mobile device, enter:
    iPad|iPhone|Android|Android Tablet|Windows Phone|Windows Tablet|Nook|BlackBerry|Opera Mini|Other Tablet|Other Phone

Deliverability

last bounced

Search subscribers who last bounced according to the following time-based criteria:

  • ever – event occurred any time in the history of the user account
  • never – event has never occurred for the user
  • since – event occurred between the specified date and today (inclusive)
  • not since – event did not occur between the specified date and today (inclusive)
  • in the last – event has occurred since ‘the current time of day, X days ago’
  • not in the last – event has not occurred ‘since the current time of day, X days ago’
  • between (relative dates) – event occurred between X and Y days ago, based on the current time this query is submitted. For example, ‘between 2 to 4 days ago’ is translated to ‘between 48 and 96 hours ago’, that is, “the current time of day 4 days ago through that time 2 days ago”.
  • between (exact dates) - event occurred between the specified dates (inclusive of the dates specified)

marked as spam

  • Returns subscribers who have marked one of your emails as spam

status is softbounce

  • Find subscribers who have been marked as a softbounce (for more information on softbounces, see Delivery)

status is hardbounce

  • Find subscribers who have been marked as a hardbounce

Communication

messaged

  • Searches subscribers who received a certain amount of email message(s) (both campaign and transactional) within a time period.

Screen Shot 2016-03-27 at 9.09.34 PM

Onsite

viewed page

  • Identify users who have or have not been on your site (i.e. viewed a page) a certain number of times
  • For example: If you’d like to identify users who have been on-site at least 2 times in the past thirty days you can accomplish that with viewed page. If you want to identify users who have never visited your site, use last viewed, instead (see below).
    viewed-page

browses site using

  • Select users based on devices (for mobile visits) and/or browsers (for desktop visits) that they have used to visit your site on at least one occasion.
  • Enter any of the following devices exactly as written below. To match at least one of multiple criteria (using an ‘OR’ statement), separate all using a pipe (“|”).
    • iPad
    • iPhone
    • Android
    • Android Tablet
    • BlackBerry
    • Windows Phone
    • Windows Tablet
    • Nook
    • Other Tablet
    • Other Phone
    • Firefox
    • Chrome
    • Safari
    • Opera
    • Opera Mini
    • Internet Explorer
    • Thunderbird
    • Gmail
    • Outlook
    • Xbox
    • Nintendo
    • Playstation
    • Tesla Model S
    • Other
  • For example, to match users who have used any mobile device, enter:
    iPad|iPhone|Android|Android Tablet|Windows Phone|Windows Tablet|Nook|BlackBerry|Opera Mini|Other Tablet|Other Phone

Screen Shot 2016-10-21 at 6.51.24 PM

last viewed

Search users who last viewed a page on your site according to the following time-based criteria:

  • ever – event occurred any time in the history of the user account
  • never – event has never occurred for the user
  • since – event occurred between the specified date and today (inclusive)
  • not since – event did not occur between the specified date and today (inclusive)
  • in the last – event has occurred since ‘the current time of day, X days ago’
  • not in the last – event has not occurred ‘since the current time of day, X days ago’
  • between (relative dates) – event occurred between X and Y days ago, based on the current time this query is submitted. For example, ‘between 2 to 4 days ago’ is translated to ‘between 48 and 96 hours ago’, that is, “the current time of day 4 days ago through that time 2 days ago”.
  • between (exact dates) - event occurred between the specified dates (inclusive of the dates specified)

Lists

is a member of list

  • Query who is a member of particular list(s) that you enter.
    The llst name is case-sensitive and must be entered exactly as it appears in the Lists page.

Screen Shot 2016-03-27 at 9.29.16 PM

is not a member of list

  • Query who is not a member of particular list(s) that you enter.
    The llst name is case-sensitive and must be entered exactly as it appears in the Lists page.

is not a member of any list

When you add a new user through a Sailthru list, a user profile is simultaneously created. However, it is possible to send a transactional email (e.g. an order confirmation email) to a user who is not yet on any list. When this occurs, a user profile is automatically created (so that you may track site and purchase data for this user), but the user is still not a member of any list. This criteria (“is not a member of any list”) will identify all such users who have a profile, yet are not a member of any list.

Mobile App

has any app

  • Query for subscribers who have an app device set on their user profile.

has app(s)

  • Query for a specific mobile app using the app’s identification number (i.e. aid)
  • You can query for multiple apps using multiple aids divided by “|” (i.e. “or”)

Consider the following example:

This query searches for the following apps, and returns the intended Audience Builder action:

  • App with aid 5480e163a6cba836608b4ed6
  • App with aid 51fbcad07332c1395300008a

FURTHER INFORMATION:
Smart Data Mobile: Glossary of Terms
Determining An Application’s ID

Prediction Manager User Predictions

For detailed information about how to use these Prediction Manager criteria, see the User Predictions page.

AOV if purchase(s) occur within 7 Days (aov_7)

The predicted order value if the user makes a purchase within the next 7 days.

Message Volume Within 1 Day (msgs_1)

The expected message volume for the user over the next day.

Open Within 7 Days (openrate_7)

The probability that the user opens a message within the next 7 days.

Click Within 7 Days (click_7)

The probability that the user clicks a link in a message within the next 7 days.

Optout Within 7 Days (optout_7)

The probability that the user opts out of messaging within the next 7 days.

Purchase Within 1 Day (purchase_1)

The probability that the user makes a purchase within the next day.

Purchase Within 7 Days (purchase_7)

The probability that the user makes a purchase within the next 7 days.

Purchase Within 30 Days (purchase_30)

The probability that the user makes a purchase within the next 30 days.

Page Views Within 30 Days (pv_30)

The user’s predicted number of pageviews within the next 30 days.

Revenue Within 30 Days (rev_30)

The predicted revenue generated by the user over the next 30 days.

Revenue Within 365 Days (rev_365)

The predicted revenue generated by the user over the next 365 days.

Audience Builder in Campaign Detail Reports

The following criteria are only available in the Audience Builder functionality available in any Campaign Detail Report.

You must click on the Audience Builder button found in this report to access these criteria. After selecting any of the criteria below, Submit Filter. Once the job runs, if you’d like to save these users to a new or existing Natural List, select Save To List.

opened message

  • Find subscribers who opened your email message. Sailthru only tracks unique opens therefore even if the user opens the email twice, it will only count as one open.

Screen Shot 2016-10-21 at 6.56.24 PM

did not open message

  • Find subscribers who did not open your email message

Screen Shot 2016-10-21 at 6.59.57 PM

clicked message

  • Find subscribers who clicked on a link within the email message

did not click message

  • Find subscribers who did not click on a link within the email message

purchased from this message

  • Requires Purchase API enabled
  • Find subscribers who made a purchase as a result of this email message

Screen Shot 2016-10-21 at 7.00.36 PM

did not purchase from this message

  • Requires Purchase API enabled
  • Find subscribers who did not make a purchase as a result of this email message

Screen Shot 2016-10-21 at 7.02.00 PM

opted out from this message

  • Query subscribers who unsubscribed from this particular message; status is “optout(blast)”

clicked on URL

  • Find subscribers who clicked on a particular URL within the campaign


The URL must be entered exactly as it appears in the Links tab of campaign detail report
Screen Shot 2016-03-27 at 9.30.52 PM

was sent URL

  • Find subscribers who received a specific URL
  • Must match exactly, including case-sensitivity
  • This is particularly useful when Zephyr syntax variables specific to each subscriber are passed into a URL

was sent subject line

  • Find subscribers who received a specific subject line in the campaign
  • Must match exactly, including case sensitivity
  • This is particularly useful when Zephyr syntax variables specific to each subscriber are passed into the subject line

message is softbounce

  • Find subscribers for whom the message softbounced
  • Note that this queries this message’s delivery only; the user’s status could still remain valid

message is hardbounce

  • Find subscribers for whom this message hardbounced
  • Note that this queries this message’s delivery only; user’s status may have since become valid

List of All Criteria

Click a name to jump to its definition on this page.

Top