Page targeting defines:
- what pages (URLs) in your app the flow will display 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.
- Any page: if Appcues is installed on the page, and other content isn't queued to show for the user, the flow will display.
- 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.).
Defining the environment
Environments in Appcues is how you handle different test and release environments (like staging, production) 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.
- 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
- Create your flow. The initial URL will be one instance of your dynamic URL (for example, http://yourapp.com/dashboard/23944-3)
- 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.