Automatic Blocking is a simplified solution for blocking Tags and scripts in AdOpt, as the system performs the blocking automatically, without requiring access to the code, programming knowledge, or complex configurations.

In practice, this means that if your AdOpt Cookie Notice was installed using methods such as Google Tag Manager (GTM) or a Direct Integration Plugin, the Automatic Blocking method will not work properly.

You can choose to automatically configure all tags at once by selecting the “block all tags automatically” button (to block all non-essential tags at once), or you can select and block individual tags as desired.

Automatic Blocking 01.PNG

After enabling automatic blocking for all desired tags, don’t forget to click “Save and publish” so the blocking action is registered on the platform and applied to your website.

When the feature is enabled—either globally or individually—AdOpt adds an additional line of code to your website to perform the blocking. For this reason, this method may affect site performance.

In our tests, automatic blocking was effective 99% of the time. However, unfortunately, we cannot guarantee effectiveness for all services (tags), as there are countless different tags, each with its own level of complexity.

📢 Important: Some tags/scripts may resist this method or find loopholes. For this reason, we strongly recommend ALWAYS verifying whether the blocking is 100% effective.

To perform an analysis that accurately reflects the current state of your website, we recommend rerunning the tag scanner. Repeating the tag scan ensures that tags are read at the present time and that all their files and cookies are mapped.

Automatic Blocking 02.PNG

Click “View details” for the tag and check the label in the “Blocking” field. The label should be updated from “Not blocked” to “Blocked.”

All non-essential tags must be blocked. If automatic blocking does not work, we recommend trying another blocking method (via Google Tag Manager, script-based, or manual blocking).

In some cases, blocking may go beyond what is necessary on certain URLs. Some services have different origins and require those paths (URLs) to be allowed in order to function. This means that the service is blocked and, even after consent is given (consent record), it remains blocked because its origin URL is still being blocked. In this case, you need to identify that origin and allow it.

Automatic Blocking works by identifying the origins of each cookie and blocking those origins. As a result, this approach may cause a “bug” in the website or tags, affect service activation, or even block other tags that share the same origins but belong to the “necessary” category, which should never be blocked.

To limit the blocking action, you must configure the URLs that should be exempt from blocking. Access the settings to further customize automatic blocking:

Avoid blocking on specific URLs, providing flexibility in configuration. Click “Settings” for a general configuration that applies to all tags.

📢 Important: This feature should be used when tag blocking goes beyond what is necessary, blocking tags when it shouldn’t. As a solution, you must configure the URLs that the blocking should ignore.

autoBlock4.png

Refine blocking by identifying tags or scripts based on specific URLs. Add or remove URLs as needed. Click “View details – i.”

autoBlock6.png

autoBlock7.png

autoBlock8.png

These advanced settings enable full control over automatic blocking, allowing customization to meet the specific needs of your website. Be sure to review and adjust them as necessary to ensure an effective implementation.

Para realizar uma análise que seja fiel a situação atual do seu site recomendamos que você repita o “escâner de tags” do seu site. Repetir a leitura das tags garantirá que as tags sejam lidas na presente data e cada um de seus arquivos e cookies serão mapeados.

📢 Importante: Essa funcionalidade deve ser empregada quando o bloqueio de Tags ultrapassa o necessário, bloqueando Tags quando não deveria. Como solução, será preciso configurar as URLs que o bloqueio deve ignorar.

2. Configurações Avançadas: Refine o bloqueio identificando Tags ou scripts com base em URLs específicas. Adicione ou remova URLs conforme necessário. Clique em "Ver detalhes - i".

3. No detalhamento da Tag, clique em “Configuração avançada”.

4. Adicione as URL’s da origem e semelhantes, para garantir a identificação.

Automatic Blocking is a simplified solution for blocking tags and scripts on AdOpt, as the system will perform the blocking automatically, without the need for code access or programming skills.

Important For better efficiency of the Automatic Blocking method, we recommend that the Cookie Banner tag be installed on the site, via code, at the beginning of the

. This way, the tag will be read with preference, and the Automatic Blocking settings will also be prioritized. If the service/tag you intend to block is read/executed before the AdOpt tag, it is possible that the automatic blocking will not work.

You can activate automatic blocking for all tags at once by selecting the "Automatically block all tags" button (to select all non-required tags at once) or individually select the desired tags.

Selection and blocking of all tags simultaneously

After activating the automatic blocking for all desired tags, don't forget to "Save and publish" so that the blocking action is recorded on the platform and sent to your website.

With the feature activated broadly or individually, the AdOpt system adds an additional line in your website's code to perform the blocking. For this reason, it's worth mentioning that this method can interfere with site performance.

In our tests, automatic blocking was effective 99% of the time, but unfortunately, we cannot guarantee effectiveness for all services (tags) - as there are numerous distinct tags, each with its complexity.

Important

This method is a facilitated option, but it may not be effective for all tags.

It's essential to be aware of this! Some tags/scripts may resist this method or find loopholes, and for this reason we ALWAYS recommend analyzing whether the block is 100% or not.

In order to carry out an analysis that is faithful to the current situation of your website, we recommend that you repeat the “tag scan” of your website. Repeating the tag scan will ensure that the tags are read on the current date and each of your files and cookies are mapped.

Click on “See Details” of the tag and check the label in the “Blocked” field. The label should be updated from “Not blocked” to “Blocked”.

All non-required tags need to be blocked. If automatic blocking does not work, we recommend trying another blocking method (via Google Tag Manager; script or manual).

What can I do if the blocking does not work as desired? In some cases, blocking works more than necessary on other URLs. Some services have different origins and must have their path (URL's) cleared for functioning. What do you mean? The service is blocked and even after acceptance (“consent granted”) it continues to be blocked, because its URL of origin is being blocked. In this case, it is necessary to identify this path and release it.

Automatic blocking works by identifying the origins of each cookie and blocking their origins. This can cause a “bug” in the operation of the site or tags, the service activation, or even block other tags that have the same origins but are from the “required” category.

To limit the blocking action, you will need to configure the URLs that will be free from blocking action.

Access settings to further customize automatic blocking:

These advanced settings give you complete control over automatic blocking, allowing you to customize it to meet your site's specific needs. Be sure to review and adjust as necessary to ensure effective implementation.