Skip to content

Runtime Suite Install and Verify

Last updated: November 20, 2026

Use this guide to choose one CYBEXO Runtime Suite installation path, publish it safely, and test the running integration. For a website, Pulse can also inspect the returned page source.

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.

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?delivery=2">
</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
  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
  • Tag Assistant identifies the published container and tag that loaded the runtime
  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
  • the active WordPress plugin and the published page use the intended installation
  • plugin admin settings match the production Settings ID

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

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

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

For web deployments, record the tested URL or hostname, scan time, pages read and the rule results. Pulse can report metadata when an exact-page scan inspects a directly linked CYBEXO loader. Keep the report link or download the evidence JSON. For Android and iOS, use the device checks above.

Open the connected property and review its latest runtime evidence. Match any received consent events to the visitor actions exercised in your browser or device test. Retain the deployment surface and version with those observations.

Keep this evidence with the release record:

  • install surface selected
  • production Settings ID confirmed
  • duplicate-loader check completed
  • browser/app verification completed
  • for a website, Pulse source report saved with its date and page coverage
  • source evidence JSON downloaded when a customer-safe proof packet is needed
  • Command Center runtime status reviewed
  • rollback owner and rollback path confirmed