Multiple Action Sets
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 Multiple Action Sets
Creating multiple action sets in your intercept can help you create a more dynamic web experience for your visitors. For example, maybe you want to conduct A/B testing. Maybe you have different creatives that appear under different conditions, or you want to target a particular type of visitor with your creatives. Multiple actions can help you with all these situations and more.
Creating Multiple Action Sets
Creating a New Action Set
To add an action set, click Add Another Action Set.
Qtip: To ensure that users don’t receive multiple intercepts within a short duration, use browsing session conditions or intercept logic.
Copying an Action Set
You can also create a duplicate of an existing action set. Click Options and select Copy Action Set.
Order of Action Set Evaluation
Sequential Order (Default)
By default, multiple action sets are evaluated in a sequential order, from first to last, and only one is ultimately carried out. If the website visitor does not qualify for any of the action sets, then no action set is carried out.
Example: In the screenshot above, the Intercept would look at the day the visitor came to the website on and see if it was Saturday. If it wasn’t, it’d move onto the next Action Set and see if the URL contained leather-goods.
Randomized Order
If you’d prefer that action sets were assigned to visitors at random (i.e., for A/B testing), you’ll want to select the Randomize action set option. You can find this on the Intercepts tab in the Options section.
Combining Multiple Intercepts
Instead of creating an intercept for each creative, sometimes it’s better to put multiple action sets into one intercept instead.
Even if your creatives are for unrelated tasks, combining all of them onto one intercept ensures that these creatives don’t all pop out at your visitors at once. Remember, action sets work by checking one at a time if their conditions apply; once a condition applies, the intercepts stops looking for an action set to display.
Merging Existing Intercepts
In order to merge intercepts, you have to rebuild one intercept’s logic inside another intercept.
Targeting Different Users
Within each action set you can set up different logic to target selected users. For example, you might want to target certain mobile devices or browser types used to access the webpage.
One common example of targeting is having one action set display a smaller Pop Over creative for users on mobile devices and a separate action set display a bigger Pop Over creative for users on desktops.
Alternatively, maybe you’d like to have U.S.-based users see one creative and U.K.-based users see a different creative. This can also easily be done within Multiple Action Sets.
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.
That's great! Thank you for your feedback!
Thank you for your feedback!