Targeting Flows

To drive more impact with your flows, make sure the flow is targeted to the right people, in the right place, at the right time. User targeting for your flows starts on the settings page. From there, you can define where you want your flow to display, the audience who will see it, and what happens upon the flow's completion.

This article covers: 

This information is also available in video form in the user targeting webinar.


Intro to flow targeting


Flow triggering

This section defines what should start the flow, and how often it should be displayed.

Defining when to launch the flow

The first set of options configures when the flow should be displayed to a user who qualifies to see it.

Options
  • When the user reaches the page (default): when a user reaches the page, Appcues will evaluate whether to show them this flow.
  • When an event occurs: flow should display when a specific event is sent to Appcues, using a client-side track call.
  • Only manually: for displaying a flow based on permalink or in a Checklist. Note: This will override all other targeting (frequency, page, and audience).

Defining how often to display the flow

The frequency options control how often users who qualify for the flow will see it.

Options
  • Show once: Once the user has seen the flow, it will not show again. This is dependent on a user seeing or completing the first step of the flow, and behavior can vary slightly depending on whether the first step is a modal, slideout, tooltip, or hotspot. For more information, be sure to check out our documentation on groups and step-groups.
  • Show every time: The flow will show every time the user qualifies for the parameters you've set in Audience Targeting - even if they have seen it already.


Page targeting


Page targeting defines:

  • what pages (URLs) in your app the flow will be triggered on.
  • which environments (domains) the flow will display in (normally used for production, staging, etc.).   

Defining the path

The options for which path the content will display on.

Options

  • Any page: if Appcues is installed on the page, and other content isn't queued to show for the user, the flow will trigger.
  • At a specific path: define the path(s) you want your content to appear on.

More on paths

A path is anything after the ".com" (or ".xyz", etc.).

To target a flow to appear on a specific path, use the options in the  specific path section (like "ends with", "contains", etc.).

For a more in-depth look at page targeting, check out our documentation here

Note: this section defines on which pages a flow is eligible to be triggered. However, once a flow begins showing, it can be used to guide users across other pages not explicitly listed in the flow's page targeting. Check out our doc for how to build flows across pages.

Defining the environment

Environments in Appcues is how you handle different test and release environments (like  stagingproduction) and also multiple domains (like appcues.com and blog.appcues.com). You define this separately from the path so you can test a flow on a specific path in Staging before releasing to Production.

Options

  • Everywhere my Appcues embed script is installed: Will show this flow on all domains you've installed Appcues. This is useful if you haven't installed Appcues across multiple domains or environments, and when you want the flow to appear in all environments (like when things have gone to Production, and you still want to see it in Staging).
  • Only the domains I choose: Specify which domain(s) this flow should appear on. More on managing domains.

Publishing to Dynamic URLs

Many applications include account- or user-specific information in the URL. Examples are account ID, user ID, the ID for that folder, etc. Dynamic URLs tend to have a base structure but include a string of letters, numbers, and occasionally characters that can change frequently.

For example,  http://yourapp.com/dashboard/23944-3 is a dynamic URL. Dynamic URLs normally look identical except for that unique identifying information.

Steps for setting up dynamic URL

  1. Create your flow. The initial URL will be one instance of your dynamic URL (for example, http://yourapp.com/dashboard/23944-3)
  2. Set up your path: In the page targeting for your flow, set up the path to expect the stable part (the word "dashboard") and be flexible about the unique part (the unique identifier, in this case "23944-3").

In some cases, you may need something more advanced.

Let's say your URLs include both the account and user identifier, like https://yourapp.com/dashboard/23944-3/user/123456. Use a regex to match.

For more about using regex, refer to this doc.


Audience targeting

The audience section defines  who will see your flow.

Who should see this content?

  • All users: show this flow to all users in your platform.
  • Users in a segment (recommended): specifically target one of the segments in your account. We recommend segments because they allow you to create a more focused message, and you're able to get a sense of what messages are being sent to what segments.
  • Specific users: Narrow your audience down by User Properties, Language, Flows, Checklists, Events and Segments. These are all available by dropdown, for example:

Flow priority

Depending on your Flow settings (trigger, page targeting, and audience), it is possible for multiple Flows to qualify to be shown to a user. If that happens, Appcues shows only one of the qualified Flows per page-view. By default, the most recently published Flow will be shown. On the next page-view, Appcues will show the next most recently published Flow for which a user qualifies, and so on.   

Most of the time there is no need to change Flow priority since usually, only one Flow will qualify to be shown to a user at a time. However, if based on your Flow settings multiple Flows do qualify to be shown to a user, you can set a Flow weight to override a default priority and define the exact relative order a Flow will be shown to a user.  

The Flow you are editing is highlighted in bold in the list. Flows by default are usually prioritized with the most recently published Flow first. We have written a detailed explanation of how Flow priority is determined if you want to learn all of the details.  To override the Priority of this Flow so it is always a higher priority than other Flows (even if other Flows are published later), enter a higher value for Flow weight and publish the Flow. If you want to make sure this Flow is shown after any flows with a weight of 0, you can specify a negative weight such as -1. Weights can be any number between -100000 and 100000. Weights can also include decimals, so if you have flows with weights 1, 2 and 3, and then want to set a new flow's weight between Flows 1 and 2,  you can use 1.5. This way you do not need to change multiple Flows' weights and republish those Flows.

Changes to Flow weight do not take effect until you click the Push Changes button at the top of the page, or for a new Flow until you click Publish.  The preview table always shows how the Flow will be prioritized  as if you published it or pushed any changes.  To see the Flow priorities for all published Flows, click  View Flow Priority, and the Flow priority table will open in a new tab.

For more information see Flow Priorities


Goals

The goals section is where  you can measure the success of your flows, based on what users accomplished after seeing it.

Choose how to measure your success

  • No Goal: will only track views and completion of a flow. 
  • Choose an existing goalsaved goals will appear in a drop-down list in your flow settings. 
  • Define a new goal: create a new goal to measure.  When a goal is created from this screen, it will automatically be linked to the flow, and the goal results will appear on the flow's analytics page.  Learn more about how goals work and how to create them.


Flow completion actions

What should we do when this Flow has completed?

  • Redirect to a different page: will redirect your users to a separate URL, either inside or outside of your app
    • To redirect to a separate domain, enter the entire URL (starting with http[s]://)
    • To redirect within the same environment, enter the address after the domain (ex: if the flow is set to my.appcues.com and you'd like to redirect to the profile page, instead of my.appcues.com/profile, you can enter /profile)
  • Trigger Appcues content: will launch a separate Appcues flow. You can use this feature to link multiple flows together. 
    • Any flows you link must all be published live in order to be seen together
    • If the flow you are triggering is set to appear on a different page, you can use Redirect to a different page and Trigger Appcues content together

Curious how user properties, events and targeting work? 

In this webinar, we'll walk you through user properties and events as well as how to target them. We'll also touch on segmenting, flow targeting, and goals within the Appcues dashboard. 

Check it out below!

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.