Choose where your survey will be displayed. Adjust survey questions to the step of your customers' journey and select which URL condition will help you to collect the most insightful feedback.

Not done with your website or in-product survey yet?

Table of content:

  1. Adjust your survey URL

  2. How does every type of condition work?

  3. Best practices

Adjust your survey URL

By default, your survey will be displayed on all pages you have tracking code installed. Follow this guide to adjust displaying the survey only on a specific page.

1. Go to Target > Triggers > Where would you like to show the survey?

2. Select the Only certain pages option if you want to display the survey on a specific page.

3. You can see two options: Show the survey on the following pages and Don't show it on certain pages. You can apply both conditions for one survey so that it only shows on a specific group of pages, excluding some of them.

โ—๏ธBetween showing the survey on the following pages and don't show on certain pages, there is an 'AND' logical conjunction. So, your survey will show when both these conditions are matched.

๐Ÿ’ก For example, if you were selling solutions for several industries and wanted to show your survey to everyone visiting solutions.org/industry excluding those interested in security, your conditions would be:

๐Ÿ“Œ You can include or exclude pages simultaneously and set up different conditions based on different parameters, to include additional pages, click โž• Add new pages option

How does every type of condition work?

As you can see below, we have various conditions applicable to the site's URL.

  • Exact URL Match lets you show your survey only on a specific page. It's useful if you want to survey customers viewing a certain software feature or a particular product. The survey won't be displayed a survey on any page that doesn't exactly match the URL, which means when you pick the match condition for solutions.org/pricing/ the survey won't be viewed on solutions.org/pricing/free.

  • URL Starts with is for displaying surveys on pages beginning with a specific URL. This way you can, for example, target everyone checking your pricing by visiting solutions.org/pricing/ or target only users of your online app with app.solutions.org

  • URL Ends with lets you display surveys only on pages that have a URL ending with a specific string of characters. For instance, when you want to target people looking for a certain feature of your software, you can use ends with: feature so no matter how the URL changes, the survey will be displayed if it ends with a feature.

  • URL Contains is for displaying surveys on pages containing a particular string of characters. This way, you can, for example, target everyone visiting your /cart/ regardless of a product they've chosen or the page they came from.

  • URL RegEx is a condition that should be used only when you or your developer know how to use Regular Expressions properly. Regular Expressions allow people to search for certain strings of characters and pieces of information in a line of code. With Survicate you can use them to target specific sets of pages without applying a number of different rules. (Click here to learn more about RegEx conditions)

Best practices

Target the survey on specific URLs or show it with a delay

Choose to show your survey after someone has scrolled a part of your webpage when they're about to exit, or only on some of your website's subpages. Visit our targeting basic guide to learn more about available options.

Make sure only a chosen group of visitors see your survey

Define your survey audience to ensure that only visitors with specific attributes, devices, or visit frequency can respond.

Run multilingual surveys

Try our automatic translations feature to show your respondent's surveys adjusted to their browser language and increase the response rate.

๐Ÿ“ž If you have any questions or need help installing the Survicate tracking code on your website - feel free to reach out to our team via chat or email: support@survicate.com

Did this answer your question?