Handling trackers

• Enabling the "Include trackers found when scanning" setting
  • Toggled on (enabled)
  • Toggled off (disabled)
• How to manage the tracker results
  • What is the “Status” column?
  • How do I map?
  • What does it mean when a tracker is “Blocked” or “Not Blocked”?
  • How to handle “not blocked”?
• Displaying tracker information on your cookie policy page
  • Finding your embeds
  • Embed types

Enabling the "Include trackers found when scanning" setting

You can find these settings by selecting Service Settings in the main menu, and clicking the Scan Settings button on the DPS Scanner tab.

A dialog will open where you can switch on a toggle labeled Include trackers found when scanning.

Toggled on (enabled)

Whatever a tracker is found during a scan it'll automatically be assigned to one of the DPS added to your configuration. The tracking entity will additionally be listed on your consent banner and the automatic declaration of trackers found adheres to the Auto-population setting.

With the Include trackers found when scanning setting enabled a new selection field will appear that will allow you to switch between the Services and Trackers views.

Trackers listed as Done in the Trackers section will be presented under their respective DPS under Storage Information within your CMP banner.

To view these, expand one of the categories on the Categories tab of your banner and click on the icon next to one of the services.
On the next view, scroll to the bottom and expand the Stored Information section to view the trackers associate with that service.

  

Toggled off (disabled)

Should you choose to disable the Include trackers found when scanning toggle, the Trackers section will disappear from the Service Settings overview.
Subsequently, the Storage Information section for the DPS on your consent banner will no longer be populated via scan results, but instead adhere to the storage information associated with each DPS from our repository.

How to manage the tracker results

Depending on your auto-population settings you’ll find that some trackers have been automatically mapped and potentially published to your CMP, there might be trackers needing mapping or there might be trackers irrelevant for you CMP declaration.

What is the “Status” column?

Done

These are listed as “DONE” in the tracker management. These are the trackers previously added or automatically added to your declaration. These are “LIVE” but can always be removed at your convenience.

Todo

Tracker listed as “Todo” are the trackers which do not have a DPS mapping yet. These trackers are not displayed on your banner and won't be until you have mapped them to a DPS.
To-do trackers can be “Ignored” should you deem them unimportant. This will also prevent the auto-population feature from publishing them at a later point.

Ignored

Tracker listed as “Ignored” are the tracker you’ve deemed unimportant for your CMP declaration. Should you wish to apply them at a later point you can always unignore later.

How do I map?

For mapping an unmapped tracker you can always use the “MAP DPS” button which will present you with the options for mapping. These will include the DPS added to your config, as well as an opportunity to “un-map” should you deem the tracker unimportant.

Once a DPS has been chosen and the relation confirmed, the tracker should now be listed as “Done” in your tracker management view, meaning that it is mapped correctly and LIVE in your banner.

What does it mean when a tracker is “Blocked” or “Not Blocked”?

The Usercentrics scanner deploys a prior consent check logic when scanning your website, meaning that it determines whether the trackers detected were found before or after a “full consent” was given. This attribute is only available to you via your admin, and is aimed at validating the blocking setup deployed on your website(s).

How to handle “not blocked”?

If you make use of the auto-blocking feature and you find trackers which are not blocked originating from a non-essential DPS, you can choose to deploy a manually blocked script for that specific service, to ensure that the service only loads with permission from the end user. You may confirm by scanning the domain anew, this should reflected in the Blocking column.

If you already manually ensured that the service is blocked prior consent, you should reassess your implementation and validate via a new scan.

If you're unable to ensure that that the service only loads with permission from the end-user you can reach out to our support team. They may be able to provide additional insights into why your set-up does not work, and provide possible solutions.

Displaying tracker information on your cookie policy page

If your website has a cookie policy page, you can easily display using so-called "Tracked Declaration embeds". This essentially an HTML snippet that you place in the exact position, in the body of the cookie policy page. When the snippet is in place, the updated tracker data is automatically injected into the page, completely eliminating the need to manually update the content of your cookie policy.

Finding your embeds

You can find the embeds by selecting Implementation in the main menu, by selecting the Embeddings tab.

You'll find the Tracker Declaration embeds at the bottom of the page.

Embed types

There are different ways of displaying your tracker information.
The different options are listed here:

• Default

  The default view is ordered by Data Processing Services, with all related trackers listed below each service.
  

• Default with filtering

  The default view with filtering is ordered by Data Processing Services, with all related trackers listed below each service. The distinction with the Default view is that here you can choose to only display a specific type of tracker using an HTML attribute.

• Matrix

  The Matrix view is ordered by trackers, with all related services listed with each tracker.
  

• Matrix with filtering

  The Matrix view is ordered by trackers, with all related services listed with each tracker. The distinction with the Matrix view is that here you can choose to only display a specific type of tracker using an HTML attribute.