Connexity
How to configure Connexity 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, Customise online ads
Overview
This guide explains how to reflect the Connexity merchant pixel in the Consenter Manager. Connexity documents a consent-signal mechanism but no separate configuration tiers, so this guide uses a single fixed-behaviour table.
- Implement the service as described below.
- Map the implementation in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.
At a glance
Scope. Connexity merchant pixel (conversion tracking and Dynamic Product Ads).
What the service does in this scope. In relation to merchants, Connexity is a controller under the GDPR and, together with Taboola, uses data for affiliate and behavioural advertising. Connexity offers merchants ways to pass consent signals and to opt out of behavioural advertising. Pixel details, including the unified pixel for Dynamic Product Ads, are covered by the Merchant Privacy Terms.
Step 1 — Implement Connexity
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Support marketing analytics; Customise online ads |
| Pixel | Load after Consenter consent and pass the consent signal |
| Behavioural advertising | Opt out via the mechanism Connexity offers if not wanted |
| Contract | Connexity Merchant Terms and Merchant Privacy Terms |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Support marketing analytics, Customise online ads | — |
| Tracking method | Third party tracking (crosssession, cross-website) | Behavioural advertising |
| Identifier | Device identifiers | Cookie IDs |
| Data categories | Device identifiers, Browsing and interaction data, e-commerce Activity, Users' profiles, Privacy choices | Consent signal passed |
| Legal role of data recipient | Individual Controller | — |
| Personalisation model | Profile based | Behavioural advertising |
| Maximum storage duration | Per Connexity Merchant Privacy Terms | — |
| Processing location | United States | US enterprise; 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