How to Use Response Targeting

Response Targeting allows you to target any new interactions to only display to customers that responded a specific way on a past Survey and/or Prompts (formerly Notes).

This article will detail how to use the feature. 

How To Use

Within your WHO targeting segment, this targeting option is listed as “Has Responded to Interaction”. You are able to add this rule on the following interactions: Surveys, Prompts, Love Dialog, Ratings Dialog.

Once you have selected that rule, you can then choose the specific Survey and/or Prompt response(s) you want to base your new interaction off of.

Here is a summary of how to set up the targeting for both of these interactions.

Surveys:

After you select the specific Survey you are interested in targeting from, you can then select a specific question from within that Survey and the answer choice(s) your customers have made.

It is also possible to target based on free text responses.

Prompts:

After you select the specific Prompt you are interested in targeting from, you can then target based on what specific button(s) they selected or didn’t select on the Prompt.

Targeting Multiple Applications

When you want to use the same survey or prompt across multiple applications, make sure to set up targeting properly by selecting all the apps that will display the survey or prompt. This ensures the right users see the right survey experience.

Step 1: Select your apps

From the Apps tab, choose the apps that will display the survey. In the example below, two apps are selected.

Step 2: Confirm targeting per app

Verify that each application has a clear targeting rule applied. If the app has a check mark, it will receive the survey or prompt.

Targeting across Web and Mobile SDKs

When using both the Web SDK and Mobile SDK, it's important to understand that each SDK operates independently when evaluating targeting criteria.

• No cross-SDK targeting overlap:
  Targeting is evaluated locally by each SDK, using only the data available in its own environment (e.g., browser storage for Web, local storage for Mobile).

• Example scenario:
  You cannot target a web survey to someone who previously responded to a mobile survey, and vice versa. Each SDK has no awareness of user activity on the other.

• Interaction targeting limitations:
  Even if you create a multi-target interaction across Web and Mobile, using a condition like "Has Seen Interaction" for a Mobile survey will only apply to Mobile SDK users.

This separation ensures accurate targeting within each platform but requires thoughtful configuration if you're managing feedback across both Web and Mobile experiences.