Other Conditions
Suite
Customer Experience
Strategy & Research
Product
Qualtrics
What's on this page
Qtip: If you don’t have access to any of the features described on this page, reach out to your Account Executive. For more information about the differences between Digital Feedback and CustomerXM for Digital, see Digital Feedback vs. CustomerXM for Digital.
About Other Conditions
In the previous support pages, we showed how you can use intercepts to set the conditions under which your creatives appear to site visitors. In this section, you will learn about how to base intercept logic off of the action itself, Qualtrics surveys, and whether other intercepts have been displayed.
This Action
This Action is used to determine whether a creative should be shown, based on whether or not it has been shown in the past.
Qtip: To prevent repeated display at the intercept targeting-level rather than on each individual action, or for more control over the length of time repeated display should be prevented, consider using the Prevent Repeated Display option under Intercept Options.
To set a This Action condition
On either the intercept targeting-level or the action set-level, add logic.
Drop the first field down and select This Action.
Select whether you would like to target visitors for whom the action Has Not Been Taken (they haven’t seen the creative), or those for whom the action Has Been Taken (they have seen the creative).
Indicate whether the time frame for this condition is During the browsing session, or Ever.
Qualtrics Survey
If your intercept is linked to a Qualtrics Survey, then you can base logic off whether the visitor has taken the survey or not.
To set a Qualtrics survey condition
On either the intercept targeting-level or the action set-level, add logic.
Drop the first field down and select Qualtrics Survey.
Select the desired survey.
Select whether this logic is based on whether the survey Has Been Taken or Has Not Been Taken.
Qtip: Survey Has Been Taken and Has Not Been Taken logic relies on the QST cookie, which will not work with vanity URLs.
Intercept Logic
Intercept logic can display your creative based on whether another intercept in your project has been displayed or not displayed in a given time frame. For example, you could choose to only target visitors who have not seen another intercept on your site in the past day.
Qtip: Prevent Repeated Display depends on first party cookies that are placed on the end user’s browser on your behalf. However, if the end user has any mechanism that clears cookies regularly (such as an internal organizational policy), then Prevent Repeated Display will not work.
To set an Intercept condition
On either the intercept targeting-level or the action-level, add logic.
Drop the first field down and select Intercept.
Select whether you’re basing logic off any Intercept, no Intercept, or a specific Intercept you’ve created.
Qtip: There are many different reasons to implement Intercept logic. Here are some examples:
- You want to display the same intercepts on each page of the website but may not want to distract or show the visitor the intercept each time they navigate to a new section in your website.
- You have different intercepts on the website tied to different surveys. The conditions for the intercepts could be the same so people could technically see both, but you don’t want them to take both surveys. To avoid that, you can add a condition that checks to make sure Intercept A hasn’t been seen in 8 days before displaying it again, or you could set a condition that checks to make sure Intercept A hasn’t been seen in 8 days before displaying Intercept B.
Select whether the Intercept Has Been Seen or Has Not Been Seen.
Qtip: Any Intercept and No Intercept only have the Has Been Seen option.
Enter the value of the timeframe.
Enter whether this timeframe is in Days, Hours, or Minutes.
Frustration Targeting Logic
Qtip: The options described in this section are only part of licenses that include Digital Experience Analytics. If you’re interested in this feature, please reach out to your Account Executive.
You can use logic to display intercepts when visitors show common frustration behaviors on your website. This lets you connect with your customers when they most need your help, so you can better understand website issues and route them to the right teams.
Example: When visitors show a certain combination of frustration behaviors, you show them a responsive dialog asking for feedback. Or, for a more passive approach, you can make a help button appear on the side of the page.
Example: Use frustration signals to route customers to the correct teams. For example, frustrations encountered on your larger website could route the customer to support, while frustration behaviors on a sales-specific page could divert the customer to Sales. (To alert specific teams, your target survey could use workflows to generate an email or a ticket.)
Make sure you have session replay enabled and set up to your liking.
Qtip: Frustration targeting only works on pages where Digital Experience Analytics is active. In addition to this, a session that is not sampled cannot use frustration targeting logic. Learn more about sampling and page groups.
If you’re using an individual intercept, add logic to the entire target or to an individual action set.
Click the first menu and hover over Frustration Signals.
Choose from the following:
Define how many frustration signals should occur in a session before the intercept triggers. Determine if the number you choose is:
- Equal to
- Not Equal to
- Greater Than
- Greater Than or Equal To
- Less Than
- Less Than or Equal to Example: Trigger the intercept if there are 5 or more mouse thrashes.
Make sure you save your changes.
Qtip: You can add more conditions as needed. For more details, see Advanced Action Set Logic.
FAQs
When should I use logic on my action sets?
When should I use logic on my action sets?
Action set logic is used to determine when you want to display the Intercept. It can be helpful for when you have multiple action sets with different conditions for displaying.
For example, since creatives are not responsive to screen size, many users like to implement action set logic focused on whether a website viewer is/is not using a mobile device or whether the website is being displayed on a certain screen size. By using logic in this instance, you are able to target a properly formatted and sized creative to the appropriate person.
Action set logic based on location can even be used to make sure that website viewers are seeing a creative that is written in the language that most likely applies to them.
For example, since creatives are not responsive to screen size, many users like to implement action set logic focused on whether a website viewer is/is not using a mobile device or whether the website is being displayed on a certain screen size. By using logic in this instance, you are able to target a properly formatted and sized creative to the appropriate person.
Action set logic based on location can even be used to make sure that website viewers are seeing a creative that is written in the language that most likely applies to them.
I activated my intercept, but it‘s not showing up on my site. Why not?
I activated my intercept, but it‘s not showing up on my site. Why not?
There are numerous potential causes as to why an intercept may not be appearing once it has been implemented. These causes may stem from the setup of the intercept itself or the implementation of the code.
- Logic: intercept targeting logic and action set logic are the conditions that must be met in order for an intercept to be displayed to a visitor. Checking this logic will be helpful in discovering why the Intercept is not displaying on a page.
- Logic sets that use “Contains”: A common cause of logic error is the use of the “Contains” vs. “Is.” To say a condition “Contains” means that the parameter you are basing the logic off (i.e., Current URL) will have the specified value present in addition to more information. For example, if I had logic that read as Current URL contains ‘qualtrics’, this would cause the intercept to display on any URL that has the word qualtrics present. The other option you have is using Current URL is [URL]. This condition depends on the visited URL being an exact match. Any differences or additional characters will prevent the intercept logic from passing.
- Intercept Revisions: When making edits to intercepts, changes are not made live until the intercept is published. When publishing an Intercept, a version of the intercept, or a “revision,” is saved. Reviewing the revisions that have been made is very useful for identifying any changes that may have suddenly prevented the intercept from appearing.
- Debug Window: The debug window is an invaluable tool for testing why an intercept is not displaying on a particular page.
For intercepts whose deployment code was implemented before March 2019, to enable the debug window, append a query string to any given URL called Q_DEBUG. This must be prefixed with a ? or a & like the following examples: https://www.qualtrics.com?Q_DEBUG, https://www.qualtrics.com/blog?item=value&Q_DEBUG.
For intercepts whose deployment code was implemented after March 2019, run the following JavaScript snippet in the Console of your web page:
QSI.API.unload();
QSI.isDebug = true;
QSI.API.load();
QSI.API.run();Qtip: The Website Insights debugger does not function if the code has been implemented using a tag manager. Also, if the URL already has a query string with a ?, then the debugger will require a & instead.
- Network Request: Most browsers possess a developer tools menu that allows a user to see a site’s source code, resources, cookies, and network calls. Website Insights possesses a distinct presence in the Network section of these tools. To check for these scripts running, open the developer tools and navigate to the Network section. Once here, reload the webpage and the menu should begin to populate with all network requests being made by the website. To identify Website Insights code, look for calls that begin with ?Q_ZID or ?Q_SID. This is the code itself running checks on the display logic. If you cannot find anything matching this format, then there is an issue with the implementation of your project code. You can refer to our support page on implementation for advice on where is best to place the code.
- Content Security Policy Issues: If you receive a console log that violates a Content Security Policy, there is most likely a restriction on your website that is blocking our intercepts from deploying. We recommend reaching out to your web-development team to resolve. To ensure your intercepts work, we generally recommend allowlisting the following items in your Content Security Policy headers:
- connect-src https://*.qualtrics.com
- frame-src https://*.qualtrics.com
- img-src https://siteintercept.qualtrics.com
- script-src https://*.qualtrics.com
- SPA URL Handling: If your site uses a single-page application (SPA) framework, make sure your code triggers history.pushState() when navigating between views. Some frameworks may re-render or update the URL without pushing a new history entry, which can prevent intercepts from firing. If you're using useEffect or similar lifecycle hooks, make sure your intercept logic runs after navigation is complete.
What should I be basing frustration targeting logic on?
What should I be basing frustration targeting logic on?
What you base frustration targeting logic on can be very specific to your website and even to individual pages on your site. If you don’t have existing data to help decide, try running Digital Experience Analytics and reading the results to understand which frustration triggers are happening on your pages.
If I sample with Digital Experience Analytics, will that affect who sees intercepts with frustration targeting logic?
If I sample with Digital Experience Analytics, will that affect who sees intercepts with frustration targeting logic?
Yes. Frustration targeting only works on pages where Digital Experience Analytics is active. In addition to this, a session that is not sampled cannot use frustration targeting logic. Learn more about sampling and page groups.
That's great! Thank you for your feedback!
Thank you for your feedback!