Runtime Verification
Last updated: November 20, 2026
Use this guide to confirm that a CYBEXO Runtime Suite installation is live and producing customer-safe evidence.
Verification Targets
Section titled “Verification Targets”| Check | Passing evidence |
|---|---|
| Runtime loader | https://cmp.cybexo.com/loader.js is present on the page |
| Script identity | script id is cybexo-cmp for direct web and supported CMS surfaces |
| Settings ID | the loader has the customer Settings ID |
| Install surface | The published template, container, plugin or app build identifies the installation method |
| Runtime contract | The browser or app initializes the integration and the observed tag or SDK behavior matches the tested visitor choices |
| Version traceability | The deployment record identifies the installed version. An exact Pulse web page check may also return metadata for a directly linked loader |
| Google Consent Mode | default consent is initialized before marketing or analytics tags run |
| Report trace | The launch record links the dated source report and the separate interaction test |
Browser Checks
Section titled “Browser Checks”Run these checks in the browser console on the customer site.
Loader
Section titled “Loader”document.getElementById("cybexo-cmp")performance .getEntriesByType("resource") .filter((entry) => entry.name.includes("cmp.cybexo.com/loader.js"))Google Consent Mode
Section titled “Google Consent Mode”(window.dataLayer || []).filter( (entry) => Array.isArray(entry) && entry[0] === "consent" && (entry[1] === "default" || entry[1] === "update"))Expected result:
- a
defaultconsent command appears before tags that require consent - an
updateconsent command appears after the visitor makes a choice
Public API
Section titled “Public API”typeof window.initCybexoCMPtypeof window.cybexoReportConversionThese APIs may be unavailable on pages that use a managed integration which initializes CYBEXO internally.
Pulse Verification
Section titled “Pulse Verification”Open CYBEXO Pulse at https://pulse.cybexo.com/ and scan the customer domain.
The public scanner uses the same-origin API path:
https://pulse.cybexo.com/v2/public-scanThe compatibility API path https://api.cybexo.io/v2/public-scan remains available for API clients, but browser-based public scans should prefer the Pulse same-origin path.
Read the scan time, requested page or site scope, number of URLs found and checked, and each page’s findings. An unreadable page or an undetermined rule needs follow-up. If a direct CYBEXO loader was inspected, the report can also include its metadata. The Pulse rule catalog describes each result.
Use Download evidence JSON to retain this source observation with the release record. Record any actual browser or app interaction in its own test result.
Command Center Verification
Section titled “Command Center Verification”For a connected property, confirm the intended domain or app and inspect the time of its latest runtime evidence. Match received events to the consent choices you exercised. A saved Pulse report describes its own method and observation time.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Likely cause | Next check |
|---|---|---|
| No loader detected | loader is not installed, blocked by CSP, or injected too late | Check page source and network tab |
| Duplicate banner | multiple install surfaces are active | Confirm direct script and GTM are not both loading CYBEXO |
| Consent Mode missing | tag order is wrong or consent bootstrap is disabled | Use Tag Assistant and the dataLayer check |
| Pulse report has no version/build | loader could not be fetched or inspected | Check network access to cmp.cybexo.com/loader.js |
| Command Center not verified | the property has no matching runtime observation | Confirm the property connection, exercise the integration and check for a newly received event |