Get help faster: the Debugging panel

When something isn’t behaving — a banner that won’t appear, a script that loads when it shouldn’t, a setting that seems ignored — the fastest path to a fix is sending us a debug snapshot. It gives our support team the exact picture of your configuration in one paste, instead of five rounds of “which version are you on?” emails.

Where to find it

Open the Logs tab and expand the Debugging section at the bottom. You’ll see a text area containing a JSON snapshot of your configuration, generated fresh on each page load.

What the snapshot contains

• Site environment — CoreConsent version (and Pro version if installed), WordPress and PHP versions, active theme, whether the site is multisite, the site URL, and the list of active plugins (a frequent source of conflicts, which is why it’s included).
• License state — your plan and whether Pro features are enabled. Your license key is never included.
• Plugin settings — your full CoreConsent configuration: services, banner options, styling, and so on.
• Pro sections (when Pro is active) — Script Manager entries and scanner findings, so we can see how your trackers are wired up.

What it deliberately leaves out

The snapshot contains no consent-log entries, no IP addresses, and no visitor data — it describes your configuration, not your visitors. You can share it with us (or post it in a forum) without exposing anyone’s personal information.

One nuance: by default, Script Manager entries include only metadata about your custom scripts (name, position, length, a checksum) — not the script code itself. If your issue involves a script’s actual behavior, tick “Include script bodies (may contain tracking/pixel IDs)” before copying. It’s opt-in because script code often embeds your analytics or ad-pixel IDs, and you should share those knowingly rather than by default.

Sending it to support

1. Reproduce the problem first if you can, and note the steps — the snapshot tells us your configuration, but your description tells us what went wrong.
2. In the Debugging section, decide whether to tick Include script bodies (see above).
3. Use one of the three buttons:
   • Copy — puts the JSON on your clipboard, ready to paste.
   • Download .json — saves it as a file, better for large configurations or attaching to an email.
   • Send to support — opens our contact form in a new tab.
4. In the support form, describe: what you expected, what actually happened, the steps to reproduce, and paste or attach the snapshot. (The form doesn’t receive the snapshot automatically — attaching it is the step people most often miss.)

That’s it. A report with a snapshot plus reproduction steps typically gets a useful first response instead of a clarifying question.

FAQ