Guide

Troubleshooting

The things that go wrong, in the order they usually do.

  1. Getting help
  2. The banner does not show
  3. A tracker still fires before consent
  4. Consent logs are empty
  5. Publish is refused

Getting help

Write to support@cmpstack.io.

Email. Write to support@cmpstack.io. Say which workspace and which domain, and paste the line the tag prints in the browser console if the question is about a banner — it usually answers it.

The banner does not show

Almost always one of: not verified, not published, tag not on the page, or a stored decision.

  1. Domains: is the row Verified? An unverified domain is served no banner.
  2. Banner Management: is the banner Published, not just saved?
  3. View the page source: is the tag in <head> with the right Site ID? A cached page or a CDN in front of the site may still be serving the old HTML.
  4. Open a private window. A stored decision hides the banner for 12 months; a private window has none. The preferences control (bottom-left) is still there for anyone who decided.
  5. Open the browser console. The tag says why in one line, prefixed [cmpstack]: a missing Site ID, an unregistered site, a duplicate tag.

A tracker still fires before consent

It is either hard-coded above the tag, or there is no rule for it.

  1. Blocking tab: is there a rule matching that script’s URL? Add one; the presets cover the common vendors.
  2. View source: is the script above our tag in the page? Then it ran before we could hold it. Mark it with type="text/plain" data-cmp="…".
  3. On WordPress, another plugin may print its script before ours. Our plugin hooks in first, but a theme that hard-codes a script into its header still needs marking.

Consent logs are empty

The tag records only on a verified domain with a published banner, and only when someone actually decides.

Check the same three things as for a missing banner: verified, published, tag on the page. Then make a decision yourself in a private window; it appears within seconds. If the banner shows but nothing is recorded, an ad blocker or a strict browser privacy setting on that device may be dropping the request to our API; try another browser before assuming the site is wrong.

Publish is refused

The message names the reason: past the plan allowance, or a feature the plan does not include.

A domain past the plan allowance cannot be published until you upgrade or remove a domain you added earlier. A draft using custom CSS or hiding the branding on a plan without those is refused at save with the plan that has them named. In both cases the draft is kept exactly as you left it.