Auto-Blocking FAQ

Does the Auto-Blocking script have to be the first element on the site?

Yes, the Auto-Blocking script must be the first item in your head section of your source code. This is to ensure it runs before any cookies are dropped.

Not all the cookies are being blocked by Auto-Blocking. What do I need to do?

You should make sure all cookies on your site have been categorized in the OneTrust application. Cookies that are uncategorized will not be blocked by the Auto-Blocking feature. Additionally, any cookies that are categorized as Strictly Necessary will not be blocked by the Auto-Blocking feature.

If all of the cookies are categorized, verify that the cookies being dropped are not categorized as Strictly Necessary cookies. These cookies will not be blocked by default.

Any cookie that is categorized but does not have a source URL associated with will continue to fire on the website irrespective of a user's consent. For information on how to check the source URL for a cookie, see Configuring Purposes.

Check the consent model being used for your region. If the consent model is opt-out, then the cookies will be enabled until the site visitor opts out.

What happens to newly added, uncategorized cookies on my site when using Auto-Blocking?

Cookies will not be blocked until they are categorized. Make sure to republish your scripts if you make any categorization changes for those changes to reflect on the site.

When should I use a tag manager versus Auto-Blocking?

Simple integrations are available for all tag managers, giving you a great way to control when tags fire based upon user consent.

With Auto-Blocking turned on, new tags are automatically disabled if the tag is in a category blocked until consent is given.

If you already have a tag manager integrated with your domain, it is recommended that you utilize the respective tag manager blocking mechanism.

Auto-Blocking is only recommended if you have 20-30 cookies or if the CMS does not allow code modification for manual blocking, like Shopify or Wordpress. Additionally, it is important to note that Auto-Blocking requires cookie categorization in the OneTrust tenant and only works for cookies that have a resource URL.

For additional details on Auto-Blocking requirements, please see OneTrust Cookie Auto-Blocking™.

How do I ensure my Auto-Blocking settings are up to date?

You can rescan your site by using the automatic scan scheduler or by manually initiating a scan. If new cookies are found, you will need to make sure they are categorized and have the correct resource URL added or they will not be blocked.

After categorizing the new cookies, you will need to publish the script.

Can I use custom category IDs with Auto-Blocking?

Yes, you can use custom category IDs with the Auto-Blocking script. It uses whatever IDs are configured in the tool. The Auto-Blocking script adds the appropriate IDs to the tags that need to be blocked.

Does Auto-Blocking work with iFrames embedded directly on the page?

Right now Auto-Blocking will only work for iframes created dynamically on the page, such as advertising iframes that are injected by a JavaScript file.

For iframes embedded directly on page (for example, some YouTube videos), we recommend following the manual steps to block those iframes.

For more information, see Client-Side Cookie Management.

Can I use an Opt-out consent model with Auto-Blocking?

Yes, you can use any consent model with Auto-Blocking.

For more information, see OneTrust Cookie Auto-Blocking™.

When Auto-Blocking is enabled on my domain, why are some functionalities on the page (such as images, videos, etc.) not loading properly when particular cookie categories are set to inactive?

This happens when the Auto-Blocking file contains sources responsible for loading those functionalities.

To ensure all aspects of your site load properly when cookies are rejected, you can unblock any unnecessary sources from your Auto-Blocking file. Unnecessary sources may include sources ending in .img, .png, .css or .gif.

You can also test whether Auto-Blocking is causing an issue on your site by blocking the network call to the Auto-Blocking file and reloading the site to see if the behavior continues.

For more information on how you can unblock sources, see OneTrust Cookie Auto-Blocking™.