Embedded Link Creative
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 Embedded Link Creatives
The embedded link allows you to place a link on your website that will direct visitors to different destinations depending on criteria you set. This can be useful for A/B testing. For example, you could send 50% of your visitors to a different version of your page in order to determine which layout or version converts more customers. Or for promotional material, you could link visitors from certain geographic regions to special landing pages specific to those regions.
Setting Up the Embedded Link
The embedded link does not have the editing options that most creatives have. Instead, most of the setup actually happens in the Intercept tab, when you use the intercept to decide where the embedded link should take visitors, and when.
To Implement an Embedded Link
Type the text you would like displayed for your link.
Select Publish.
Navigate to the Intercepts tab.
Create an intercept or navigate to an existing intercept.
Under “Select a Creative to show,” choose your embedded link creative.
Specify the target survey or website.
Click Change/Add Logic to determine the conditions under which your creative leads to this target.
Qtip: To add additional action sets (conditions under which the embedded link goes to different webpages), see our page on Action Sets.
Have your web team designate space on your website where your embedded link will be inserted. This space should include an HTML element with an ID attribute. Identify and copy the HTML ID between the quotation marks as shown below.
In many cases, an HTML tag with an ID already exists in the proper location, and no site modifications are needed.
Qtip: Use your browser’s Inspect Element function to determine the HTML ID of an element. In most browsers, simply right-click on the portion of the page you would like to inspect, and select Inspect Element.
Make sure you have your intercept open in the Intercepts tab.
In the Options menu of your intercept’s action, select Advanced Options.
Qtip: If you’re curious, see our page on Action Set Advanced Options for a deeper explanation of each of these options!
Paste the HTML ID of your target container into the Creative Insertion Point field.
Attention: If you have multiple action sets, be sure to do step 11 and 12 for each action set!
Click Save.
Publish your intercept.
If you haven’t already, click Activate.
When a visitor comes to this page on your website, Website Feedback will find the target container with the HTML ID you specified and insert the creative there.
Qtip: Your webpage’s CSS determines the style/design of your link. Generally, the link will have the same style as the page it’s placed on.
FAQs
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.
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?
There is a tool called a bookmarklet that allows you to test any intercept without having to activate it.
That's great! Thank you for your feedback!
Thank you for your feedback!