Wix
How to configure Wix 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, Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for the analytics and marketing functions Wix runs on a site and how to reflect them in the Consenter Manager. Hosting and Wix's essential session and security cookies are out of scope.
- 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. Wix Analytics and Wix-managed marketing functions. Apps and custom code with their own trackers need separate entries.
What the service does in this scope. Wix's consent policy has the properties essential (always true), functional, analytics, advertising and dataToThirdParty. A consent app sets them with updateConsentPolicy, with all types except essential set to false until consent. With the Wix cookie banner, only essential cookies and scripts load first; Functional, Marketing and Analytics require consent.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Consenter integrated via the Wix consent policy; analytics and advertising false until consent. |
| Configuration B — Higher risk | No consent policy set; Wix analytics and marketing functions load by default. |
Step 1 — Configure Wix
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service; Support marketing analytics | Improve the service; Support marketing analytics |
| 2 | Consent policy | Site Properties API, updateConsentPolicy | functional, analytics, advertising, dataToThirdParty from Consenter | Not set |
| 3 | Custom code | Settings → Custom code | Categorise as non-essential | Default categorisation |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Check Wix's DPA and sub-processor list; list the United States where US entities or providers are involved.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service, Support marketing analytics | Improve the service, Support marketing analytics |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device identifiers, Device characteristics, Privacy choices | Aggregated site statistics, Browsing and interaction data, Device identifiers, Device characteristics |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Per Wix cookie information | Per Wix cookie information |
| Processing location | Per Wix DPA; United States possible (CLOUD Act) | Per Wix DPA; United States possible (CLOUD Act) |
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