Set up your bannerConfigure Your ToolsAffiliate and Price Comparison

Webgains

How to configure Webgains 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 reflect Webgains affiliate tracking on an advertiser website in the Consenter Manager. Webgains' tracking runs in a single consent-gated mode, so this guide uses a single fixed-behaviour table.

  1. Implement the service as described below.
  2. Map the implementation in the Consenter Manager.
  3. 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. Webgains onsite script and conversion tracking.

What the service does in this scope. Webgains' default method is a first-party cookie, _CK_WG_, set by the onsite script on the advertiser domain when a user arrives via an affiliate link. The cookie stores campaign, programme ID and a unique click reference; the script only drops it on user consent and no user-identifiable information is sent. A consent=1 / consent=0 parameter can be passed in tracking URLs and scripts. Webgains positions itself as a data processor.

Step 1 — Implement Webgains

Configuration areaFixed behaviour / required action
Processing purposesSupport marketing analytics (affiliate attribution)
Cookie_CK_WG_ first-party, set only on consent
Consent signalPass consent=1/0 from Consenter
ContractWebgains DPA

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesSupport marketing analytics—
Tracking methodFirst party tracking (cross-session)_CK_WG_ on advertiser domain
IdentifierDevice identifiersClick reference
Data categoriesDevice identifiers, Browsing and interaction data, e-commerce Activity, Privacy choicesConversion data; consent parameter
Legal role of data recipientProcessor—
Personalisation modelNo personalisation—
Maximum storage durationPer programme cookie period—
Processing locationPer Webgains DPACheck 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

On this page