Targeting conditions

Show a survey to the right people, in the right place.

Last reviewed

Targeting conditions

Use targeting conditions when a survey should appear only for the right person, in the right place, or when the current app version is ready for it.

For example, you might show a checkout survey only on checkout pages, show a beta survey only to people in a saved segment, or wait until the current app version can support a new experience.

Add a condition

Open the survey delivery settings and add a condition.

Common conditions are:

  • User is in segment: show the survey only to people in a saved segment.
  • Current page path: show the survey only on matching pages.
  • Runtime has capability: show the survey only when the current app version says it can support a feature.

You can combine conditions. The survey displays only when all of them match.

Target pages

Use Current page path when a survey belongs on one page or a small set of related pages.

Enter the path without the domain, query string, or hash:

/checkout

checkout is treated the same as /checkout. A trailing slash is ignored, so /checkout and /checkout/ match the same page.

Use * as a wildcard when part of the path can change. It matches any text in that part of the path.

/checkout/*

This matches pages like /checkout/payment and /checkout/review.

You can also put * on both sides of a word when the matching part may appear in different places:

*checkout*

This matches paths like /app/checkout/payment.

Patterns must still name something specific. * and /* are not accepted because they would match every page.

Page path rules

Page path conditions match the browser pathname only.

They do not include:

  • the domain
  • query strings like ?plan=pro
  • hash fragments like #payment

Matching is case-sensitive. %2F, spaces, and other encoded characters are matched exactly as the browser reports them.

Examples

PatternMatchesDoes not match
/checkout/checkout, /checkout//checkout/payment
/checkout/*/checkout/payment/billing/payment
*/settings/account/settings/account/settings/profile
*checkout*/app/checkout/payment/billing/payment

Use capabilities for app-version support

Use a capability condition when the page is not enough. This is helpful when some visitors may still be running an older app version, cached code, or a runtime that cannot show the survey in the right place yet.

Learn more in Capabilities.

Next steps