Submit Article Requests

Do you have a suggestion for an article you would like to see created?
Feel free to submit this form and add your suggestions to our document board.

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

  • Appcues Certifications & Training
  • Integration Hub
  • Contact Us
  • Docs home
  • Web Experiences
  • Targeting and Triggering

Audience Targeting

Learn more about audience targeting and how to ensure your experiences will show to the right people.

Updated at June 17th, 2025

Submit Article Requests

Do you have a suggestion for an article you would like to see created?
Feel free to submit this form and add your suggestions to our document board.

Please fill out the contact form with the details about the help content you'd like to see.

  • Installation & Developers
    Installing Appcues Web Installing Appcues Mobile API & Data Troubleshooting Extras
  • Web Experiences
    Flows Launchpads Pins Checklists Banners NPS Surveys & Forms Targeting and Triggering Customization & Styling Troubleshooting Use Cases 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 & Data
    Experience and Event Analytics Data Users & Accounts
  • Best Practices
    Best Practices Use Cases Pro Tips Product-led Growth
  • Integrations
    Integration Documents Use Cases Extras
  • System Status
    System Status & Incidents
+ More

Table of Contents

What is Audience targeting? Which users should see this experience? All users Users in a segment Specific users User property Group property Language Flow Mobile Flow Pins Banners Checklist Event Segment Emails Push notification Advanced targeting options Use multiple conditions

What is Audience targeting?

Audience targeting is used to determine to whom experiences should appear. When a user is identified, Appcues makes a check to see what particular content that user is eligible to see. If the user matches the conditions in an experience audience targeting, it means that content can be triggered for them.

Which users should see this experience?

To start off, you can decide on a general level which users should see the content:

  • All users
  • Users in a segment
  • Specific users

All users

This option means that all identified users by your Appcues installation will see the content.

Users in a segment

Segments are a way to manage groups of users for easy, repeatable targeting of your Appcues  experiences. Using the dropdown, find the segment you'd like to use to target this experience. All the users in that segment will be eligible for the content.

Alternatively, you can exclude users in a segment. For that, pick the Specific Users option, select your segment and add the condition ‘doesn’t match'. Now, your experience will target all the users except the ones in the segment.

Specific users

This option allows you to drill down on specific options to determine who should see the content. Depending on which experience you're seeing, below you'll see all the options that can be available.

User property

This options refers to auto-properties or custom properties you've sent into Appcues, specific to the end-user. They can be whatever you send Appcues, like Role, Plan Type, Created At, etc. Read more about using properties in our article Targeting by User & Group Property.

Group property

This options refers to the account-level properties you've sent into Appcues, specific to the end-user's account or wider user group. Learn more about group properties here.

Language

This options refers to the end-user's browser language -- you can create multiple versions of your experiences based on language and target them to the appropriate audience. Learn more about language targeting here.

Flow

This option refers to your Appcues Flows, so you can target experiences based on what other Flows your users have or have not seen, or have or have not completed. Learn more about Flows targeting here.

Modals and Slideouts are considered completed when seen, so in targeting menus, those types of steps will show up as “has been seen”. 

Tooltips and Hotspots are considered completed when the user has interacted with them, so in targeting menus, those types of steps will show up as “has been completed”. 

Mobile Flow

This options refers to your Appcues mobile Flows, so you can target experiences based on what other mobile Flows your users have or have not seen, completed or dismissed.

Pins

This option refers to your Appcues Pins, so you can target experiences based on what other Pins your users have or have not interacted with.

Banners

This option refers to your Appcues Banners, so you can target experiences based on what other Banners your users have or have not seen and dismissed.

Checklist

This option refers to Appcues Checklists, so you can target experiences based on certain checklists being skipped, completed, in progress (at least one checklist item has been completed) or not started.

NOTE: When targeting a checklist based on the completion of a different checklist you may see that the original completed checklist re-appear after the completion and dismissal of the latest checklist. This happens because the checklists are shown until they are actively dismissed by the user.

Event

This option refers to events that happen within your platform that you send into Appcues. You can target based on the event occurring or not. Learn more event targeting here.

 

Segment

Use a segment or exclude a segment from seeing the content. If you exclude a segment, all users will see the content except the ones in the segment.

Emails

This option refers to Emails sent via an Appcues Workflow. You can target experiences based on emails being or not delivered, opened, clicked, marked as spam, failed or skipped.

Push notification

This option refers to Push notifications sent via an Appcues Workflow. You can target experiences based push experiences being or not sent, opened, failed or skipped.

 

Advanced targeting options

You may have noticed that some filters display a ‘show options’ button. This button allows you to create further granularity in your targeting. When you click on it, you'll see additional fields to determine when the content should be shown to the user.

Zight Recording 2025-06-11 at 11.09.01 AM

Using an event as the example, on top of saying that it must have or not occurred, you can also say how many times it must have had or not occurred:

You can also say how many times it occurred or not in the last X days.

And finally, you can specify a date from which it did or not occurred, as well as how many times.

Use multiple conditions

You can add multiple conditions to an experience, and make it so the user must match all of them or simply one of them.

With the three conditions below, the experience will show to a user on Trial plan and if they are a Cook, and not an Admin. They need to satisfy ALL of these conditions simultaneously.

If it's changed to ANY instead of ALL, the user only needs to match one of the conditions for the experience to show, although it will still show if all conditions match. For example, with the below rules, the experience would show to a user on a Paid plan, even if they are a Cook and not an Admin.

For a deeper dive into using multiple conditions successfully, read our article use multiple targeting conditions.

 

 

audience targeting specific users targeting options in the last previously multiple conditions

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Segments vs. Audience Targeting
  • Targeting Flows Use Cases
  • Use Multiple Targeting Conditions (All vs Any)
  • Recommended Segments
Appcues logo

Product

Why Appcues How it works Integrations Security Pricing What's new

Use cases

Appcues Integration Hub User Onboarding Software Feature Adoption Software NPS & Surveys Announcements Insights Mobile Adoption

Company

About
Careers

Support

Developer Docs Contact

Resources

The Appcues Blog Product Adoption Academy GoodUX Case studies Webinar Series Made with Appcues Appcues University

Follow us

Facebook icon Twitter icon grey Linkedin icon Instagram icon
© 2022 Appcues. All rights reserved.
Security Terms of Service Privacy Policy

Knowledge Base Software powered by Helpjuice

Expand