Unbounce
How to configure Unbounce 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 Unbounce landing pages 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. Landing pages built and hosted with Unbounce (Unbounce Marketing Solutions Inc., Vancouver, Canada).
What the service does in this scope. Unbounce pages set the cookies ubpb, ubvs and ubvt; ubpv keeps a visitor on the same A/B variant and ubvt supports external conversion tracking. Unbounce offers a built-in cookie banner so visitors can accept or reject cookie tracking on the landing page. Unbounce is a data processor and provides a DPA on request. A customer reported that Unbounce adds its own Google Tag Manager and events.ub-analytics.com trackers to landing pages.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Single-variant landing page; Unbounce cookies after consent; forms with consent text. |
| Configuration B — Higher risk | A/B tests and conversion tracking (ubpv, ubvt); after consent. |
No configuration without prior consent. Unbounce itself categorises these cookies as performance cookies requiring opt-in on its own site.
Step 1 — Configure Unbounce
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service; Support marketing analytics |
| 2 | Consent | Consenter on the landing page, or Unbounce cookie banner | Before tracking | Before tracking |
| 3 | A/B testing | Page variants | Off | On |
| 4 | Conversion tracking | Unbounce conversion goals / external tracking | Off | On |
| 5 | Forms | Form builder; consent checkbox | Consent text | Consent text |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Unbounce is Canadian; check the DPA for US sub-processors (e.g. CDN and analytics) and list the United States if present.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service | 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, User-provided data | As A, plus Device characteristics |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Per cookie inspection | Per cookie inspection |
| Processing location | Canada; per DPA | Canada; per DPA |
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