[en]If you have lots of cookies and/or intensive site content, AutoBlock must be loaded synchronously on the page. If you have a long list of cookies, the download of the AutoBlock script may cause your page to render more slowly than expected. If this is a concern, consider integrating with your tag manager for a more performant implementation. For more information, see Cookie Consent Integration with Google Tag Manager.
[en]If you generate revenue from targeted ads AutoBlock.js might impact the timing and order of scripts firing. This can sometimes cause ad targeting libraries to malfunction and impact revenue. The best practice is to use a method other than AutoBlocking for cookies related to ad targeting.
[en]If you leverage Bulk Domain Management, due to the nature of web properties, the source URLs for many scripts will change per domain.
[en] If any of the above scenarios are applicable to your domain(s), AutoBlock might not be the best fit for your website. Consider tag manager integration or type-rewriting for your cookie blocking needs. It is still possible to use a combination of solutions, so AutoBlock may be a good fit for some but not all of your cookie blocking.
[en] OneTrust AutoBlocking can block commonly identified trackers automatically without the need to locate a source URL. This behavior is configured during publishing. The common hosts are listed below.
表1 共通ホストリスト
addthis.com
addtoany.com
adsrvr.org
amazon-adsystem.com
bing.com
bounceexchange.com
bouncex.net
criteo.com
criteo.net
dailymotion.com
doubleclick.net
everettech.net
facebook.com
facebook.net
googleadservices.com
googlesyndication.com
krxd.net
liadm.com
linkedin.com
outbrain.com
rubiconproject.com
sharethis.com
Taboola.com
twitter.com
vimeo.com
yahoo.com
youtube.com
[en] To enable this functionality, see the Automatically Block Known Tracking Technologies section in Cookieコンプライアンススクリプトを実装する. When enabled, any script on the website inserted by the hosts listed above is mapped to OneTrust’s Targeting category and is only allowed when the user accepts targeting cookies on a site.
[en] Things to Know
[en] Cookies may not be detected by the scanner if the related tag is triggered by actions such as form submission, scroll depth, timing delay, etc. These tags will either need to be added manually to OneTrust or blocked using another method.
[en] Any cookie categorized as non-essential (Functional, Performance, Targeting, Social Media, or any custom category) that has an accurate source URL will be controlled by auto-blocking. If a cookie is categorized as Strictly Necessary or Unknown, it will not be included in the OtAutoBlock auto-blocking.
[en] Cookies set by in-line scripting (e.g., using 'document.cookie' inline) are not supported by auto-blocking functionality. Instead, consider Client-Side Cookie Management type-rewriting for these cookies.
[en] OneTrust suggests using autoblock for simpler websites (where you don’t have dynamic URLs firing cookies on the website and where you have fewer cookies, which makes it easier to maintain the AutoBlock file).
注記
[en] You will need to check your autoblock.js file every time a new publish occurs to ensure no new or incorrect URLs are added.
[en] This JavaScript file is available within the scripts in https://cdn.cookielaw.org/consent/(YOUR. DATA DOMAIN ID)/AutoBlock.js
2.
[en] Does the Auto-Blocking script have to be the first element on the site?
[en] Yes, the Auto Blocking script must be the first item in your head section. This is to ensure it runs before any cookies are dropped.
3.
[en] Not all the cookies are being blocked. What do I need to do?
[en] Ensure all cookies on your site have been categorized. 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.
[en] Confirm that the correct source URL is linked to the cookie in the OneTrust tool if a cookie is not being blocked. Republish after adding the correct URL and test if the cookie is now being blocked as expected.
[en] 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.
[en] Confirm the cookies dropped on your site are blockable.
[en] Contact OneTrust Support if you experience persistent issues.
4.
[en] How do I check which cookie has the source URL that is breaking my site?
[en] You can export an Excel file that gives you a list of all the cookies and their associated source URL(s). To export this file, follow the steps in the To export you cookie list section of Cookieを管理/分類する.
重要
[en] Disable the Exclude Resource URLs setting on the Cookie Export modal when exporting your cookie list.
5.
[en] What happens to newly added, uncategorized cookies on my site?
[en] Cookies will not be blocked until they are categorized, have the correct source URLs included, and the AutoBlock script has been republished to include the new URLs.
6.
[en] When should I use a tag manager versus Auto-Blocking?
[en] Simple integrations are available for all tag managers, giving you a great way to control when tags fire based upon user consent.
[en] With Auto Blocking turned on, new tags are automatically disabled if the tag is in a category blocked and the correct source URLs are present until consent is given.
7.
[en] How do I ensure my Auto-Blocking settings are up to date?
[en] 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 with correct source URLs present or they will not be blocked.
[en] After categorizing the new cookies, you will need to publish the script.
8.
[en] Can I use custom category IDs with Auto-Blocking?
[en] 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.
9.
[en] Does Auto-Blocking work with iframes embedded directly on the page?
[en] 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.
[en] For iframes embedded directly on page, for example some youtube videos, we recommend following the manual steps to block those iframes.
[en] Can I use an Opt-out consent model with Auto-Blocking?
[en] Yes, you can use any consent model with Auto-Blocking. When using an opt-out consent model, cookies are allowed when the user first visits the site. If the users chooses to opt-out or reject a category, cookies belonging to that category are blocked on the website. This also applies to AutoBlocking.
