Testing Unpublished Intercept Changes

Suite
Customer Experience Strategy & Research
Product
Qualtrics
What's on this page

About the Test Intercept Section

You can test your unfinished, unpublished intercept on any website you want. This can be a great way to make sure your intercepts work the way you want before publishing changes to the live code on your website, where visitors can see.

Attention: When running a test, bookmarklets only consider targeting logic. If the bookmarklet fails for another reason (for example, repeated display prevention), it will still show that it passed. The bookmarklet also doesn’t consider custom trigger options or custom display options. When testing, the intercept will only appear and be marked as passed if the Intercept Display is On Load. Otherwise, the bookmarklet will say it has passed, but not actually show the intercept unless these trigger and display options have been met.

Running Tests from Intercepts Settings

On the Intercepts settings page, you can run tests on multiple intercepts at once. You can test both standalone intercepts and guided setups this way.

Go to Intercepts.
intercept settings testing options
intercept settings testing options
Select Intercept settings
Under Testing unpublished changes, select the intercept(s) you want to test. Select the top checkbox to select all intercepts.
Click Apply changes.
Save the bookmarklet to your bookmarks. If your browser has a bookmarks toolbar, you can do this by simply dragging the bookmarklet onto the toolbar.
Qtip: For more detailed instructions, refer to the section on Displaying the Bookmark Bar below.
In a new window or tab, open the webpage where you would like to test your intercept.
how tests appear in your website on your browser
how tests appear in your website on your browser
Click on the bookmarklet, which will run the code for that intercept on your webpage.
A window on the lower-left will let you know if any parts of the intercept failed, and if so, what part you need to fix so it’ll pass next time.
Qtip: When you run the bookmarklet on the individual intercept level, the “Any Intercept in this Zone” logic doesn’t function the same because you are loading a given intercept rather than a zone or project.

Testing Individual Intercepts

Go to the Intercepts tab.
opening an individual intercept to test it
opening an individual intercept to test it
Go to Intercepts list.
Go to Intercepts.
Open the intercept you want to test.
Go to Test Intercept.
testing bookmarklet
testing bookmarklet
Choose which Intercept Version you’d like to test. Published Version will show the latest changes you made before clicking Publish. Editing Version will show the latest changes you made, regardless if they are published.
Qtip: Though the published version can also be previewed, we recommend using the Editing Version for testing as it allows you to preview changes without having to publish them. That way you can test settings on a live intercept without changing what visitors see on your site.
Save the bookmarklet to your bookmarks. If your browser has a bookmarks toolbar, you can do this by simply dragging the bookmarklet onto the toolbar. For more detailed instructions, refer to the section on Displaying the Bookmark Bar below.
In a new window or tab, open the webpage on which you would like to test your intercept.
how tests appear on your website
how tests appear on your website
Click on the bookmarklet, which will run the code for that intercept on your webpage.
A window on the lower-left will let you know if any parts of the intercept failed, and if so, what part you need to fix so it’ll pass next time.
Qtip: When you run the bookmarklet on the individual intercept level, the “Any Intercept in this Zone” logic doesn’t function the same because you are loading a given intercept rather than a zone or project.

Qtip: These steps are written for standalone intercepts. Guided intercepts tend to have testing included in the guided setup, or if you click Preview intercept on the page shown below.

in the last page editing guided intercept, preview button in upper right
in the last page editing guided intercept, preview button in upper right

guided step that advises on how to use a bookmarkelt
guided step that advises on how to use a bookmarkelt

Displaying the Bookmark Bar

If your web browser has a bookmarks (or favorites) toolbar, saving the bookmarklet needed to preview your intercept is as simple as dragging it onto that toolbar. If you don’t have a bookmarks toolbar, the following steps will describe how to display it on your browser.

Qtip: In every browser, you can right-click to delete a bookmark once you’re finished using it.

Testing on a Mobile Browser

Saving the bookmarklet to a mobile browser is certainly possible, but a bit tricky given how mobile browsers don’t typically let you drag and drop. The best way to test how your intercept will appear and behave on mobile devices is to access the developer tools in your web browser.

Open Developer Tools on your browser.
Navigate to the Toggle Device Toolbar option.
The Toggle Device Toolbar is highlighted in the top left corner of the Developer Tools in the web browser
The Toggle Device Toolbar is highlighted in the top left corner of the Developer Tools in the web browser
Select the mobile view, or enter the dimensions you would like to test for.
In the Toggle Device Toolbar of the Developer Tools, the dropdown is selected to show all device sizes
In the Toggle Device Toolbar of the Developer Tools, the dropdown is selected to show all device sizes

Troubleshooting Tips

Intercept Logic

  • Make sure the values are correct.
  • Examine your use of “Is” vs. “Contains.”
  • Examine your use of And/Or logic.
  • Watch out for spaces in the values.

Revision History

Make sure the published version is the most recent (or the version that you would expect).

Watch For the Website Feedback Network Request

Open Developer Tools on your browser.
Look at the network request for ?Q_ZID etc.
  • No network request: The implementation is not working.
  • Network request: Check the parameters of the request for inconsistencies. Sometimes the code is implemented using a tag management system. There are cases where this implementation messes with the parameters in our request for current URL, etc.
  • Network request with an error: Check if your project is activated.

Look For Other Hanging Script Requests That Might Be Interfering With Our Script

Right-click anywhere in your browser.
Select Inspect Element.
Choose Console (this is where errors appear).
Qtip: You will also want to right-click and select View Page Source to verify that your project code is actually on the page.

Was this helpful?

The feedback you submit here is used only to help improve this page.

That's great! Thank you for your feedback!

Thank you for your feedback!