Ignored Trackers Option & Updated Trackers Logic

To provide our customers with even more insight and control when it comes to detected scripts and iframes, we added a new “Ignored” category to our existing tracker categories (Analytics, Functional, Malicious, Marketing, Strictly Necessary, and Unclassified). This is similar to the unclassified logic used with cookies, with a few key differences. Here is why it is important and how it works:

• In order to comply with stricter data privacy laws like GDPR, all trackers (cookies, scripts, or iframes) that store any type of user data (including things like IP address or other items that could be used to tie data back to an individual), should be classified and blocked prior to consent unless they are strictly necessary.

• Our team has always put in a lot of effort when it comes to automatic detection and blocking of not just cookies, but scripts and iframes as well. It is extremely important to correctly detect and block scripts and iframes since they often set data like cookies and that is disallowed by GDPR even if deleted right away. It isn't an easy problem to solve, and there are other companies in the consent management space that struggle with pieces of it. In some cases, they don’t process scripts and iframes and only detect and delete cookies after the fact. As noted above, that is simply not compliant at all with laws like GDPR.

• While we have a very large database of trackers that is used to automatically classify known trackers in real-time, this allows better visibility into all running scripts and iframes, so any of them that are detected but not automatically classified, can still be reviewed and classified when needed. This provides full insight into all scripts and iframes, without impacting functionality, as ignored scripts and iframes are made available for review and classification without being processed by the auto-blocking engine. The combination of the new ignored functionality for scripts and iframes and our existing unclassified functionality for cookies, ensures that nothing falls between the cracks.

• We have had an automated process behind the scenes for quite a while that is used to review and classify newly detected trackers that aren’t yet part of the global trackers database. This provides additional benefits to our team as well when it comes to our commitment to continually updating the global trackers database to make compliance here as easy as possible for all of customers.

For details on how to configure this, visit the help doc here: Configuring Automatic Translation