Set up your bannerConfigure Your ToolsA/B Testing and Personalisation

VWO (Visual Website Optimizer)

How to configure VWO (Visual Website Optimizer) 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, Personalise the website

Overview

This guide explains how to implement different privacy configurations for VWO 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. VWO SmartCode for testing, personalisation and VWO Insights (heatmaps, session recordings).

What the service does in this scope. VWO stores a pseudonymised UUID per visitor. By default, the last octet of IPv4 (or last five segments of IPv6) addresses is anonymised before storage; stricter formats or disabling IP storage are configurable. Customers can opt for EU data residency; the EU data centre is in Belgium (europe-west1). SmartCode can run conditionally on the visitor's cookie consent via callbacks. VWO acts as processor.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskTesting only; IP storage disabled; EU data residency; SmartCode after consent.
Configuration B — Higher riskTesting, personalisation and VWO Insights session recordings; default IP anonymisation; after consent.

No configuration without prior consent. VWO stores a UUID and recommends consent before tracking.

Step 1 — Configure VWO

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionImprove the serviceImprove the service; Personalise the website
2ConsentSmartCode cookie-consent configurationAfter consentAfter consent
3IP address settingsPrivacy settingsDo not store IPDefault (last octet)
4Data residencyVia Customer Success ManagerEUEU or default
5Session recordingsVWO InsightsOffOn (with masking)

Step 2 — Map the configuration in the Consenter Manager

Processing location. Belgium (europe-west1) for EU residency; the region name indicates Google Cloud, a US provider subject to the US CLOUD Act. List the United States as a potential access location.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesImprove the serviceImprove the service, Personalise the website
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiersBrowsing and interaction data, Device characteristics, Device identifiers, IP address anonymised, Users' profiles
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationGroup based (behaviour)
Maximum storage durationPer account retentionPer account retention
Processing locationEU (Belgium); United States as potential access locationSame, or per residency choice

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