OneTrust Auto-Blocking se puede utilizar para bloquear automáticamente las cookies para que no se configuren en los dispositivos de visitantes del sitio. El bloqueo automático automatiza el proceso de configuración de cookies, scripts y etiquetas para responder a la preferencia seleccionada por los visitantes del sitio.
En lugar de utilizar un administrador de etiquetas o agregar manualmente type="text/plain" para la reescritura de tipo JavaScript, simplemente puedes activar una configuración para tu aviso y el script del centro de preferencias que bloqueará automáticamente las cookies categorizadas en tu sitio.
Cómo funciona
OneTrust Cookie Auto-Blocking funciona utilizando tus resultados de análisis y categorizaciones para bloquear automáticamente la configuración de cookies antes de que se otorgue el consentimiento del visitante del sitio.
Esto se basa en las categorías de cookies que configuraste y el modelo de consentimiento que seleccionaste. Cuando el script se carga en tu página, las cookies se bloquean según tu política de consentimiento, las reglas de geolocalización y las preferencias seleccionadas por el visitante del sitio.
Si una categoría de cookies no se activa o un visitante del sitio se sale de una categoría, la tecnología de bloqueo automático evitará que dicha categoría se active.
¿Es adecuado Auto-Blocking para tu dominio?
Esta sección te ayudará a determinar si la funcionalidad de bloqueo automático de OneTrust en el módulo Consentimiento de cookies es una solución adecuada para tu dominio.
[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] Implementation Requirements
Requisito
Explicación
Se requiere el script OtAutoBlock para ejecutarse de forma sincrónica.
Si el atributo asincrónico del script OtAutoBlock se añade y es "true", el resto de la página continuará analizándose y las etiquetas pueden dispararse. Esto puede establecer cookies antes de que el script OtAutoBlock inyecte los elementos HTML apropiados.
Los scripts OtAutoBlock y otSDKStub deben colocarse en el elemento <head> por el sistema de administración de contenido (CMS) o directamente en el código HTML.
Si los scripts se implementan con un administrador de etiquetas, existe un alto riesgo de latencia entre el dominio y el administrador de etiquetas. Esto da lugar a la posibilidad de que las etiquetas se activen antes de que se complete el script OtAutoBlock.
Si los ingresos se generan a partir de anuncios dirigidos, se recomienda utilizar métodos de bloqueo manuales.
Auto-Blocking puede hacer que las etiquetas se comporten de manera inesperada en la carga de la página y puede afectar a los ingresos de anuncios.
[en] Common Host 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.
Tabla 1. Lista de host común
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 Implementación de scripts de Consentimiento de cookies. 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.
Requisitos previos
OneTrust Cookie Auto-blocking utiliza tus resultados de análisis y categorizaciones de cookies para saber qué bloquear. Si el análisis del sitio no ha detectado una cookie o no está clasificada, no estará controlada por el script de bloqueo automático.
Para garantizar una implementación exitosa del script de bloqueo automático, vuelve a analizar tu sitio antes de comenzar la implementación y asegúrate de que todas las cookies estén clasificadas.
Implementación de OneTrust Cookie Auto-Blocking
Atención
Nunca debes implementar esta funcionalidad sin antes validarla en un entorno de prueba.
En el menú Consentimiento de cookies, selecciona Scripts. Aparecerá la pantalla Scripts.
Selecciona el dominio para el que quieras activar el bloqueo automático. Aparecerá la pantalla Scripts.
Haz clic en el botón Publicar la prueba. Aparecerá el panel Publicar.
Selecciona la versión del script que quieras publicar y haz clic en Confirmar.
[en] Click the Confirm button.
Activa la opción Habilitar el bloqueo automático. Esto actualizará el script para incluir OneTrust Auto-Blocking.
Sugerencia
[en] If you’d like to automatically include AutoBlocking for scripts from Common Hosts, select Automatically Block Known Tracking Technologies.
[en] Click the Publish Test Scripts button.
Navega a la pestaña Scripts de prueba. Haz clic en el botón Copiar Scripts para copiar el script y luego colócalo como el primer script en el encabezado del sitio.
[en] Click the Copy Scripts button to copy the script.
[en] Place the script as the first script in the head section of your site.
Atención
[en] The Autoblock.js script must be added directly to the page, not via an injector or tag manager.
Este script debe colocarse primero para que todo lo demás funcione correctamente. Si no se coloca primero, no podrás bloquear de forma efectiva las cookies para que se configuren.
Si ya tienes un script de aviso implementado en tu sitio y quieres utilizar el bloqueo automático, debes reemplazarlo con el nuevo script generado mediante la activación de la configuración.
Después de la prueba, repite el proceso para el guion de producción y coloca el guión en tu sitio de producción.
[en] You can remove source URLs from your AutoBlocking Javascript for greater control over your autoblocking functionality.
[en] On the Cookie Consent menu, select Websites. The Websites screen appears.
[en] Click the name of a website. The Website Details screen appears.
[en] Go to the Auto-Block tab.
[en] Enable the Enable Auto-Blocking setting, if disabled.
[en] Select the source URLs you want to remove from your auto-blocking.
[en] Click the Unblock Source URL button. A confirmation modal appears.
[en] Click the Confirm button.
[en] To manually block source URLs
[en] On the Cookie Consent menu, select Websites. The Websites screen appears.
[en] Click the name of a website. The Website Details screen appears.
[en] Go to the Auto-Block tab.
[en] Enable the Enable Auto-Blocking setting, if disabled.
[en] Click the Block Source URL button. The Block Source URLs modal appears.
[en] Enter a Source URL for the cookie you want to add to your auto-blocking script.
[en] Click the Search button.
[en]Previously Linked URLs
[en] If the source URL matches to an existing cookie, the existing cookie displays.
[en] Click the Block button.
[en]New URLs
[en] If the source URL does not match to an existing cookie, configure the fields.
[en] Field
[en] Description
[en] Link to
[en] Select an item to which the source URL should be linked.
[en] Existing Cookie
[en] New Cookie
[en]Existing Cookie
[en] Cookie
[en] If linking to an existing cookie, select the cookie to which the URL belongs.
[en]New Cookie
[en] Name
[en] Enter the cookie name.
[en] Host
[en] Enter the host URL.
[en] Lifespan
[en] Select Persistent or Session.
[en] Default Category
Selecciona la categoría predeterminada para la cookie. La categoría se asignará a esta cookie en todos los dominios hasta que la edites en la pantalla Categorizaciones avanzadas.
[en] If a new domain is scanned and an existing cookie is found, it will be assigned to the Default Category on that domain.
[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).
Nota
[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 Gestión y categorización de cookies.
Importante
[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.
