The Tracking and Consent Framework (TCF) 2.2 Guidance

Webgains is a member of the IAB Transparency & Consent Framework (TCF). To obtain consent for Webgains using TCF, you must ensure your Consent Management Platform (CMP) includes Webgains GmbH (Vendor ID: 870).

This document outlines the solutions you can use to ensure Transparency and Consent Framework (TCF) 2.2 compliance when working with Webgains. Since Webgains is already set up for TCF compliance, your role as a publisher is to ensure that user consent is correctly gathered and passed during all interactions involving Webgains tracking links.

Key Steps for TCF Integration with Webgains

1. Ensure the Correct Vendor ID (870) is used

Webgains is identified by Vendor ID 870 within the TCF framework. The complete vendor list can be found here: Vendor List

You need to ensure that your system or Consent Management Platform (CMP) is configured to pass consent data for Vendor ID 870.

2. Set Up and Configure a Consent Management Platform (CMP)

To comply with TCF, you must implement a Consent Management Platform (CMP) on your website. The CMP collects and manages user consent before any tracking technologies (like cookies) are activated.

• Your CMP Should:

  • Ask users for consent to track their data.

  • Allow users to specify consent preferences for each vendor, including Webgains (Vendor ID 870).

  • The CMP will generate a consent string according to the TCF specifications, which will include information on whether the user has consented to data processing by Webgains (Vendor ID 870).

3. Passing Consent

When a user interacts with your site, their consent preferences are captured via your Consent Management Platform (CMP), which generates a TCF-compliant consent string. This string includes consent status for each vendor, including Webgains (Vendor ID 870).

To ensure Webgains handles tracking in accordance with the user's consent, you must ensure that either of the following methods is used to pass consent:

Option 1: Consent Parameter in Tracking Links

You can explicitly include a consent parameter in your Webgains tracking URL based on the user’s choice:

• consent=1: Consent granted

• consent=0: Consent denied

Example Click Tracking Link:

https://assets.ikhnaie.link/click.html?wgcampaignid=XXXXXX&wgprogramid=XXXXXX&consent=1

Including the consent parameter is a clear and straightforward way to pass consent. If omitted, Webgains assumes consent is granted unless the TCF string is also provided and indicates that consent is denied. Including the parameter is still recommended to ensure transparency and consistency.

Post-View Ad Example

For post-view tracking (e.g., ad views), if you choose to use the consent parameter method, add it to the script URL like so:

<script language="javascript" type="text/javascript">
  (function(){
    var uri = 'https://assets.ikhnaie.link/link.html?wglinkid=XXXXXX&wgcampaignid=XXXXXXX&js=1&nw=1&consent=1';
    var me = document.currentScript;
    var s = document.createElement('script');
    s.setAttribute('src', uri);
    me.parentElement.insertBefore(s, me.nextSibling);
  })();
</script>

Option 2: Relying on the TCF Consent String

If your CMP is correctly set up and passing the TCF consent string, you do not need to manually include the consent parameter. Webgains will process or ignore tracking based on the vendor-specific permissions within the string.

• If the string indicates consent for Vendor ID 870, tracking proceeds.

• If consent is denied or Vendor ID 870 is excluded, tracking will not occur — even if the consent parameter is present.

4. Handle Missing Consent Parameter

If the consent parameter is missing from the tracking link, Webgains will assume consent is granted by default—unless the TCF consent string is present and explicitly denies consent. To avoid ambiguity and ensure clear, compliant communication of the user’s choice, it is strongly recommended to always include the consent parameter when using tracking links.

5. Testing and Validation

After implementing the CMP and consent flow, test the system to ensure proper functionality.

• Test Consent Scenarios:

  • Ensure the consent string accurately reflects user consent for Vendor ID 870.

  • Validate that the consent parameter is correctly passed in tracking links.

  • Verify that tracking only happens when consent is given.

For any other queries, please contact support@webgains.com.