Real People, 24/7

Filtering And Segmentation

Our Filtering feature in SyncApps can be used to sync a subset of records based on specific criteria.

In a trial or plan using SyncApps, you can sync all the records if they match your criteria, so the best practice on a trial is to place test email addresses in a Campaign, List View, or Saved Search, then use Filtering for easy testing.  

The Object Type selected in Step 1 determines what is looked at in Step 4 of the automation.

Some Use Cases

For example, to sync only Contact records with the country, which is the United States, you can create the following filter : 

Country [Is Equal To] the United States


Conditional Operators

The following operators can be used to create criteria:

  • Is Equal To
  • Check if the field value equals a specific value
  • Is Not Equal To
  • Check if the field value does not equal a specific value
  • Starts With
  • Check if the field value starts with a specific value
  • Does Not Start With
  • Check if the field value does not start with a specific value
  • Contains
  • Check if the text field contains a specific value
  • Does Not Contain
  • Check if the text field does not contain a specific value
  • Greater Than
  • For numeric or date comparison
  • Greater Than or Equal
  • For numeric or date comparison
  • Less Than
  • For numeric or date comparison
  • Less Than or Equal
  • For numeric or date comparison
  • Is Blank
  • Check if the text is blank
  • Is Not Blank
  • Check if the text is not blank
  • Is True (Checkbox Checked)
  • For boolean value or usually a checkbox in UI
  • Is False (Checkbox Unchecked)
  • For boolean value or usually a checkbox in UI 

Date Criteria

Date criteria must use YYYY-MM-DD format, so if we need to sync a record that is created after July 20th, 2022, we can use the following criteria:

Created [Greater Than] 2022-07-20

For relative date comparison, SyncApps provides a function to_date("x days/months/years ago").

Using that function, we can create criteria to sync records that were created within the last 30 days:

Created [Greater Than] or [Equal] to_date("30 days ago")


Complex Criteria

Complex criteria can also be created by combining expressions using AND and OR operators.  For example, if we want to sync records with an email address that is not blank and lives in CA or NY state, we can create the following expression:  

Email Address Is Not Blank AND (State Is Equal To CA OR State Is Equal To NY)

In the filtering feature in SyncApps, the above conditions can be expressed like this below:


Please make sure Grouping, AND, and OR operators are chosen correctly.  In the above example, "State Is Equal To CA OR State Is Equal To NY" must be grouped using an OR operator to produce correct logic.

If you have multiple criteria that include the boolean field( True or False), make sure that you have set it to "Is False (Checkbox Unchecked)" or "Is True (Checkbox checked).


The screenshot above caused the error because Opted out is a boolean field, so it should be "Is False (Checkbox Unchecked)" or "Is True (Checkbox checked); see the correct setup below:


Let's see the difference between our Step 5 Filtering and Segmentation feature operator, the “Contains” vs. “Is Equals to.”

Mailchimp for Salesforce Use Case  


How to include records that have one or more checkboxes on their record? In this case, we are tracking badges.

The first inclination for many is to set up Step 4 in this manner below using the "Is Equal To" operator, yet this is not the best practice to manage this type of requirement.


Contacts with multiple badges (checkboxes) will be filtered out based on this setup above, as it is exclusionary. The best practice is to use the "Contains" instead of the "Is Equal To" operator.

Let's see another use case for Filtering Date Parameters:

Constant Contact for Salesforce Use Case   


How to pick up the current date daily to exclude members who expired.

The initial solution for this is to add a filter using the "Paid through date" field and want the date parameter to be today's date to exclude members who expired. 


Yet this is not the best practice for managing this type of requirement.


       -  Badges Contains X
       -  Badges Contains Y

    -  Paid date > Z

Parenthesis must match the grouping.

What this means is the Parenthesis of the logical requirement.

Creating a parenthesis representation for complex logic (which contains both AND and OR) is good. 
For example, we have the requirement that a record must have paid date > Z and have badges containing either X or Y.

We can translate the requirement into this:

((Badges Contains X OR Badges Contains Y) AND Paid date > Z)
Then to convert it to the SyncApps filtering feature shown in Step 4, we need to go from the outer parenthesis first.

We need to create like this:

AND Group
- OR Group
- Badges Contains X
- Badges Contains Y
- Paid date > Z

This one below works great if configured using the Step 4 feature:


Hope you found this article helpful in getting to know more about our Filtering and Segmentation features.

Need some help?

Check out the options below on how you can contact our Support team and find the answers you need to help you with your SyncApps integrations.

Help Center & Email is 24/7 to | Live Chat & Phone is scheduled  


Check out these Help Desk articles for answers to frequently asked questions.

Get Started | Login Issues | Pricing

Have more questions? Submit a request