CYBEXO Debug Tool

Last updated: April 27, 2026

The CYBEXO Debug Tool is the implementation validation surface for CMP script health, Consent Mode ordering, and TCF runtime readiness on public pages.

1. Debug Entry Points

?nxg_debug=1: runs diagnostics in background and writes result to console/runtime snapshot.

?nxg_debug_ui=1: opens on-screen debug overlay with pass/fail status, issue list, and remediation hints.

Example:

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

Console entry points:

Returns the current diagnostic report object.

Opens the debug overlay and returns the same report object.

2. What the Debug Tool Validates

Consent Mode v2 key presence and values:

ad_storage

analytics_storage

ad_user_data

ad_personalization

Consent ordering:

whether consent default is present

whether consent default appears before Google tag execution

TCF readiness:

__tcfapi presence

__tcfapiLocator presence

TCF event status metadata

CMP runtime signals:

detected developer ID

consent sync/update event visibility

3. Late Loading / Misconfiguration Detection

The debug tool explicitly detects late or misconfigured consent setup, including:

Consent default missing (No gtag("consent","default", ...) found)

Consent defaults not set before tags

gtag("js") or gtag("config") observed before consent default

Missing TCF API or missing TCF locator iframe

When detected, the debug overlay shows:

Header: NXG Consent Audit: ATTENTION NEEDED

Late/Misconfigured: DETECTED

issue codes and human-readable details

actionable hints to correct ordering

4. GTM vs Direct gtag.js Remediation Routing

If the affected page uses Google Tag Manager:

Follow Google Tag Manager (GTM) Template Guide

Ensure CMP tag fires on Consent Initialization - All Pages

Re-test in Tag Assistant after publish

If the affected page uses direct gtag.js integration:

Follow Google Consent Mode v2 Validation

Ensure consent defaults execute before any Google tag config calls

This routing is required so late-load findings point customers to the correct implementation path.

5. Proactive Alert Flow

CYBEXO uses two complementary surfaces:

Debug Tool (on-page): customer-visible pass/fail and remediation hints.

Pulse Monitoring (continuous): scheduled checks on configured public URLs to detect regressions in CMP load and consent ordering.

When misconfiguration is detected, customers are alerted and directed to the relevant implementation documentation above.

6. Audit Evidence Collection

For Google CMP Partner Program evidence, capture both states:

Misconfigured case:

debug overlay showing ATTENTION NEEDED

visible late/misconfigured details

Fixed case:

debug overlay showing PASS

corrected ordering and consent visibility

Recommended attachments:

debug report JSON (from Copy report)

affected URL

Settings ID

browser/version

Tag Assistant screenshots (if GTM-managed)

Google Tag Manager (GTM) Template Guide

Google Consent Mode v2 Validation

Troubleshooting Playbook

1. Debug Entry Points#

2. What the Debug Tool Validates#

3. Late Loading / Misconfiguration Detection#

4. GTM vs Direct gtag.js Remediation Routing#

5. Proactive Alert Flow#

6. Audit Evidence Collection#