User Targeting Overview (Settings Page)
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:
- Display Targeting: URLs, Domains, Frequency
- Audience Targeting: User Properties, Events
- A/B Test Targeting: split users into two groups
- Flow Completion Targeting: what happens after the flow is completed
This information is also available in video form in the user targeting webinar.
This section dictates where your flow will appear when it's published.
Which page should we show this flow on?
To display your flow at any URL within your platform where Appcues is installed.
At a specific path
Use this targeting to display your flow at one, or multiple specific URL paths. A path is anything after the ".com" (or ".xyz", etc.). Lets take this exact URL for example, since its pretty simple in structure.
To target a flow to only this page you'd enter this:
Publishing to Dynamic URLs
For many applications, page addresses (URLs) will contain account- or user-specific information - maybe the account ID, or 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.
These are dynamic URLs. They look identical except for a unique string of numbers at the end of the address based on who is logged into your application.
- Create your flow at one version of your dynamic URL (ex: http://yourapp.com/dashboard/23944-3)
Just note, these URLs must appear the same for your end users: if certain page elements are missing from some versions of this URL, your flow may not appear.
- In the Settings step of your flow, target and publish the flow to URLs that contain stable keywords:
In the *rare* case that your URL does not contain stable keywords publish the flow to all versions of this URL by using a regular expression (regex):
While using “contains” is good for basic keyword matching, you may require more advanced targeting. For instance, what if you wanted to only target /dashboard/2392/view but not /dashboard/2392/? Matching URLs that contain /dashboard would result in too many matches.
When this is the case, we can use Regular Expression matching. Regular Expressions (or "regex") are a simple way of representing strings in a URL by patterns in its characters. For more on using regex, refer to this doc.
On which environments?
Everywhere my Appcues embed script is installed
Will show flows on any domains you've installed Appcues. This is helpful for customers who installed Appcues on multiple domains (ex. beta, staging, and production environments). Selecting this option will show flows across all these domains
Only the domains I choose
And how often?
Show the flow one time to those who meet your 'Audience' and page targeting. The flow will not relaunch to the same person, even if the flow has been unpublished, edited, and republished again.
ProTip: If you need to display a "show once" flow again (including those that have already seen it), clone the flow from the dashboard. The cloned flow will look identical, but will not have any of the user history.
The only instances where "show once" flows reappear are when:
- It is a tooltip or hotspot flow that has multiple steps: if a user does not complete all steps, the remaining (unseen) tooltips/hotspots will launch the next time they visit the targeted URL.
- The flow targets anonymous users: anonymous users cannot be differentiated, so if the same person views your site in a new anonymous session, we cannot identify them as already having seen your flow
- If the flow is being viewed via permalink: permalinks override targeting, and will launch a specific flow each time they are clicked.
Show Every Time
This will launch the flow every time someone meets the targeting criteria (determined by your other display or audience settings).
ProTip: Use this option in conjunction with the "Show only to my team" setting (see "Audience" section below) to create a testing environment for a flow.
The flow will only show when it is triggered manually, and not when someone reaches a URL and meets the 'Audience' targeting. Some examples of where this can come in handy:
- When you'd like a flow to only launch from the widget.
- When building a choose your own adventure style flow.
- When launching a flow via permalink.
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, Events, Flow history, and Segments. These are all available by dropdown, for example:
- Show only to my team: show your flows to teammates in your Appcues account (useful for testing). A user must be logged into Appcues to see flows when this is selected.
One of Appcues' more advanced features is A/B testing. As you learn more about how your customers interact with your flows, you can use A/B testing to learn even more!
The best way to utilize this feature is to compare how one flow performs against another. Are you users more likely to engage with a slideout containing a gif or a static photo? Do you users like a tooltip tour, or would they prefer one modal containing all content? You can use A/B testing to learn exactly this!
How it works
Appcues will automatically assign your users into 2 different groups:
1 (Group A) or a
2 (Group B)
The property that Appcues will send over is called
_ABGroup, and the value will either be depending on which group the user was assigned. We generate this property, and whichever A/B group a user is assigned persists on his profile and will remain the same. If this sounds like jargon to you, don't fret. We geek out about analytics and are happy to help—reach out!
A/B Testing Your First Flow
You can enable A/B testing from the flow's Settings page. Scroll down until you find this section below:
Check the "Enable A/B testing" box to show the flow to a random 50% of your user base. This random bucketing is done for you, and you can also test two flows against each other by selecting Group A for your first flow and Group B for your second.
Analyzing the Results
To properly analyze the results of your A/B test, we suggest integrating Appcues with a third-party analytics system. Those systems will let you see your results in a larger context and provide reporting features designed for this kind of analysis. You can also view the results within Appcues, by comparing the Analytics page for each flow.
If you opt to view the results in your analytics tool of choice, you'll want to view all users who:
- Completed a "Flow Started" event for the flow in question.
- Were either in Group A or Group B, depending on which you want to analyze.
Most systems will let you view that segment in funnels and other types of useful business reports. Give it a try and let us know what you think!
To accurately measure the efficacy of your experiment, you'll first need to enable one of our third-party integrations and have the ability to segment users by their properties.
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 goal: saved 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 Targeting
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!