Set up your bannerConfigure Your ToolsAnalytics

Wizaly

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

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Support marketing analytics

Overview

This guide explains how to implement different privacy configurations for Wizaly 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. Wizaly marketing attribution tracking in hybrid mode. Wizaly is a French company.

What the service does in this scope. With consent, Wizaly collects individualised, detailed data and stores a wzuid entry in local storage; without consent, it collects aggregated data only, sets no persistent cookie, limits IP-based geolocation to country level, keeps no personal data and allows only aggregated viewing and export. The opt-out cookie esv_opt_out (one year) makes the pixel ignore calls. Wizaly acts as processor and keeps each client's data in a separate database. Servers are hosted by IBM France; Amazon Web Services EMEA collects and forwards browsing traces through a node in France; Wizaly commits not to transfer EU personal data outside the EU.

Configurations included.

ConfigurationSummary
Configuration A — Lower risk (⚠ no-consent)Collection without consent: aggregated, no persistent cookie, country-level location.
Configuration B — Higher riskCollection with consent: wzuid in local storage, individual-level attribution data.

⚠ Recommendation — exemption is self-assessed and France-specific. CNIL treats audience-measurement tracers as exempt only under strict conditions. Describe A as a self-assessed exemption. § 25 TDDDG in Germany contains no equivalent exemption. Run A without consent only after review by your DPO or independent counsel.

Step 1 — Configure Wizaly

#Configuration areaWhere to configure itConfiguration A — Lower risk (⚠ no-consent)Configuration B — Higher risk
1Processing purposesOperator decisionSupport marketing analyticsSupport marketing analytics
2Consent statusPassed to Wizaly with each record from the CMPRefused / not expressedGranted
3Opt-outWizaly opt-out page (iframe, CNAME recommended) or esv_opt_out cookieProvideProvide

Step 2 — Map the configuration in the Consenter Manager

Processing location. France (IBM France; AWS node in France). IBM and Amazon are US enterprises subject to the US CLOUD Act; list the United States as a potential access location.

Consenter Manager fieldConfiguration A — Lower risk (⚠ no-consent)Configuration B — Higher risk
Processing purposesSupport marketing analyticsSupport marketing analytics
Tracking methodNo trackingFirst party tracking (cross-session)
IdentifierNo identifierDevice identifiers
Data categoriesAggregated site statistics, Browsing and interaction data, Non-precise location dataBrowsing and interaction data, Device identifiers, Device characteristics, IP address, Users' profiles, Privacy choices
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage durationAggregates onlyPersonal data deleted within 90 days after account closure
Processing locationFrance; United States as potential access locationSame

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