Activating, Publishing, & Managing Intercepts
What's on this page
About Activating, Publishing, & Managing Intercepts
At the top of every section when you edit an intercept are 2 buttons: Publish and Manage.
Any changes to your intercepts won’t go live until you are ready. There are 2 key components that make this possible: publishing and activating. When you publish a creative or intercept, the latest changes you have made can go live on your website. When you activate an intercept, this turns the intercept on so it is live on your website.
You will separately publish creatives and intercepts after every set of changes you make, however, you will only activate intercepts once.
Publish Intercept
Qtip: If you have the published version of the project deployment code on your website, both the creative you are implementing and the intercept that runs it will need to be published before visitors will see your changes.
Qtip: If your organization has implemented an approval system, you may instead see a button that says Request Approval to Publish. For more information about setting up an approval system for projects, check out our Website / App Insights Administration support page.
Activate Intercept
Publishing a creative and intercept simply means your latest changes can go live on your website. You must Activate an intercept before the code will work at all. From there, you can turn off the code at any time by Deactivating the intercept.
To activate an intercept, simply click Activate on the top-right of the Edit section. This button is only available once the intercept has been published for the first time.
To deactivate an active intercept, simply click Deactivate on the top-right of the Edit section. This button is only available once the intercept has already been activated.
Qtip: Want your intercept to stop running, but don’t have the time or resources to remove the code from your site? Deactivating the intercept shuts it off so that you don’t have to worry about this.
Manage Intercept
On the top-right of the intercept editor you will find the Manage dropdown menu.
Revisions
View the Revision History of your intercept. Here, you can tell when a revision was made and what user made it.
Click on the version you’re currently editing for the option to Save a new revision.
Click on an older version to Revert to this revision. This will replace the version you’re editing with this older revision.
You can always go back in your Revision History to restore any previously saved revision, including ones created after the revision you are restoring.
Save
Manually save any changes you’ve made to your intercept. Note that changes are saved automatically every few seconds, so this option is not typically necessary.
Rename
Give your intercept a new name.
Create Duplicate
Create a copy of your intercept within the same project.
Event Tracking
With event tracking, you can keep track of actions your visitors take on your website, such as downloading a monthly statement on a banking website, clicking to chat with a live agent on a commerce site, and more. To learn more about setting up Event Tracking, go to the linked support page.
Survey Quotas
If you are building Qualtrics surveys, you can set what are known as quotas. Quotas allow you to limit how many people come into your survey, often based on a response they’ve given (e.g., limit your survey to only 50 male and 50 female respondents).
When building your quota, you can decide what happens when that quota is met. Are new respondents sent to a different survey? Are they sent out of the survey entirely? One of your options is to activate or deactivate an intercept (not a whole project).
Example: You only want 100 responses on your feedback survey. You display this feedback survey in an intercept on your site. With the Website / App Insights quota action, you can ensure that once 100 responses are collected, the feedback survey will stop appearing in an Intercept on your site.
Attention: Website feedback actions for quotas are not available when the New Survey Taking Experience is enabled.
FAQs
When should I use logic on my action sets?
When should I use logic on my action sets?
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?
- 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.
I have built my intercept but would like to test it before activation. How can I do that?
I have built my intercept but would like to test it before activation. How can I do that?
That's great! Thank you for your feedback!
Thank you for your feedback!