Check that the banner works
This page explains how to check the banner after installation and how to find the cause if it does not appear.
The v2 banner has no window.Avacy and writes console messages with the [avacy-loader-v2] prefix (see [avacy-loader-v2] messages). If you don't know which banner your site uses, read Which banner your site is using.
Prerequisites
Before you start, check that:
- the snippet is in the site's
<head>, as in HTML snippet or in your platform's page; - the web space banner is published in the dashboard.
Steps
- Open the site in a private window, which starts with no saved consents.
- Wait for the page to finish loading. The banner appears on the page.
- Open the developer tools console.
- Type
window.Avacyand press Enter. The console shows an object. - Type
window.Avacy.versionand press Enter. The console shows the banner version. - Look for messages starting with
[avacy-loader]. On a working site there are none.
Check
window.Avacy exists only after the banner has started, and right after loading it may still be empty. Try again after a few seconds.
After a visitor makes a choice, the banner no longer appears and, if the web space has one, the preferences icon appears. This is why you run the check in a private window.
Common problems
The banner does not appear
| Cause | How to recognize it (console or page) | What to do |
|---|---|---|
| Wrong web space code, or banner not published | banner.json not loaded … (HTTP 404) | Copy the snippet again from the dashboard and check that the banner is published |
| The CSP blocks the configuration | banner.json not loaded … (TypeError: Failed to fetch) and a CSP error | Allow the addresses described in HTML snippet |
| The CSP blocks the styles | No banner and the warning "The banner styles were blocked by the Content-Security-Policy…" | Put the nonce on the snippet, as in HTML snippet |
| The CSP with nonce blocks the banner | No banner and a CSP error on script-src | Put the site's nonce on the snippet, as in HTML snippet |
| Cached page | The site still shows the page without the snippet | Clear the site or theme cache and reload the page |
| Consent already saved in the browser | The preferences icon appears, not the banner | Try in a private window |
The snippet is on the page twice
Two identical snippets produce a single banner and no errors, but the page loads the loader twice. Keep only one snippet per page.
The banner does not change after an edit in the dashboard
The CDN may serve the previous configuration for a few minutes. Wait and reload the page without cache.
"Accept cookies" does not close the banner and a warning appears
With TCF enabled, the banner downloads the IAB vendor list when the visitor makes a choice. If the download fails, the banner saves no consent and shows "Something went wrong: your choice could not be saved. Please try again later.".
| Cause | How to recognize it (console) | What to do |
|---|---|---|
The CSP blocks assets.avacy-cdn.com | [Avacy] The site's Content Security Policy blocks … and a CSP error | Allow the addresses described in HTML snippet |
| The network or a browser extension blocks the download | [Avacy] The IAB vendor list could not be downloaded from … | Check the network and disable the extensions that block requests |
Reject all, the X and Continue without accepting never block the visitor: if the download fails, the banner closes until the end of the browser session without saving any consent. In the next session the banner appears again.
[avacy-loader] console messages
The loader writes its messages in English.
| Message | Type | What it means | What to do |
|---|---|---|---|
[avacy-loader] no ?webspace= in the install tag; the banner is not served. | error | The snippet does not contain webspace. The banner does not start. | Copy the full snippet from the dashboard. |
[avacy-loader] banner.json not loaded from <address> (<reason>); the banner is not served. | error | The loader did not download the web space configuration. The banner does not start. | Read the reason in brackets, explained below. |
[avacy-loader] '<name>' is not part of this release; ignored. | warning | The configuration requests an add-on that this version does not include. The loader ignores it. | Write to Avacy support with the add-on name. |
[avacy-loader] add-on '<name>' failed to load (<reason>). | error | The loader did not load an add-on, for example preemptive blocking or the consent archive. | Check the network and the CSP. If the reason is no definition named '<name>' as default export, write to support. |
[avacy-loader] boot failed | error | Startup stopped. The console shows the error right after the message. | Copy the error and write to support. |
[avacy-loader] cannot find its own <script> tag. | error | The loader cannot find its own tag. This happens with a module tag whose address does not contain webspace=. | Paste the dashboard snippet without changing it. |
The reason in the banner.json not loaded message can be one of these.
| Reason | Meaning |
|---|---|
HTTP 404 or HTTP 403 | The CDN cannot find the configuration. The web space code is wrong, or the banner is not published or is turned off. |
not an object | The downloaded file is not a valid configuration. |
SyntaxError: … | The downloaded file is not valid JSON. |
TypeError: Failed to fetch | The request did not go through, because of the network, a CSP block or a browser extension. |
[avacy-loader-v2] messages
A site with the v2 banner and the Avacy snippet writes messages with the [avacy-loader-v2] prefix.
| Message | Type |
|---|---|
[avacy-loader-v2] oil is already on this page; ignored. | warning |
[avacy-loader-v2] #oil-configuration is on the page: oil follows its data-remote-config, not ?webspace=. | warning |
[avacy-loader-v2] no ?webspace= in the install tag; the banner is not served. | error |
[avacy-loader-v2] cannot find its own <script> tag. | error |
Other banner messages
| Message | What it means |
|---|---|
[Avacy] Google tags ran before the Consent Mode default or the TCF stub … | A Google tag ran before the banner. Read Google tag order and debug mode. |
Last updated: 30/10/2026.