Help

Troubleshooting

Fixes for the common problems: the banner doesn't show, a tracker still loads before consent, Consent Mode isn't detected, or visitors keep being asked again.

Most problems come down to the order of scripts, caching, or a second consent tool. Work through the section that matches what you see.

Before anything else, test in a private window. A normal window keeps your earlier choice, so the banner won't show and blocked tags may already be allowed.

The banner doesn't show

  1. Check the script is on the page. View the page source (not the developer tools Elements panel) and search for allowedit.com/c/. If it's missing, a cached copy may be served, or the code was added somewhere that isn't published. Purge your site's cache and your CDN.
  2. Check it's in the head, first. The tag should be above every other script. See Install the script.
  3. Check the domain. The banner only runs on the domain you added and its subdomains. On a staging site, a preview URL or a different domain it stays quiet. Add that domain as a site if you need the banner there.
  4. Check you haven't chosen already. Open the site in a private window, or delete the allowedit_consent cookie.
  5. Check your region rules. If the zone you're in is set to No banner, nothing shows. See Region rules.
  6. Check for an ad blocker. Some blockers hide consent banners. Try with extensions off.
  7. Check for another consent tool. A second banner, plugin or app can hide ours or remove it. Remove it.
  8. Check you published. Changes in the editor go live only after Publish.
  1. Check the order. Anything above the allowedit script in the head runs before it and can't be blocked. Move allowedit to the top.
  2. Check how it's loaded. Inline scripts (code inside a <script> tag with no src) can't be caught by URL. Mark them with type="text/plain" and data-category. See Block scripts manually.
  3. Add a rule. If the tracker isn't on the auto-blocking list, add a custom URL rule under Banner, then Blocking. See Auto-blocking and custom rules.
  4. Check optimisation plugins. Plugins that delay, combine or defer JavaScript can move scripts above ours or bundle them into one file. Exclude allowedit and your trackers from those features.
  5. Check Google tags. In Consent Mode's advanced mode, Google tags load before consent on purpose, in a denied state. They don't set analytics or ad cookies until the visitor allows them. Switch to basic mode if you want them held back entirely.
  6. Run a scan. The scanner flags every cookie set before consent and the page it was first seen on.
  1. Look for other defaults. A gtag('consent', 'default', ...) snippet left in your theme, or a Consent Mode template in Google Tag Manager, can override ours. Remove it, so only allowedit sets defaults.
  2. Check the order. The allowedit script must come before the GTM snippet and the Google tag. Don't load allowedit from inside GTM.
  3. Check it's on. In your dashboard, under Banner, check Google Consent Mode is turned on, then publish.
  4. Use Google's tools. Open GTM Preview and look at the Consent tab, or use Tag Assistant. You should see a default state before any tag fires, then an update after a choice.

Full setup: Google Consent Mode v2 and Google Tag Manager.

Visitors are asked again and again

  1. Cookies are blocked. If the browser blocks cookies on your site, the choice can't be saved.
  2. Different domains. A choice on example.com doesn't carry to example.co.uk or to a separate checkout domain. Subdomains of one domain share the choice.
  3. Short expiry. Check your consent expiry under Banner, then Behaviour. The default is 365 days.
  4. Version bumps. Ask visitors again raises the consent version, and everyone chooses again once. If you used it by mistake, visitors are asked one more time, then it settles.
  5. Something clears cookies. Some logout flows or privacy scripts clear every cookie, including ours.

More detail: The consent cookie.

Embeds show a placeholder after accepting

Blocked iframes load as soon as their category is allowed. If one stays blank, check its category matches what the visitor allowed, and that the iframe uses data-src rather than src.

The scan finds nothing, or fails

  • The site must be verified.
  • Pages behind a login aren't scanned.
  • A firewall or bot protection may block our scanner. Allow it, or check your security service's logs.

Still stuck?

Email support@allowedit.com with your site's address, the page where you see the problem and what you expected to happen. A screenshot of the browser's developer tools (Console and Network) helps us answer faster.

Still stuck? Email support@allowedit.com with your site's address and what you see.