Skip to main content
All CollectionsLeadfeederTracking Script
Using Leadfeeder tracker with consent to comply with GDPR
Using Leadfeeder tracker with consent to comply with GDPR

This article helps you to configure the Leadfeeder Tracker to work with cookie banners.

Tamar Keenan avatar
Written by Tamar Keenan
Updated this week

To help you comply with GDPR, the Leadfeeder tracker can work with most Consent Management Platforms (CMPs). When this is set up, the tracker will set cookies only after the visitor grants consent to the cookies. If the visitor does not grant consent, the tracker will still work and identify companies on your website!

If you would like to understand more in detail on how the Leadfeeder Tracker works and what data it collects, you can read about it here.

How to add Leadfeeder Tracker in your CMP

If you are using a CMP, we don’t recommend blocking the entire Leadfeeder Tracker until the visitor grants consent. If the tracker is blocked completely until consent is granted, and if most of your visitors don’t grant consent, the companies identified on your website by Leadfeeder will be significantly lesser than the actual number. This means you will not be using Leadfeeder to get the most value out of it.

Instead, you can configure Leadfeeder with your CMP in a way that provides the most value to you while complying with GDPR and national laws and regulations ✅

To set this up in the most efficient and compliant way, you will need to:

  • Enable Consent Mode of the Leadfeeder tracker

  • Add the tracker in your CMP under the category of “Analytical cookies”

  • Configure consent events: trigger a JS request to the tracker when consent is granted

  • Once the tracker receives the consent event, it will set the cookie

The easiest way to set this up is in the Google Tag Manager and the steps are as follows:

STEP 1: Ensure you are using the correct GTM container

If you already have a cookie consent management platform set up in your Google Tag Manager container (for example CookieHub, OneTrust, etc.), please make sure that it is in the same GTM container you have connected to your website where the Leadfeeder Tracker is. Please make sure that Leadfeeder Tracker is installed to trigger on all pages. It won't set cookies until we specifically instruct it to (which is done in the next step).

STEP 2: Configure Consent Event

Set up a new custom HTML tag for accepting the Dealfront cookie and include the following code there:

<script>
 if (window.ldfdr) {
   window.ldfdr.acceptCookie()
 }
</script>

This is the consent event that instructs the tracker to safely set the cookie as the consent has been granted. In GTM, it should look like this:

STEP 3: Choose a trigger

Choose a trigger from your cookie consent management platform sample triggers. For example, if you use CookieHub, you can choose CookieHub - Allowed Analytics.

STEP 4: Publish

Save, submit changes, and publish.

STEP 5: Enable Consent Management Mode

Enable the consent management mode of Leadfeeder tracker by going to tracker settings here. This step is very important as if this mode is not enabled, the tracker will still always set cookies.

Once the above steps are finished, only the visitors that grant cookie consent on your website will have the Dealfront cookie set in their browser. Note that for the visitors that do not grant cookie consent, the tracker will not set cookies.

When cookies are disabled, the Leadfeeder tracking script will still identify companies visiting your website. However, it won’t be able to recognise individual visitors on your website as returning (repeat) visitors. That means that each visitor might be shown as a new visitor in the Leadfeeder UI even if they might have visited your website before. You can read more about the sessions and returning visitors here.

What if I don’t use GTM?

If you don’t use GTM, you can also set up a process similar to the one explained above in the tag management system you currently use. If you don’t use any tag management system, you can reach out to your technical team to set up a similar process. As soon as the tracker receives the consent event (in step 2), it will set the cookie and you are all set.

On top of the above-mentioned process, based on advice from your legal team on GDPR compliance, you can also anonymise the IP addresses in your user settings here.

--

Questions, comments, feedback? Please let us know by contacting our support team via the chat or by sending us an email at support@dealfront.com.

RELATED:

Did this answer your question?