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
  • Targeting

Targeting Flows Use Cases

Learn some targeting use cases to define when your flows should show to your users.

Written by Ricky Perez

Updated at June 21st, 2024

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.

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

In this article, we'll cover some use cases to target flows based on Flows and on Events.

Targeting Flows based on Flows

Ordering flows to show sequentially and days apart

You may want your users to complete a set of flows in a particular order and in a timed interval. For example, let's show a "Welcome" flow first and an "Add Tasks" flow 5 days later.

In the "Add Tasks" flow, we target for the "Welcome" flow having been seen previously but not within the last 5 days:

Showing a flow x amount of times

You may want to show a flow x number of times before it stops showing. In order to do that, make sure you select 'show every time'.

Then, in that flow targeting, you'd say:

Once it shows 3 times to a user, it will stop showing.

Showing a flow every x days

You may also want to show the same flow in a cadence, say once a week. In that case, you'll want to target that flow to users who haven't seen it the last 7 days. After those 7 days, a user will then be eligible to trigger this flow again. Repeat every 7 days.

Spacing the time between showing multiple flows

It's good practice to make sure your users aren't seeing too many flows. You can set a flow to show a set number of days after another flow was shown: 

Showing a flow each time a user qualifies until they complete the flow

You can make sure a user sees a flow until they actually complete it. For example, if we have a "Demo-Enable Welcome" flow composed of 5 steps, I can set that flow's audience targeting to show to any user who has not completed it the last step:

And set the flow to "Show every time":

This way the flow will show every time until "has not been completed" is no longer true, ie. the user completed the flow.

Note: this currently only works for Hotspot and Tooltips where we track whether the flow has been completed rather than simply seen. Check the note below to learn more about this.

Targeting Flows based on Events

Showing a flow x days after an event has occurred (or more)

You may want to show a flow 3 days after an event has occurred, regardless of how long ago it happened. For this, we'll need to target the event having occurred at least 1 time in the past, but not in the last 3 days.

Showing a flow on the second week after signing up

You may want to show a flow two weeks after your users have signed up. If you’re sending an event like ‘Sign up’ you can say that it has occurred in the last 14 days, but that it hasn’t occurred in the last 7 days.

This will then show the flow only to users who signed up two weeks ago.

A few things to note... 

Modals and Slideouts are considered completed when seen, so in the UI, 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 the UI, those types of steps will show up as “has been completed”. Continuing the flow by clicking a 'next' button or dismissing the flow will mark a tooltip and hotspot as having been completed.

To learn more about different targeting scenarios, check out this article:

  • Targeting Use Cases and Corner Cases

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Targeting by User Property
  • Pass Appcues Flow Events to Fullstory to See User Interactions
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