Set up your bannerConfigure Your ToolsForms, Surveys and Scheduling

Qualtrics

How to configure Qualtrics at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Improve the service

Overview

This guide explains how to implement different privacy configurations for Qualtrics Website / App Insights (site intercepts) and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. Qualtrics Website / App Insights intercepts (Site Intercept, QSI script) and Digital Experience Analytics. Qualtrics is a US company.

What the service does in this scope. All cookies used by Website / App Insights are first-party cookies on the website's domain. For Site History and Page Count you can choose to store the information as cookies or in session storage, as a setting for the whole project. Intercepts use cookies such as Prevent Repeated Display to track whether a user has already seen an intercept. Qualtrics advises consulting legal counsel on the consent needed for Digital Experience Analytics and documents a OneTrust integration.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskIntercepts with Site History / Page Count in session storage; no repeated-display cookie; after consent.
Configuration B — Higher riskIntercepts with cookies (Site History, Prevent Repeated Display) plus Digital Experience Analytics; after consent.

No configuration without prior consent. The intercept script evaluates browsing behaviour to trigger surveys.

Step 1 — Configure Qualtrics

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionImprove the serviceImprove the service
2Site History / Page Count storageProject optionsSession storageCookies
3Prevent Repeated DisplayIntercept settingsOffOn
4Digital Experience AnalyticsDXA projectOffOn
5LoadingConsenter script blocking; QSI.API.load after consentAfter consentAfter consent

Step 2 — Map the configuration in the Consenter Manager

Processing location. Qualtrics is a US enterprise subject to the US CLOUD Act; list the United States in addition to the data centre in your contract.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesImprove the serviceImprove the service
Tracking methodFirst party tracking (single session)First party tracking (cross-session)
IdentifierNo identifierDevice identifiers
Data categoriesBrowsing and interaction data, Device characteristics, User-provided dataBrowsing and interaction data, Device characteristics, Device identifiers, User-provided data
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage durationSessionPer Qualtrics cookie documentation
Processing locationContract data centre; United StatesContract data centre; United States

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page