Targeting surveys

Each survey in Medallia Digital provides targeting options that control how the survey functions as part of a website or app. Surveys are assigned a trigger, which determines the rules available to target who receives the survey. The different trigger types also have different design options. Digital surveys can be triggered in various ways, for example by an always-on feedback button, after a behavior such as an abandoned purchase, be limited to a certain percentage of visitors, depend on a cookie and so on. Multiple surveys can be published for a property, for example a survey invite targeting all visitors who viewed more than 3 pages while another survey targets only VIP visitors who have not returned after a time.

To configure targeting for a survey, click the Configure Targeting Options icon for survey in either card or list view.

Configure Targeting Options for a survey in list view.

The targeting options available are determined by the type of trigger currently assigned to the survey.

Trigger types

Use Digital triggers to configure how a property's surveys are chosen as candidates and presented by websites and apps. The type of trigger assigned to a survey determines the available targeting options.

Where you change the trigger type.

The following types of trigger are available:

  • Button trigger - commonly used for "always-on" surveys because the button is visible across a website or app, serving as a consistent channel for feedback. Therefore the targeting capabilities for buttons are fewer, you primarily specify which URL(s) the Button should be present on. You can configure the design and location of buttons.

  • Invitation trigger - commonly referred to as "intercepts" because they can intercept a user at any time in their journey. Invitation triggers have advanced targeting capabilities, with full control over who, where, and when you target each survey, and how it is displayed on different platforms such as mobile and desktop. Intercepts can collect general feedback (general intercept), and also intercept after a specific behavior (behavioral intercept), such as a transaction, search experience, cart-abandonment, and so on.

  • Embedded in page - the survey is shown directly in an HTML element within a web page or app. Use an embedded in page trigger to show a survey as an integral part of your site or app. For example on product pages to provide product specific feedback, or as a replacement for contact us forms.

  • Code trigger - an advanced option to configure a trigger after a user-action on your website or app, such as the click of a link, or a call-to-action button. Unlike a button trigger which opens out of the box on a URL, or invite triggers that intercept at a specific time and place, code triggers are more specific to the action being taken. For example to listen for a tag embedded by an application such as Adobe Launch that triggers a survey when a certain threshold is passed. See code triggers.

When you change the trigger type, any current targeting settings and translations are deleted. To avoid losing data, the Switch trigger mode dialog opens.Confirming the switch of trigger mode.
Important: Only click OK if you are sure you can lose the existing settings. Alternatively, create a duplicate survey and change its trigger type.

Depending on the type of trigger assigned to the survey, the following targeting options are available: