Set up your bannerConfigure Your ToolsWebsite and Shop Platforms

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.

  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. 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.

ConfigurationSummary
Configuration A — Medium riskConsenter integrated via the Wix consent policy; analytics and advertising false until consent.
Configuration B — Higher riskNo consent policy set; Wix analytics and marketing functions load by default.

Step 1 — Configure Wix

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionImprove the service; Support marketing analyticsImprove the service; Support marketing analytics
2Consent policySite Properties API, updateConsentPolicyfunctional, analytics, advertising, dataToThirdParty from ConsenterNot set
3Custom codeSettings → Custom codeCategorise as non-essentialDefault 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 fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesImprove the service, Support marketing analyticsImprove the service, Support marketing analytics
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers
Data categoriesAggregated site statistics, Browsing and interaction data, Device identifiers, Device characteristics, Privacy choicesAggregated site statistics, Browsing and interaction data, Device identifiers, Device characteristics
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage durationPer Wix cookie informationPer Wix cookie information
Processing locationPer 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

On this page