Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Web Experiences
  • Targeting

Targeting Logic (All vs Any)

Learn when to use All or Any when creating targeting logic for your experiences.

Written by Sofia Domingues

Updated at May 14th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Installation & Developers
    Installing Appcues Web Installing Appcues Mobile API & Data Troubleshooting Extras
  • Installation & Developers
    Installing Appcues Web Installing Appcues Mobile API & Data Troubleshooting Extras
  • Web Experiences
    Building Web Experiences Targeting Studio Customization & Styling Use Cases Troubleshooting FAQ
  • Mobile Experiences
    Installation & Overview Building Mobile Experiences Mobile Analytics & Integrations Troubleshooting
  • Workflows
    Building & Configuration Use Cases Workflow Analytics and Integrations
  • Account Management
    Subscription Users & Data
  • Analytics
    Experience and Event Analytics Data
  • Best Practices
    Best Practices Use Cases Pro Tips Product-led Growth
  • Integrations
    Integration Documents Use Cases Extras
+ More
  • Home

  • Installation & Developers

    • Installation & Developers

      • Web Experiences

        • Mobile Experiences

          • Workflows

            • Account Management

              • Analytics

                • Best Practices

                  • Integrations

                    Once you've envisioned how to target your flows, it's worth double-checking that your targeting logic is correct.

                    It can sometimes be confusing as to when to use the conditions 'All' and 'Any' when setting up the logic but hopefully, this article will give some clarity!

                     

                    'All' Condition (AND Operator)

                    When setting your conditions up to target based on 'All' conditions qualifying, 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:

                    Once you publish the flow with these conditions, then it is a requirement for your user to be in a Trial plan, be a Cook, and be Funky! 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 flow. For example:

                    When you publish the flow with these conditions, then it will only require your user to pass at least one condition so that they are eligible for the flow. 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 above, the flow is looking to qualify users that are in a Paid plan, or if their ID contains 'Appcues'. However, a logic group is also added to qualify users that have Moonwalk as their dance move and if they have 'Jackson' as their last name.

                    Ultimately, AND operators will look to satisfy all requirements, while OR operators will only look for at least one condition to be satisfied.

                    Note: When using negative conditions like "doesn't equal" or "doesn't contain", it's good to keep in mind that if this is combined with other conditions using the OR operator, then it will likely qualify most of your users since not having a certain value for at least one condition will automatically qualify them. For instance, the page targeting example below:

                     

                    Let's say we're on a page that contains 'dashboard'; 'dashboard' doesn't contain 'login', right? Therefore, because we meet at least one of the conditions, the flow will show on that page. The correct way to make sure that the flow won't show on all of those pages is to use AND.

                     

                    Was this article helpful?

                    Yes
                    No
                    Give feedback about this article

                    Related Articles

                    • Targeting Flows
                    • Targeting by User Property
                    • Segments
                    • Event Triggering
                    • Targeting Use Cases and Corner Cases
                    DON'T TAKE OUR WORD FOR IT

                    Start building with Appcues for free

                    Try before you buy
                    No credit card required
                    Support included
                    Start building for freeBook a demo
                    or take an interactive tour
                    Appcues logo

                    Product

                    In-app messaging
                    Email
                    Push notifications
                    Workflows
                    Data
                    How it works
                    Pricing
                    What's new

                    Use cases

                    Onboarding
                    Free-trial conversion
                    Feature adoption
                    Feedback
                    Support

                    Integrations

                    Why connect
                    All integrations
                    All workflows

                    Company

                    About
                    Careers
                    HIRING
                    Why Appcues
                    Teams
                    Customers

                    Support

                    Request a demo
                    Start free trial
                    Developer Docs
                    Help Center
                    Customer Success
                    Contact

                    Resources

                    Product Adoption Academy
                    Courses
                    Workshops
                    Templates
                    Examples
                    Made with Appcues
                    The Appcues Blog
                    PLG Collective
                    Product-led Experience Report
                    The Product Experience Playbook
                    The Product-Led Growth Flywheel
                    © 2025 Appcues. All rights reserved.
                    SecurityTerms of ServiceWebsite Terms of UsePrivacy PolicyCookie Preferences
                    Expand