Use Multiple Targeting Conditions (All vs Any)
Learn when to use All or Any when creating targeting logic for your experiences.
Table of Contents
You can add multiple conditions to an experience, and make it so the user must match all of them or simply one of them.
'All' Condition (AND Operator)
When setting your conditions up to target based on ‘All’, the rule of thumb will have to be that Appcues will look to qualify your users if they match every line of conditions you set. For example, the screenshot below. Once you publish the experience with these conditions, then it is a requirement for your user to be in a Trial plan, be a Cook, and not be an Admin. If your user does not satisfy at least 1 of the conditions above, then Appcues will automatically disqualify your user from being eligible.
'Any' Condition (OR Operator)
If you'll choose to use the 'Any' condition, the rule of thumb is that your users will only have to pass at least one (1) condition to be eligible for the content. For example, the screenshot below. When you publish the experience with these conditions, then it will only require your user to pass at least one condition so that they are eligible for the content. If your user is on a Paid plan but is still a Cook, then that will still qualify your user!
Mixing It Up (Logic Groups)
Once you're confident with the basic conditions, then you can also make use of logic groups for granular control over your targeting. The rules of thumb remain the same!
From the targeting below, the experience is looking to qualify users that have Moonwalk as their Dance Move and if they have 'Jackson' as their Last Name. Additionally, they should be in a Paid Plan or their ID must contain 'Appcues'. They only have to meet one of the two bottom conditions.
Ultimately, AND operators will look to satisfy all requirements, while OR operators will only look for at least one condition to be satisfied.
Multiple negative conditions
If you use multiple negative conditions (like “doesn’t equal” or “doesn’t contain”) combined with the OR operator in Appcues targeting, the experience will qualify users who do not meet at least one of those conditions. This means most users are likely to be included, because as long as a user fails to meet a single negative condition, they will qualify for the experience.
For example, if you have conditions like “NPS score doesn’t equal 3” OR “NPS score doesn’t equal 7,” nearly all users will match. That is because an NPS score of 2, for instance, is not equal to 3, so that user is eligible, and so on for every user unless they meet every one of the negatives at the same time.
This is usually not the intended behavior.
If you want to make sure that your content does not display to users who match any of several unwanted criteria, you should use AND instead. Using AND ensures that only users who do not meet any of the unwanted conditions qualify (in other words, they must not meet all the negatives simultaneously to qualify).
