Intercepts Section

About the Intercepts Section

When you’re ready to test or adjust the project settings of your Website Insights project, head to the Intercepts section of the Settings tab.

Testing Unpublished Changes

When building an intercept, you can navigate to the Testing unpublished changes section to preview what your intercept will look like on any website you desire. This 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.

1. Once inside the Testing unpublished changes section, select the checkbox(es) next to the name of the intercept(s) you want to test. Select the top checkbox to select all intercepts.
2. 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.
3. In a new window or tab, open the webpage on which you would like to test your intercept.
   
4. Click on the bookmarklet, which will run the code for that intercept on your webpage.
5. 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.

For more information on testing intercepts, see Test Intercept Section.

Approval Process

Approval requirements can be used to ensure only quality content is published to your website. With the approval system, you can specify individual users or groups of users who must be given permission for a creative or intercept to be published.

ADDING APPROVAL REQUIREMENTS

In this section, learn how to make it so that users must be granted approval before their changes are published.

1. Make sure you are in the Settings tab of your project.
   
2. Click on the Intercepts section.
3. Navigate to Intercept Approvals or Creative Approvals.
4. Click Add Approver.
5. If set to User Type, you can decide how many users of the selected type must approve an intercept or creative before it can be published.
   Qtip: Regardless of who the user is, the system will still explicitly require an approval. For example, let’s say you are a Brand Administrator. If you have configured an intercept to require an approval from one Brand Administrator user, you will still need to explicitly approve your own request to publish.
6. Select whether you want to require approval by a User or User Type.
7. If set to User, select the user who must approve an intercept or creative before it can be published. If set to User Type, select a user type.
   Example: In the above image, creatives and intercepts need the approval of a Brand Administrator and the Qualtrics Demo user.
8. Click the plus (+) sign to add additional approval requirements to the same feature.

APPROVEE PROCESS

When a user goes to publish new content, they will see a Request Approval to Publish button instead of a Publish button.

After clicking this, the user will have to select an individual or group from your list to approve their change. That person will receive an email with the opportunity to either approve or reject the changes.

The same is true for guided intercepts, such as the responsive dialog, embedded feedback, and feedback button. At the end of guided creation, you’ll see a Request Approval button and be able to pick who you’d like to review your intercept.

You can also choose to cancel your current request for approval and resend a new one if you find you’d like to make more changes.

APPROVER PROCESS

If you are one of the users being asked to approve an intercept or creative, you will receive a notification email. Upon logging in, you will see all pending approvals at the top of your Homepage.

Click View to take a look at the list of creatives or intercepts awaiting approval.

Click Review next to an intercept or creative to view it.

You may decide to Send Request Back to reject it or Approve Request to allow it to be published.

Click the dropdown next to Request for Approval for additional options.

• If you select Approve, you will be asked if you’re sure. Click Approve Request on the next window to publish the changes.
  
• If you select Send Back, the changes will not be published. You will be able to submit a comment explaining to the user why you did not approve so they know what edits to add next time.
  

Notification Emails

In addition to requiring approvals, you can enter email addresses in the Notification emails area if you wish for yourself or others to receive a notification when creatives or intercepts are published or activated.

Single-page Application Support

If you’re using an intercept on a Single Page App, you can turn on a setting to check the display logic each time the URL changes, even if the entire page doesn’t reload. Select Re-evaluate intercept logic when the URL changes to enable this.

Intercept Loading Options

This option allows you to load the entire project using JavaScript code. Despite the project being active, intercepts will not begin evaluating logic, nor will any creatives display, until the project code is loaded manually with the JavaScript code, QSI.API.run().

Browser Storage

In the Browser Storage area you can configure browser storage settings to enable intercept conditions.

• Cookie domain: Specify where the cookie that records the visitor’s site history will be stored. This can be useful for websites with multiple subdomains (e.g., shop.siteintercept.com and about.siteintercept.com). By default, cookies are saved independently for each subdomain so that each would have its own Site History, Time On Site, and Page Count. You can only add 1 cookie domain at a time.
  Example: Setting the cookie domain to siteintercept.com would ensure just one cookie is used for the entire website.
• Page visit history storage: This refers to how visit history is stored. This will only be used if site history or page count targeting criteria is used in intercepts.
  Qtip: For older projects, the default is Use cookies. For all projects made after May 7, 2019, the default is Use session storage.
  • Use cookies: Browsing session history and page count are stored as a cookie on the browser.
  • Use session storage: Browsing session history and page count are stored in that particular browsing session.
• Max storage: In bytes, the maximum storage size you’d like the information to take up on a session or cookie.
  Attention: The organization-level limit overrides the limit set at the project level.