Loading...
  • Customer Experience
    Customer Experience
  • Employee Experience
    Employee Experience
  • Brand Experience
    Brand Experience
  • Product Experience
    Product Experience
  • Core XM
    Core XM
  • Design XM
    Design XM

Website / App Feedback Browser Cookies

What's on This Page:


Was this helpful?


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

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!


About Website / App Feedback Browser Cookies

Website / App Feedback stores certain data inside cookies. This includes the Site History cookie, Prevent Repeated Display cookie, a cookie that tells us that we have a Pop Under, a cookie that stores history data if localStorage is disabled, and a cookie that tracks user events.

Cookie Limit

Except for when action set logic is based off of Site History or Page Count, all cookies are within 100 bytes. The total size of the cookies listed on this page can be controlled by the Maximum Cookie Size, found under the Organization Settings tab of the Admin page. This is a brand-wide setting and cannot be limited to singular accounts or projects.

Site History and Page Count

For Site History or Page Count, you can choose between storing information as cookies or as session storage instead. This is a setting that applies to an entire Website Feedback project.

Once you choose a storage method, you can then set the maximum storage size (in bytes) on either a project-level or on the brand-level (if you are a Brand Admin). If they are set, project-level settings override brand-level settings. If you do not want to keep track of the user’s site history in the browser, you can set the maximum storage size to “1”; the cookie or session storage key will still be created, but it will stay empty as the user navigates through the site.

Cookie Domain

You can specify where the Site History cookie will be stored by setting a Cookie Domain. This can be useful for websites with multiple subdomains (i.e., 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.

Example: Setting the Cookie Domain to shop.siteintercept.com would track Prevent Repeated Display independently from about.siteintercept.com. If you would like to specify that this cookie be saved site-wide, or if you would like it saved on a specific subdomain, you can specify the Cookie Domain. For example, we could set a Cookie Domain of siteintercept.com to ensure Prevent Repeated Display is applied site-wide rather than being specific to a subdomain like shop.siteintercept.com or about.siteintercept.com.

Hide Intercept When Cookies or Local Storage are Disabled

There is an option on the Intercept’s Change Options section that prevents Intercepts from running in browsers that have cookies disabled. By default, the option is enabled.

List of Cookies

Qtip: All the cookies listed on this page are first-party cookies. That means they will have the domain marked as your website domain (e.g., the website on which the intercept is shown). Any restrictions that apply to third party cookies do not affect these first party cookies. The exception is the survey completion cookie (that is also used for purposes of preventing multiple responses), which is a third party cookie. This cookie is always marked as Secure; SameSite=None in order to comply with common third party cookie restrictions.

Site History Session

    • Key: n/a
    • Expiry: n/a
    • Purpose: This cookie tracks the Urls of the web pages that the user visited. The pages should have the project deployment code for tracking to work. This cookie can grow up to 2000 bytes, unless Maximum Cookie Size is set.
Attention: By default, the Site History Session cookie is not employed. For more information about storing visit history, read the Browser Storage section of our Deployment Section page.

Sampling

  • Key: QSI_S_{ZoneID}
  • Expiry: Persistent, 1 week
  • Purpose: The cookie name is QSI_S_{ZoneID} and the value is “{v|r}:{1}:{2},” where “v” means visitor sampling, “r” means request sampling, variable 1 is the percentage (for the individual visitor), and variable 2 is the number of times the visitor has visited the site.
    Example: {v:0:0} means they are using visitor sampling, and I was sampled out. {v:100:0} means they are using visitor sampling, and I was sampled in. {r:10:45} means they are using request sampling, 10% of requests should be sampled, and I’m on my 45th request. Based on this scenario, I should be sampled in on my first visit and every 10th visit thereafter.

Prevent Repeated Display

  • Key: QSI_SI_<id>_intercept
  • Expiry: Persistent. Expires based on Intercept settings.
  • Purpose: This cookie is used to track whether we should display the Intercept on repeated user visits. It is formatted as QSI_SI_<id>_intercept (e.g., QSI_SI_5sPQdCDYYVYwQRv_intercept).

Popunder Target Session

  • Key: QSIPopUnder_PopUnderTarget_SI_<id>
  • Expiry: n/a
  • Purpose: This prevents multiple windows from crowding a client by checking if other Pop Unders are being displayed already, and preventing repeated display. This cookie has the format QSIPopUnder_PopUnderTarget_SI_<id>
    Example:
    QSIPopUnder_PopUnderTarget_SI_1Y2DkewovNRaQRv

Other

  • Key: n/a
  • Expiry: Length of the browser session
  • Purpose: If local storage is disabled, we store some other values in cookies.

Cloudflare

  • Key: __cfduid
  • Expiry: Persistent, 30 days.
  • Purpose: This helps Cloudflare detect and mitigate the impact of visitors to our website. This cookie is a security feature.
Qtip: Additionally, the Survey Platform will add a persistent cookie (QST) that is used for purposes of preventing multiple responses. Website / App Feedback also uses this cookie to evaluate Qualtrics Survey logic in action sets.

List of Local Storage

Intercept Targeting

  • Key: Q_INTER
  • Purpose: This value contains the unix timestamp of all Intercept Impressions made on the domain. We use these timestamps to decide whether or not to show another Intercept when evaluating Intercept targeting logic. The value is a JSON object with an Siid as the key and timestamp as the value.

List of Session Storage

Site Exit PopUnder Embedded Data update

  • Key: QSI_OptInIDsAndWindowNames
  • Purpose: This value contains the Intercept ID mapped to any Pop Under opened by said Intercept. This is then used to update the Pop Under with updated Embedded Data upon navigation (unload).

FAQs