Skip to content
CYBEXO Developer Docs

Troubleshooting Playbook

Last updated: July 1, 2026

This playbook provides symptom -> cause -> verification -> fix guidance for CYBEXO Runtime Suite.

1. Banner Not Showing

Section titled “1. Banner Not Showing”

This can be expected in non-banner regions depending on policy and region mapping.

How to confirm runtime presence:

document.querySelector("#cybexo-cmp")
performance.getEntriesByType("resource").filter(r => r.name.includes("cmp.cybexo.com/loader.js"))

Common fixes:

  • verify Settings ID
  • test in incognito or reset consent
  • allowlist CYBEXO domains in CSP
  • confirm only one loader integration path is active
  • validate region policy in Command Center
Section titled “2. Tags Fire Before Consent Default”

How to confirm:

(window.dataLayer || []).filter(e => Array.isArray(e) && e[0] === "consent")

Common fixes:

  • if using GTM, move CYBEXO CMP to Consent Initialization - All Pages
  • remove duplicate consent default commands
  • move direct script earlier than ordinary Google tags
Section titled “3. Consent Not Updating After User Action”

How to confirm:

(window.dataLayer || []).filter(x => x && x[0] === "consent" && x[1] === "update").at(-1)

Common fixes:

  • check browser console errors
  • inspect network requests to CYBEXO endpoints
  • clear page/CDN cache and retest
  • verify no custom script prevents the banner callback

4. Duplicate Banner

Section titled “4. Duplicate Banner”

How to confirm:

document.querySelectorAll("#cybexo-cmp").length

Common fixes:

  • keep only one path: direct script, GTM, WordPress, Shopify, or Drupal
  • remove stale theme embeds or tag-manager copies

5. TCF API Missing

Section titled “5. TCF API Missing”

How to confirm:

typeof window.__tcfapi

Common fixes:

  • confirm loader loaded successfully
  • check CSP/ad-blocker interference
  • verify IAB TCF is enabled for the property where required

6. Debug Overlay

Section titled “6. Debug Overlay”

Use:

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

Or from console:

window.cybexoDebugConsent?.(true)

7. iOS Pod Version Not Found

Section titled “7. iOS Pod Version Not Found”

Symptoms:

  • CocoaPods could not find compatible versions for pod "CybexoSDK"

Common fixes:

Terminal window
pod install --repo-update
Terminal window
pod trunk info CybexoSDK

If a new version was just released, allow time for CocoaPods CDN propagation and retry.

8. Android SDK Version Not Found

Section titled “8. Android SDK Version Not Found”

Symptoms:

  • Could not find com.cybexo:android-sdk:x.y.z

Common fixes:

Terminal window
./gradlew --refresh-dependencies :app:assembleDebug

Confirm mavenCentral() is present in repository settings.

9. WordPress Runtime Not Detected

Section titled “9. WordPress Runtime Not Detected”

How to confirm:

document.getElementById("cybexo-cmp")
fetch("/wp-json/cybexo-cmp/v1/wpca-status").then(r => r.json()).then(console.log)

Common fixes:

  • verify Cybexo CMP plugin is active
  • confirm Auto-inject CMP Script is enabled
  • purge page/CDN cache
  • remove manual duplicate loader snippets

10. Shopify Customer Privacy Not Updating

Section titled “10. Shopify Customer Privacy Not Updating”

How to confirm:

typeof window.Shopify?.customerPrivacy?.setTrackingConsent
window.Shopify?.customerPrivacy?.currentVisitorConsent?.()

Common fixes:

  • confirm managed Shopify integration requirements
  • keep only one injection path
  • retest on a published storefront in incognito

11. Pulse Scanner Cannot Be Reached

Section titled “11. Pulse Scanner Cannot Be Reached”

Symptoms:

  • CYBEXO Pulse shows that the scanner is temporarily unavailable
  • the browser reports a network failure while starting a scan

Common fixes:

  • retry after a short delay
  • test from another network if a VPN, firewall, or privacy extension is active
  • confirm https://pulse.cybexo.com/v2/public-scan/healthz returns ok: true
  • use the same-origin Pulse scanner at https://pulse.cybexo.com/

12. What to Send Support

Section titled “12. What to Send Support”
  • production URL
  • Settings ID
  • Pulse report link
  • Command Center runtime status screenshot
  • debug report JSON
  • browser/device details
  • Tag Assistant screenshots for GTM issues
Section titled “13. Related Docs”