Date Time 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 Date Time Conditions
With Date/Time conditions, you can set your intercepts to automatically run at specific times, saving you the hassle of manually activating and deactivating them. For example, for a holiday promotion, you could set the intercept to run between December 12 and December 26.
Date
With a Date condition, you can set specific dates for when your creatives will show. For a project with a specific start and end date, two Date logic statements are used in conjunction.
To Create a Date Condition
On either the intercept targeting-level or the action set-level, add logic.
Drop the first field down.
Select Date Time, and then select Date.
Select whether you want the Intercept to run on, after, before, or not on that date at all.
Click on the date text box to select a date from the calendar.
Optionally, you can specify the time zone by checking Select Time Zone. If no time zone is selected, logic will run based off of the visitor’s time zone.
Example: In this action, two Date statements are used to specify that the creative will only show between November 30 and January 1 for a holiday promotion.
Day
With a Day condition, you can set your intercept to run just on specific days of the week. For instance, you might set up a weekend promotion that automatically shows creatives on the weekends so that you don’t have to activate and deactivate the intercept manually every week.
To Create a Day Condition
On either the intercept targeting-level or the action set-level, add logic.
Drop the first field down.
Select Date Time, and then select Day.
With the Is and Is Not options, specify whether you would like to target visitors on that day of the week or to exclude that day of the week.
Select the day of the week you would like to target.
Optionally, select the Time Zone to be used for the logic evaluation. If no time zone is selected, logic will run based off of the visitor’s time zone.
Time
The Time condition is appropriate when you want to pinpoint a specific time of day for your creatives to show. For a project with a specific start and end time, two Time logic statements are used in conjunction.
To Create a Time Condition
On either the intercept targeting-level or the action set-level, add logic.
Drop the first field down.
Select Date Time, and then select Time.
With the Is Before or Is After options, specify whether you would like to target visitors before or after the time you will specify.
Input a time in HH:MM 24-hour format.
Optionally, select the Time Zone to be used for the logic evaluation.
Qtip: If no time zone is selected, logic will run based off of the visitor’s time zone.
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.
That's great! Thank you for your feedback!
Thank you for your feedback!