Skip to content
CYBEXO Developer Docs

CYBEXO Runtime Suite Overview

Last updated: July 1, 2026

CYBEXO Consent Runtime is the core runtime that applies consent behavior.

CYBEXO Runtime Suite is the commercial package for deploying, verifying, and monitoring that runtime across web, CMS, tag-manager, and mobile surfaces.

What Is Included

Section titled “What Is Included”
Surface Public name Primary use
Web CYBEXO Web CMP Engine Direct loader deployment for websites and custom front ends
GTM CYBEXO GTM Consent Template Google Tag Manager deployment with Consent Initialization support
WordPress Cybexo CMP WordPress.org plugin for automatic loader injection and admin setup
Android Cybexo Android SDK Native Android consent runtime
iOS CybexoSDK Native iOS consent runtime distributed through CocoaPods
Verification CYBEXO Pulse Runtime scanning, report evidence, loader metadata, and install-surface detection
Control plane CYBEXO Command Center Runtime status, connected property state, and live verification handoff

Runtime Proof

Section titled “Runtime Proof”

Runtime Suite is designed to prove that a deployment is not only configured, but live.

CYBEXO Pulse and Command Center verify:

  • loader presence
  • CYBEXO brand identity
  • install surface, such as direct web, GTM, WordPress, Android, or iOS
  • loader version, build, channel, and commit where available
  • Google Consent Mode default/update behavior where applicable
  • canonical runtime event, debug, and storage markers where observable
  • public Pulse report URL for audit traceability

Standard Customer Evidence

Section titled “Standard Customer Evidence”

A successful runtime verification should show:

  • Runtime contract: pass
  • Brand: cybexo
  • Loader: https://cmp.cybexo.com/loader.js
  • Surface: wordpress, google_tag_manager, direct, android, or ios
  • Artifact version and Build
  • Pulse report URL
Section titled “Recommended Deployment Order”
  1. Create or confirm the customer Settings ID in CYBEXO.
  2. Install the correct runtime surface.
  3. Confirm the loader or SDK initializes once per page/app startup.
  4. Run Pulse verification.
  5. Confirm Command Center shows the property as verified.
  6. Keep the Pulse report URL with launch evidence.
Section titled “Related Guides”