Goal

This article aims to guide customers using TraceDock on the best implementation practices when utilizing a Consent Management Platform (CMP).

Who can it help?

• Web developers

Best practice

Using web tracking and cookies for marketing purposes has become essential nowadays. However, the use of this data is subject to strict regulations. In Europe, specific guidelines such as the General Data Protection Regulation (GDPR) apply.

An important aspect of using a web tracker is obtaining explicit consent from users for collecting cookies. This is where a Consent Management Platform (CMP) may come into play. CMPs help manage consents and typically provide the cookie banner or pop-up where users can accept or decline cookies. Commonly used CMPs include Cookiebot, OneTrust, and Usercentrics.

Below you can find the best practice for implementing TraceDock in combination with a CMP:

Step 1 - Classify tracking cookies
Ensure that the tracking cookies (_tdbu, _tdid & anonymous_id) from CM.com are classified as "Marketing cookies".

Step 2 - Script loading order
Ensure the CMP script loads before the TraceDock script. This allows the CMP to disable cookies if the user has not granted permission.

Step 3 - Consent-based loading
The TraceDock web tracking script should load only if consent for marketing cookies is given.

Many CMPs offer a feature called auto-blocking. This means all cookies are blocked when the website loads until the user consents via the cookie banner or pop-up. Cookiebot is an example of a CMP with this functionality. More information can be found on the Cookiebot website: Cookiebot Automatic Cookie Blocking.

Additionally, you can set up cookie blocking manually. For details, visit the Cookiebot website: Cookiebot Manual Cookie Blocking.