When setting targeting conditions in playbooks it is important to understand the difference between AND Statements and OR Statements. This article will define each type of statement and give examples of how they work.
In this article, we'll go over:
Billing Plan: And/Or targeting conditions are available on the Premium, Advanced, and Enterprise billing plans.
Intended Audience:
- Marketing Users
- Playbook Builders
AND Statements

The center section of the circles where they overlap would be the matching AND section. The area where the different groups have things in common.
An AND statement is a specific statement that has to meet ALL of the criteria in the conditions. This is used when you have multiple conditions that you want to match before showing the playbook. This should be thought of as an “all or none” statement. If any one condition is not met then the playbook will not fire.
Example:
You want the bot to show on any page that meets all 3 conditions.

This matches all 3 criteria:

This matches only 2 of the 3 criteria:

OR Statements

Every value in the box that encloses all three circles matches an OR statement.
An OR statement is a broad statement that can meet ANY of the conditions or groups of conditions you set. This is used when you have multiple conditions but you only need one of them to match before showing the playbook. This should be thought of as an “anything goes” statement. If any of the conditions meet the playbook will fire.
Example:
You want the bot to show on any page that meets any of the 3 conditions (could be 3 different OR statements like Option 1 or all on one line like Option 2).
Option 1:

Option 2:

This matches one part of the criteria:

This matches another part of the criteria:

IMPORTANT NOTE. If you use an OR condition then it can match any of the statements to show the playbook. If any of your conditions are broad it would nullify the specific conditions you set as shown in the example below.

Condition Group 2 is broad and overrides the first condition to show the playbook.
