ChannelSight
How to configure ChannelSight 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, Support marketing analytics
Overview
This guide explains how to reflect the ChannelSight "Where to Buy" widget on a brand website in the Consenter Manager. ChannelSight documents no visitor-facing privacy settings, 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. ChannelSight Where-to-Buy widget and click tracking to retailers.
What the service does in this scope. ChannelSight acts as a data processor for its brand customers, who are controllers. Where customers include cookies in their content, cookie consent is requested via a pop-up. ChannelSight markets its tracking as not relying on cookies or tracking pixels.
⚠ Recommendation. "Cookie-less" click tracking still transmits interaction data and the IP address to ChannelSight. If you load the widget without consent, treat this as a self-assessed exemption and have your DPO confirm the legal basis.
Step 1 — Implement ChannelSight
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Unlock additional website features; Support marketing analytics |
| Cookies | Avoid widget content that sets cookies, or load it after Consenter consent |
| Contract | ChannelSight DPA (processor) |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Unlock additional website features, Support marketing analytics | — |
| Tracking method | No tracking | Cookie-less; switch to a cookie-based value if your content sets cookies |
| Identifier | IP address | Request data |
| Data categories | Browsing and interaction data, Aggregated site statistics, IP address | Clicks to retailers |
| Legal role of data recipient | Processor | — |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Per ChannelSight DPA | — |
| Processing location | Per ChannelSight DPA | Irish company; check for US sub-processors; 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