Troubleshooting

The banner does not show on my site

First, open the site in the ConsentLayer dashboard. If the banner was blocked on a host because that host is not in the site's domain list, the site dashboard shows a notice:

Your banner is blocked on <host> because it is not in your domain list.

If the host is yours, click Add domain. If it is not, dismiss it in Site → Settings → Domains, under Blocked recently. The installation check also names blocked hosts, and it reports domain_not_listed when your domain redirects to a host that is not on the list.

If the dashboard shows no notice, open the page, open the browser's developer tools (F12, or Cmd+Option+J on a Mac), and read the Console tab. Find the line that starts with [ConsentLayer].

The console says the domain is not on the site's list

[ConsentLayer] The banner is off on "<host>" because this domain is not on the site's list. Add it in ConsentLayer → Site settings → Domains.

The banner runs only on the hosts in its site's domain list. On this host it does nothing, so trackers on the page are not held.

Fix: add the quoted host to the site.

• Dashboard: click Add domain on the site dashboard notice, or Add in Site → Settings → Domains → Blocked recently. You can also type the host in the domain list. Then reload the page.
• Agent: "Add <host> to my <site> site in ConsentLayer." The agent also sees blocked hosts in check_installation and list_sites (blocked_hosts). It asks you whether each host is yours before it calls add_site_domain.

Staging and preview hosts (subdomains of your domain, localhost, and hosts such as my-app.vercel.app) are free on every plan. If the host is a different website and not a copy, set it up as its own site instead. See Domains and staging.

The console says "No configuration found."

The script loaded, but it has no banner configuration. Check that the project key in the snippet matches a site in your dashboard. Copy the snippet again from Site → Settings → Installation.

There is no [ConsentLayer] line at all

The script did not load. Check that the tag is in the <head> of the page you opened (view the page source), that it has no defer and no async, and that you deployed the change. Your agent can check this with check_installation.