Each survey in Medallia Digital provides targeting options that control how the survey functions as part of the app. Surveys are assigned a trigger, which determines the options available for targeting, such as 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.

The targeting options available are determined by the type of trigger currently assigned to the survey, seen at the bottom right corner of the survey targeting options.

When you change the trigger type, any current targeting settings and translations are deleted. To avoid losing data, the Switch trigger mode dialog opens.

Important: Only click OK if you are sure you can lose the existing settings. Alternatively, create a duplicate survey and change its trigger type.

Targeting

Apps that use Digital Mobile SDK take advantage of Digital’s targeting capabilities to choose the evaluation criteria which trigger surveys or invitations to provide feedback. Targeting lets you know exactly who your users are, and when and how to reach them. Important to understanding targeting is in the concept of a session, which is refreshed as a user navigates an app.

To set up the survey in Digital Command Center:

1. Create and design a survey form.
2. Choose a type of trigger.
3. Set targeting Invitation options and customize invitation design.
4. Publish the survey by switching on the toggle.

The following options are available for in-app targeting:

• Target users based on in-app behavior, custom parameters and session parameters
• Segment by metadata such as OS and app version
• Suppress targeting so that your users are not interrupted during critical flows

Out of the box Targeting Rules

The following rules can be set directly from Command Center with no additional coding

• Sampling rate
• Number of app sessions
• Time in session
• App version
• OS version
• Quarantine rules
  • Time since user has last declined an invitation to provide feedback
  • Time since user last submitted feedback
• Any custom logic (based on dynamic rule engine, using custom parameters collected in real-time from the app)

Examples include: New or tenured customer, specific page or pathway taken in-app, etc.

The options available for targeting depend on the type of trigger being used. See Trigger types for more information.

Advanced Targeting Input

Some fields allow you to add custom values to be able to tailor the targeting engine capabilities to your specific business logic, such as App Version and OS Version.

• Any numeric value can be used

• By using commas with no spaces between them to enter multiple values:

  3.1,3.2

  

RegEx format is also supported. This allows you to be able to target a range, or a logic of targeting below or above a specific value.

For example, the expression below targets any app version from 1.1.1 to 3.6.1.

[1.3]\.[1-6]\.[1]

Custom Rules

Form Invitations can be targeted by Custom Parameter rules. Once configured, these rules are added as another standard rule available for your app to target by.