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.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- 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.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Intercepts with Site History / Page Count in session storage; no repeated-display cookie; after consent. |
| Configuration B — Higher risk | Intercepts 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 area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service |
| 2 | Site History / Page Count storage | Project options | Session storage | Cookies |
| 3 | Prevent Repeated Display | Intercept settings | Off | On |
| 4 | Digital Experience Analytics | DXA project | Off | On |
| 5 | Loading | Consenter script blocking; QSI.API.load after consent | After consent | After 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 field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service | Improve the service |
| Tracking method | First party tracking (single session) | First party tracking (cross-session) |
| Identifier | No identifier | Device identifiers |
| Data categories | Browsing and interaction data, Device characteristics, User-provided data | Browsing and interaction data, Device characteristics, Device identifiers, User-provided data |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Session | Per Qualtrics cookie documentation |
| Processing location | Contract data centre; United States | Contract 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