CYBEXO Consent Diagnostics
Last updated: October 7, 2026 · Web CMP 1.5.33
CYBEXO Consent Diagnostics is an opt-in, read-only panel on your website. It shows the consent commands retained in the current page, configuration readiness, applicable TCF readiness, and practical next steps. It does not change a visitor’s choices or send the diagnostic report automatically.
Open diagnostics
Section titled “Open diagnostics”Open https://your-website.com/consent-debugging. Web CMP 1.5.33 automatically opens diagnostics at this exact path (with or without a trailing slash).
Your website must serve a normal page at that route, including its existing CYBEXO installation and Google tags in their normal order. Create a page with the slug consent-debugging, or configure an internal rewrite that preserves this address. Use the site’s ordinary template; do not add a second CMP script or a special consent state. The runtime cannot create a server route. If the address returns a bare 404 without the CMP, configure the route first.
For a static host supporting _redirects, an example internal rewrite is:
/consent-debugging /index.html 200/consent-debugging/ /index.html 200Use your platform’s corresponding page or routing feature. Some platforms reserve root paths; where a root route cannot be created, use the query entry point below. A debugging route shows evidence for that page only. Also inspect actual landing pages, whose scripts or ordering may differ.
For any existing page, add cybexo_debug_ui=1:
https://example.com/?cybexo_debug_ui=1https://example.com/products?category=books&cybexo_debug_ui=1You can also open the panel from the browser console:
window.cybexoDebugConsent?.(true)For a report object without the panel, call window.cybexoDebugConsent?.(). The cybexo_debug=1 query parameter writes an initial snapshot to the console; it may still show loading. Refresh the report after the CMP is ready. Existing nxgDebugConsent integrations remain compatible.
The panel updates while open. Refresh takes another snapshot; Minimize reduces the panel; Close stops its observer. While privacy choices are open, diagnostics remain visible beside the consent dialog on wider screens and above it on smaller screens. Both panes remain scrollable and share keyboard navigation. Closing diagnostics restores the normal consent layout.
If the loader never runs, the panel cannot open. Check the script request, Content Security Policy, browser console and extension blocking first. Use Tag Assistant and Pulse to investigate beyond the panel.
Read the result
Section titled “Read the result”| Result | Meaning | What to do |
|---|---|---|
| Needs attention | An observable issue exists, such as incomplete defaults, a late direct command, or failed configuration delivery. | Follow the finding’s repair guidance, reload, and repeat the test. |
| Needs verification | The observer cannot determine the effective behavior, for example native GTM consent APIs or regional precedence. | Inspect the consent events and tag behavior in Tag Assistant. |
| Waiting for evidence | Configuration, TCF readiness or a visitor choice is still pending. | Complete the relevant step and inspect again. A missing update before a choice is not a failure. |
| Commands observed | The available direct command checks have the expected structure. | Confirm the values match the visitor’s choice, then verify actual tag behavior. This is not certification. |
| Consent Mode off | The verified configuration deliberately disables the CYBEXO Consent Mode integration. | Check whether this is intended. An off integration does not establish a Consent Mode implementation. |
The table lists ad_storage, analytics_storage, ad_user_data and ad_personalization. Default means retained direct global defaults; Latest updates means retained direct global update values. Missing values are shown as Not observed, never assumed granted. The report separately identifies CMP intent, which is not proof of Google reception.
The expandable command timeline shows queue positions, not execution timestamps. It is limited to the latest 120 relevant entries and reports omitted entries. It does not include arbitrary event payloads.
Diagnose and repair findings
Section titled “Diagnose and repair findings”Consent defaults were queued late
Section titled “Consent defaults were queued late”The observer found a Google measurement command before all four direct defaults were available. First establish whether the affected tag uses Google tag gateway. Follow the Google tag gateway verification and remediation guide when applicable.
For a direct integration, initialize all four defaults before Google measurement commands. For GTM, use the appropriate native consent template on Consent Initialization — All Pages. Do not add competing direct defaults to a native GTM setup. Publish the correction and inspect the earliest consent event in Tag Assistant.
Native GTM or regional consent values
Section titled “Native GTM or regional consent values”Native GTM consent APIs are not reliably represented by direct gtag queue entries. Regional defaults also require evaluating which rules apply. Missing direct entries in these contexts require verification; they do not establish a missing default.
Use Google’s consent debugging procedure to inspect defaults, updates, built-in and additional consent checks, and the tag’s actual behavior. Repeat the relevant regional cases.
Missing or differing updates
Section titled “Missing or differing updates”Before a visitor choice, an update may not exist. After a completed choice, inspect all four values. If the CMP’s reported intent differs from the queued values, wait for saving to finish, then investigate duplicate integrations or competing consent commands. A difference requires verification; the panel cannot identify Google’s effective state by itself.
Configuration, TCF or duplicate installation findings
Section titled “Configuration, TCF or duplicate installation findings”Check the indicated delivery or bootstrap error and reload after repairing it. TCF readiness is required only when the verified page configuration uses TCF; non-TCF contexts are labelled Not applicable. A TCF stub alone is not readiness, and a loaded API does not prove full TCF policy compliance.
Multiple loader elements are a reason to inspect the page integration; their presence alone does not prove multiple executions. Use one supported integration path and verify it in the browser.
Test a complete visitor journey
Section titled “Test a complete visitor journey”- Use a fresh test session and inspect the defaults before making a choice.
- Accept all and verify the intended four updated values.
- Make a mixed choice and check that denied categories remain denied.
- Reject or withdraw optional consent and verify the updated values.
- Reload and navigate to another relevant page to check saved-choice restoration.
- Repeat with the relevant region and integration type. Use Tag Assistant to verify actual tag behavior and browser networking to investigate delivery.
Follow the Consent Mode v2 verification guide for the Google checks. Use Pulse for discovered-page coverage and recurring monitoring. A single page’s diagnostic result does not establish coverage of every landing page.
Save evidence safely
Section titled “Save evidence safely”Copy report and Download produce a JSON report with schema cybexo.consent_debug.v2, timestamp, runtime version, page origin, contextual findings, safe consent values and the bounded command timeline. Browser clipboard or download permissions may apply; if Copy is unavailable, use Download.
The export omits cookie values, TC strings, personal identifiers, arbitrary event payloads, full page paths, query parameters and fragments. Review the file before sharing it with support. Keep a separate note of the tested page, choice and region when those details are needed for your investigation.
What this tool cannot prove
Section titled “What this tool cannot prove”The panel cannot certify Google or IAB compliance, confirm Google reception, establish Google tag gateway enrollment, inspect every iframe, prove actual tag execution, or audit all landing pages. Use its findings to guide repairs and combine them with Tag Assistant and the relevant integration tests. Google’s own diagnostics remain the authority for the Google tag behavior they expose.