Skip to content
CYBEXO Developer Docs

CYBEXO Debug Tool

Last updated: July 1, 2026

The CYBEXO Debug Tool validates CMP script health, Consent Mode ordering, TCF readiness, and runtime metadata on public pages.

1. Debug Entry Points

Section titled “1. Debug Entry Points”
  • ?cybexo_debug=1: run diagnostics and write the report to the browser console/runtime snapshot.
  • ?cybexo_debug_ui=1: open the on-screen debug overlay.

Example:

https://example.com/?cybexo_debug_ui=1

Console entry point:

window.cybexoDebugConsent?.()

Open overlay from console:

window.cybexoDebugConsent?.(true)

Legacy debug URLs may continue to work during customer migration, but new documentation and support tickets should use the CYBEXO names above.

2. What the Debug Tool Validates

Section titled “2. What the Debug Tool Validates”
  • Loader presence and runtime readiness.
  • Artifact metadata where available: version, build, channel, commit, and built timestamp.
  • Consent Mode v2 key presence and values:
    • ad_storage
    • analytics_storage
    • ad_user_data
    • ad_personalization
  • Consent ordering:
    • consent default exists
    • consent default appears before ordinary Google tag execution
  • TCF readiness:
    • __tcfapi presence
    • __tcfapiLocator presence
    • TCF event status metadata
  • Consent update visibility after user action.

3. Late Loading / Misconfiguration Detection

Section titled “3. Late Loading / Misconfiguration Detection”

The debug tool detects common implementation failures, including:

  • missing gtag("consent", "default", ...)
  • Google tag execution before consent default
  • missing TCF API or TCF locator
  • duplicate or conflicting loader setup

When detected, the overlay shows pass/fail status, issue codes, and remediation hints.

4. GTM vs Direct Script Remediation

Section titled “4. GTM vs Direct Script Remediation”

If the affected page uses Google Tag Manager:

If the affected page uses direct script or a CMS plugin:

  • follow Web Setup or the relevant CMS guide
  • confirm the loader is present exactly once
  • confirm Consent Mode defaults execute before ordinary Google tags

5. Evidence Collection

Section titled “5. Evidence Collection”

For audit records, capture:

  • debug report JSON
  • affected URL
  • browser and device details
  • Pulse report link
  • Tag Assistant screenshots when GTM is involved
Section titled “6. Related Pages”