Troubleshooting
The things that go wrong, in the order they usually do.
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.
A tracker still fires before consent
It is either hard-coded above the tag, or there is no rule for it.
- Blocking tab: is there a rule matching that script’s URL? Add one; the presets cover the common vendors.
- 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="…". - 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.