iAdvize
How to configure iAdvize at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Unlock additional website features, Receive marketing offers
Overview
This guide explains how to implement different privacy configurations for iAdvize 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. The iAdvize conversational tag (chat, chatbots, expert community). iAdvize SAS is a French company with subsidiaries including iAdvize GmbH and iAdvize Inc. (US).
What the service does in this scope. iAdvize needs one cookie for the conversation, iadvize-SID_NUMBER-vuid; browser type, terminal type and page URL are attached to this VUID for 12 months to apply targeting rules. iAdvize offers two consent methods: management by the CMP alone (iAdvize hidden if cookies are refused), or coordinated management, where the tag is triggered without cookies, iAdvize is always displayed, and consent can also be given in the chatbox (Settings > Consent Management > Privacy).
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | CMP-only: tag fires after Consenter consent; iAdvize hidden otherwise. |
| Configuration B — Higher risk | As A, plus proactive targeting rules and co-browsing / mirroring. |
⚠ Recommendation — coordinated management. iAdvize's recommended coordinated method loads the tag before consent, without cookies. Loading the tag still transmits data to iAdvize. Use it only if your DPO or independent counsel confirms a legal basis for that pre-consent processing.
Step 1 — Configure iAdvize
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Unlock additional website features | Unlock additional website features; Receive marketing offers |
| 2 | Consent method | Settings > Integration > Apps (CMP); Settings > Consent Management | CMP-only | CMP-only |
| 3 | Targeting rules | iAdvize targeting | Basic | Proactive, behaviour-based |
| 4 | Mirroring / co-browsing | Settings > Advanced settings > Agent settings | Off | On |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Per iAdvize's DPA; iAdvize Inc. is a US subsidiary, so list the United States as a potential access location.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Unlock additional website features | Unlock additional website features, Receive marketing offers |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, User-provided data | As A, plus Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | Group based (behaviour) |
| Maximum storage duration | 12 months | 12 months |
| Processing location | Per DPA; United States | Per DPA; 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