How to Troubleshoot a Consent Banner That Does Not Appear or Respond
If the Captain Compliance consent banner does not appear, appears twice, or does not respond to clicks, work through the checks below. Each one links to the article with the details.
Start with a clean test
Open a private or incognito browser window, so that no stored choice hides the banner.
Load the page and open browser developer tools.
Check the Console tab for errors and the Network tab for requests to
cptn.co.For more detail, add
?cc_debug=trueto the page address and reload. The banner script then writes its steps to the Console, in lines that start with[CC].
The banner does not appear
The script is missing, or it belongs to another domain. Each domain has its own script. Copy it again from the app and confirm it matches the domain. See How to Publish a Consent Banner on Your Website.
The page’s address is not the domain that the script was issued for. The script runs only on that domain, with or without www, and on subdomains that have been added in Captain Compliance. It does not run on staging, preview, or localhost addresses. With
?cc_debug=true, the Console shows an Unauthorized Domain message in this case.The script is not in the right place on your platform. See the installation guide for WordPress, Shopify, Webflow, Wix, Squarespace, HubSpot, or Next.js, React, and other single-page apps.
A Content Security Policy is blocking it. Look for Content Security Policy errors in the Console that mention
cptn.co. See How to Configure a Content Security Policy (CSP) for Captain Compliance.The page is excluded. In Google Tag Manager (GTM), check for exceptions on the Captain Compliance CMP tag. On direct installs, check for template logic that omits the script. See How to Exclude the Captain Compliance Consent Banner from Specific Pages.
In GTM, the tag is not firing. In Preview, the Captain Compliance CMP tag should fire on the Consent Initialization event. Also confirm that the container was published after testing. See How to Install and Configure the Captain Compliance CMP Template in GTM.
A cache is serving an older version of the page. Clear caching layers after installation.
A choice is already stored. The banner does not reappear once a visitor has chosen. It also stays hidden in the same browser tab until the tab is closed, even if you clear cookies. Use a private window, or reopen the settings from a footer link: see How to Add a “Cookie Preferences” Option to Your Website Footer.
The banner appears twice
The script is installed both directly and through GTM. Keep only one. See How to Publish a Consent Banner on Your Website.
Two Captain Compliance CMP tags match the same hostname in a shared container. See How to Deploy Multiple Consent Banners from One GTM Container.
On Shopify, the native Shopify cookie banner is still enabled. See How to Integrate Captain Compliance with Shopify.
On Wix, Squarespace, or HubSpot, the platform’s own cookie banner is still enabled. See the installation guide for Wix, Squarespace, or HubSpot.
The banner appears but does not respond
On WordPress sites that use WP Rocket, the Delay JavaScript Execution feature can freeze the banner’s buttons. See How to Resolve WP Rocket Caching Issues With Captain Compliance.
Other script-optimization tools can cause similar timing conflicts. On direct installs, deferred mode changes when the script runs and can help when you troubleshoot timing issues. See How to Publish a Consent Banner on Your Website.
The banner works, but tags still fire after Reject
The banner records consent. Each tag or script must also be set up to respect it.
GTM tags left at Not set fire regardless of consent. See How to Gate GTM Tags with Native Consent Settings.
Early-loading tags can be evaluated before the visitor’s consent state is known. See How to Fire Early-Loading Tags After Consent with CC - Consent Ready.
Hard-coded and inline scripts are not controlled by GTM. See How to Gate Non-Essential Scripts and Beacons Using Explicit Consent Logic.
Tools that are already running keep identifiers in browser storage. See How to Clear Local & Session Storage on Tracking Opt-Out (Beyond Cookies).
Links to your privacy notice do nothing
If links that include a # anchor appear dead, a smooth-scroll script on your site may be intercepting them. See How to Resolve Anchor Link Conflicts with Smooth-Scroll Scripts.
Still stuck?
Contact your Captain Compliance representative, or submit a request. Include the page URL, the browser you used, and any Console errors.
