c15t
Deploy on Inth

HTML Verify and troubleshoot

Troubleshooting

Add the DevTools tag next to the c15t tag while you debug. The panel shows consent state, gated scripts, the resolved policy and every event, and its Location tab tries the policy for another country. See DevTools for the tag and its attributes. Remove the tag before you publish.

Why is there no banner?

Check. In the Network tab, find the request to your backend's /init endpoint.

Fix. Act on what you find:

  • The request failed with a CORS error. Add your site's exact origin, including https:// and any www, to the trusted origins in your Inth project.
  • The request returned 200. The policy for your location may not ask for a banner. Many policies show none outside regions with consent laws. Open the DevTools Location tab and try a country such as DE.
  • There is no request. The tag did not run. Check that the src loads, that no other script on the page threw first, and that the tag has no data-manual. A Content Security Policy must allow the CDN in script-src and your backend in connect-src; see Content Security Policy.
  • You already chose. A stored choice hides the banner. Open a private window, or clear the c15t cookie and localStorage key.

Why does a vendor script run before a choice?

Check. Search the page source for the vendor's domain. The script tag only holds scripts that are type="text/plain" with a data-c15t-category. A second copy added by a theme setting, a plugin or a tag manager runs on its own terms.

Fix. Remove the second copy, or gate it too.

Check. View the published page's source and check that each gated tag still has type="text/plain". A caching or optimization plugin can rewrite a gated tag's type or move it.

Fix. Follow caching and optimization plugins.

Check the category as well. Under an opt-out policy, optional categories are allowed until the visitor refuses, so vendors load on the first visit by design.

Why does a gated script never run on a page with a nonce?

Check. When the c15t tag has a nonce or data-nonce, c15t runs only gated text/plain tags that carry the same nonce. Open the console and look for a warning that c15t skipped a data-c15t-category script, and check the tag in the Elements panel for data-c15t-activated="untrusted".

Fix. Add nonce="RANDOM_PER_RESPONSE", with the value your server sends, to the tag, including tags your own code inserts later. See gated tags on a page with a nonce.

Why is the banner unstyled or missing its colors?

Check. The console shows a CSP violation. A Content Security Policy whose style-src does not allow the stock UI's <style> element blocks it.

Fix. Put the nonce from your style-src on the c15t tag, as nonce or data-nonce, or serve the stylesheet as a file as Content Security Policy describes.

Check. Confirm that the link's href ends in #c15t-preferences and that the page loads the c15t tag. With c15t.headless.js or ui: { dialog: false }, the link asks for the dialog but nothing renders it.

Fix. Correct the href or add the c15t tag. With a headless setup, your page must render its own dialog, as headless shows.

Why does the console say "call c15t.init() first"?

Check. Something called a window.c15t method directly before the client existed, for example from an inline script that ran before the tag, or on a page whose tag has data-manual before anything called c15t.init().

Fix. Queue the call with c15t.push(), move it into an on('ready', ...) listener, or wait for c15t.ready(). See which calls you can queue.

Why does the console say a queued call "was skipped"?

Check. c15t.push() received a method it does not queue, such as has, getSnapshot or dispose, or a name c15t does not know. A queue cannot hand a value back, so c15t skips the call.

Fix. Call those methods inside c15t.onInit() or after c15t.ready().

Why is my queued configuration ignored?

Check. Look for an inline script that assigns window.c15t = [...]. Assignment replaces calls other scripts queued before it.

Fix. Use window.c15t = window.c15t || [] followed by c15t.push(...) everywhere.

Check. Look for a config call made after the bundle ran. It does nothing.

Fix. Run the config call before the tag, or pass the configuration to c15t.init() with data-manual.

Why does the page throw "Load c15t.iab.js instead of c15t.js"?

Check. Two c15t bundles are on the page, including copies a plugin adds.

Fix. Keep only c15t.iab.js for an IAB policy, and remove c15t.js, c15t.offline.js or c15t.headless.js.

Why did the banner change after a release?

Check. @alpha in the tag's URL follows the newest prerelease.

Fix. Replace it with an exact version so your page changes only when you change it.

More help

Troubleshoot consent covers problems shared by every framework, such as a missing banner, analytics that load before a choice, imports that fail because npm installed c15t v2, choices that disappear on reload, server HTML that differs from the browser, static builds that fail and content blockers that hide the consent UI.