Documentation
Cookie banners and consent tools
Find out whether your cookie banner holds back the allyWay widget and let it load without consent – with steps for Cookiebot, Complianz and Usercentrics.
Updated October 28, 2026
Many consent tools block scripts until a visitor accepts the cookie banner. Then visitors who don't accept never see the allyWay widget, and our checks – which don't click cookie banners – can't confirm the installation. This page shows how to find out and how to let allyWay load.
Find out whether your banner blocks the widget
Open a private window
Open your website in a private (incognito) window and don't click the banner. Is the widget there?
Accept and reload
If not, accept the banner and reload the page. If the widget now appears, your consent tool is blocking it.
Let allyWay load without consent
Whether allyWay counts as necessary on your website is your decision. What the widget stores in visitors' browsers is listed in Your visitors' privacy. If you decide allyWay may load without consent:
Mark allyWay as necessary
In your consent tool, put allyWay in the "necessary" (or "essential") category, or add it to the list of scripts that are never blocked. The sections below show how for some tools.
Save and clear your cache
Save the change and clear your website's cache.
Test without accepting
Open your website in a private window and check the widget without accepting the banner.
If you added allyWay through a tag manager, the tag manager's own consent settings apply too.
Cookiebot
If Cookiebot's automatic blocking holds back allyWay, either tell Cookiebot to leave the script alone or classify allyWay as necessary.
Leave the script alone: add data-cookieconsent="ignore" to the allyWay script tag and keep your own address. Do this only if Cookiebot really blocks allyWay – Cookiebot warns that on a script it wouldn't block anyway, the attribute can break the page.
<script data-cookieconsent="ignore" src="https://app.allyway.ai/widget/YOUR-WEBSITE-ID/loader.js"></script>Classify allyWay as necessary: in the Cookiebot Manager, open Cookies (in the new layout Cookies & Reports › Cookies and Trackers), find the entries the widget stores in visitors' browsers – names starting with "aw_", and "a11yLanguage" – and choose the category Necessary. Cookiebot applies it after its next scan of your website.
Then save, clear your cache and test in a private window without accepting the banner.
Complianz (WordPress)
Open the Script Center
In WordPress, open Complianz › Integrations › Script Center.
Whitelist allyWay's script
Under Whitelist a script, add a unique part of allyWay's script address, for example
allyway. A general part such asloader.jscould match other scripts too.Save and test
Save, clear your cache and test in a private window without accepting the banner.
Usercentrics
Check the Data Processing Services
In the Usercentrics Admin Interface, open Configuration, choose your configuration and go to Data Processing Services. Check whether allyWay appears there and whether it is marked as Essential.
Mark it Essential or exclude it from auto blocking
Mark allyWay as Essential. Or, if Usercentrics' auto blocking is on, exclude allyWay from it by adding
data-uc-allowedto its script tag:The allyWay code with the Usercentrics attribute <script data-uc-allowed src="https://app.allyway.ai/widget/YOUR-WEBSITE-ID/loader.js"></script>Then click Save Draft and Publish.
Check the script tag
On your website, make sure the allyWay script tag wasn't changed, for example to
type="text/plain"– that stops it from running.Publish and test
Publish, clear your cache and test in a private window without accepting.
Check that it works
Open your website in a private window and don't touch the banner: the allyWay button shows in its corner. To confirm the installation as well, see Check that allyWay is installed.
Does an extra attribute stop allyWay from recognizing my code?
No. Adding an attribute such as data-cookieconsent="ignore" doesn't stop allyWay from recognizing your code – only the address in src matters to us.
The widget still only appears after accepting. What else can I check?
If you added allyWay through a tag manager, its own consent settings apply too. For other causes, such as a cache or an optimization plugin, see The widget doesn't show.