Skip to content
CYBEXO Developer Docs

Runtime Suite Install and Verify

Last updated: July 2, 2026

Use this guide to choose one CYBEXO Runtime Suite installation path, publish it safely, and verify the live runtime with CYBEXO Pulse.

1. Choose One Install Surface

Section titled “1. Choose One Install Surface”

Install CYBEXO through one primary surface per page or app startup.

Surface Use when Detailed guide
Web CMP Engine You control the website template or application shell. Web Setup
GTM Consent Template You deploy consent through Google Tag Manager. Google Tag Manager (GTM) Template Guide
WordPress Plugin The site runs WordPress and should use plugin-managed injection. WordPress Integration
Android SDK The product is a native Android app. Android Setup
iOS SDK The product is a native iOS app. iOS Setup

Do not deploy multiple web loaders on the same page unless CYBEXO support has reviewed the design.

2. Direct Web Install

Section titled “2. Direct Web Install”

Add the loader as high as possible in the page <head>.

<script
  id="cybexo-cmp"
  data-settings-id="YOUR_SETTINGS_ID"
  src="https://cmp.cybexo.com/loader.js">
</script>

Minimum verification:

  • one script with id="cybexo-cmp"
  • one network request to https://cmp.cybexo.com/loader.js
  • banner and preferences behavior match the configured policy
  • Consent Mode default/update behavior appears where enabled

3. GTM Install

Section titled “3. GTM Install”
  1. Add CYBEXO GTM Consent Template from the GTM Community Template Gallery.
  2. Create a CYBEXO CMP tag.
  3. Enter the customer Settings ID.
  4. Use Consent Initialization - All Pages.
  5. Preview, validate, and publish.

Minimum verification:

  • CYBEXO CMP tag fires on Consent Initialization
  • Google Consent Mode v2 keys are present before ordinary tags run
  • network request to https://cmp.cybexo.com/loader.js
  • Pulse detects GTM where observable

4. WordPress Install

Section titled “4. WordPress Install”
  1. In WordPress Admin, open Plugins -> Add New.
  2. Search for Cybexo CMP.
  3. Install and activate the plugin.
  4. Enter the customer Settings ID.
  5. Keep auto-injection enabled unless another approved install path owns the loader.

Minimum verification:

  • one front-end script with id="cybexo-cmp"
  • loader URL is https://cmp.cybexo.com/loader.js
  • Pulse detects WordPress where observable
  • plugin admin settings match the production Settings ID

5. Android Install

Section titled “5. Android Install”

Add the dependency from Maven Central:

dependencies {
    implementation("com.cybexo:android-sdk:1.0.0")
}

Initialize once from an Activity:

import com.cybexo.cmp.CybexoCMP


CybexoCMP.initialize(activity, "YOUR_SETTINGS_ID")

Minimum verification:

  • first-run banner behavior works on a clean install
  • review-consent action reopens preferences
  • accept, reject, and granular choices persist across app restart
  • downstream SDK behavior matches the consent state

6. iOS Install

Section titled “6. iOS Install”

Add the CocoaPods dependency:

pod 'CybexoSDK', '~> 1.0'

Initialize once during app startup:

import CybexoSDK


CybexoCMP.shared.initialize(settingsId: "YOUR_SETTINGS_ID")

Minimum verification:

  • first-run banner behavior works on a clean install
  • showBanner(force: true) reopens preferences
  • accept, reject, and granular choices persist across app restart
  • downstream SDK behavior matches the consent state

7. Verify with CYBEXO Pulse

Section titled “7. Verify with CYBEXO Pulse”

Open:

https://pulse.cybexo.com/

Scan the production website domain after publishing. For browser-based scans, CYBEXO Pulse uses:

https://pulse.cybexo.com/v2/public-scan

The compatibility API path remains available for API clients:

https://api.cybexo.io/v2/public-scan

Passing evidence should include:

  • CYBEXO Runtime Verified
  • runtime contract: pass
  • detected surface
  • loader URL for web, CMS, and GTM installs
  • loader version/build/channel/commit where available
  • Google Consent Mode status where applicable
  • evidence timestamp
  • report link
  • downloadable evidence JSON

8. Verify in Command Center

Section titled “8. Verify in Command Center”

After Pulse verification, the property should show runtime status in CYBEXO Command Center.

Expected evidence:

  • installed or connected property
  • runtime verifier pass
  • Pulse report link
  • surface
  • loader or SDK version/build where available
  • Consent Mode status where applicable

9. Launch Evidence Checklist

Section titled “9. Launch Evidence Checklist”

Keep this evidence with the release record:

  • install surface selected
  • production Settings ID confirmed
  • duplicate-loader check completed
  • browser/app verification completed
  • CYBEXO Pulse report link saved
  • Pulse evidence JSON downloaded when a customer-safe proof packet is needed
  • Command Center runtime status reviewed
  • rollback owner and rollback path confirmed
Section titled “10. Related Docs”