Queries

The Query Builder allows you to build powerful, detailed queries for segmenting, editing and analyzing the users on your lists. Using the Query Builder, you can:

• New: Query users based on mobile and browsing data
• get a Snapshot Report that gives you detailed information about a group of users
• generate lists of users based on criteria
• create Smart Lists that automatically update to users matching the criteria
• set a bunch of vars to users or opt users in/out fitting a certain criteria (bulk update)

To access the Query Builder, click on Query Builder from the Lists page. As seen on the screen cap below.

Once you are on the Query Builder page you have the option of selecting what type of query you would like to perform as mentioned in the bulleted points above. After you selected the type of query, you can select which list you would like to query. You can query all lists, a specific list, or multiple lists at once. (Note: "All Users" will select all users ever uploaded into your Sailthru account, including those on deleted lists.) Once you select the type of list that you want to query you can start adding the criteria of what you wish to pull from our data.

If you want to add users and their vars from one list to another, select "Generate List", pick the source list in Source List, then type the name of the list you want to add them to in "List Name". The Generate List process is additive, so if you already have entries in the target list, they will not be overwritten. You don't have to select anything in the Query Builder. If the Query Builder is not filled out, it uses all users in the Source List.

There are lots and lots of criteria. Here's what they all mean:

Exactly match one of the user's replacement-variables. Put the name of the variable (case sensitive) in the Field column and the value of the variable in the Value column. As the example below shows, if you had a replacement variable called "zip_code" you would enter this variable name in the field column, select the criteria "is", and then enter the "value" from the information you gathered (In this case the value is the zip code 53214). If you put in a zip code as a string, remember to query for it as a string using quotation marks, e.g. "53214". Remember than these values are what you have collected from either user signup or a form and are not available through the data provided by Sailthru.

• If you want to match against multiple variables, use|bars|to|separate|values without any spaces in between. It will match any users matching any of the values. This is treated like an "or" statement.

A literal expression that negates the criteria (e.g. Email is not support@sailthru.com)

Ideal for numerical values

Not an optout or hardbounce

Query by the email domain. For example; gmail.com or yahoo.com

Search users by what city their IP accesses your email from - geolocation

Search users by what US state users access your email from - geolocation

Search users by what country they access your email from - geolocation

Search users by what US zipcode they access your email from

These apply to the Horizon interest tags. You can query according to the interest tags you have incorporated into your content.

The exact level of engagement on the time of your query.

The level of engagement, with no subordinate engagement level under the selected criteria.

The level of engagement, with no higher engagement level above the selected criteria.

For accounts with the purchase API enabled, query a beginning date for items purchased

For accounts with the purchase API enabled, query an end date for items purchased

Broken down by last amount of days or a selected date of when users last clicked an email

Broken down by last amount of days or a selected date of when users last opened an email

Email was marked as either a softbounce or hardbounce by an ISP

Select a date where user’s signed up to your emails before designated date.

Select a date where user’s signed up to your emails since a designated date.

Has opted out of transactional template (i.e. password reset)

Has opted out of campaigns only (They did not click on the Do Not Email button.)

Can also include those who did not opt out of the email

User has opted out of mass mail and template (They clicked on the Do Not Email button.)

For accounts with the purchase API enabled, query a minimum purchase total (in USD only)

For accounts with the purchase API enabled, query a maximum purchase total (in USD only)

For accounts with the purchase API enabled, query total purchase value at checkout

For accounts with the purchase API enabled, query total purchase floor at checkout

Largest purchase item is at most the selected dollar amount

Is a member of particular list(s) that you select

Member is not a member of a list

The users status been marked as a softbounce

The users status has been marked as a hardbounce

*If using the query builder within the campaign report, "status is soft/hardbounce" is different from "message soft/hardbounced." The former is the user status at the time of the campaign send, and the latter is the user status resulting from the campaign send.

Message has been marked as open. Sailthru only tracks unique opens therefore even if the user opens the email twice, it will only count as one open.

Message has been marked as not opened

User clicked on message in email

User did not click message in email

For users with the purchase API enabled, query that this message resulted in a sale

User has unsubscribed from this particular message

User has clicked on a URL in the campaign

User received a specific URL (If using our behavioural tool Horizon to send personalized emails, different URLs would be sent out for each user.)

User received a campaign with a specific subject line. Message must match exactly, including case sensitivity. (If using our behavioural tool Horizon to send personalized emails, different subject lines may be sent out for each user.)

Only the message softbounced; the user's status could still remain valid.

Only the message hardbounced; the user's status could still remain valid.

*If using the query builder within the campaign report, "status is soft/hardbounce" is different from "message soft/hardbounced." The former is the user status at the time of the campaign send, and the latter is the user status resulting from the campaign send.