Drupal Integration

Last updated: July 1, 2026

Use this page for Drupal sites that need CYBEXO Runtime Suite.

CYBEXO supports Drupal through the standard web runtime. When a managed Drupal module is enabled for your account, use that path. If a managed module is not available, use the direct site script path below.

1. Requirements

Drupal site administrator access.
Valid CYBEXO Settings ID.
Permission to add a site-wide script through theme, layout, or approved tag-management controls.

2. Recommended Integration Paths

Use one path per site:

Managed CYBEXO Drupal module, when available for your account.
Direct CYBEXO Web CMP Engine script in the site theme or approved tag-management layer.
CYBEXO GTM Consent Template if the site already uses Google Tag Manager.

Do not run multiple CYBEXO loader paths on the same page.

3. Direct Site Script

Add the loader once before ordinary marketing or analytics tags where possible.

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

4. Verification

On a public page:

document.getElementById("cybexo-cmp")

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

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

Run Pulse after publishing. The report should show CYBEXO runtime installed, loader verified, and Consent Mode evidence where applicable.

5. Debug Mode

Use the CYBEXO debug overlay:

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

6. Common Issues

Issue	Likely cause	Fix
Loader missing	Theme/template change not deployed or cache not cleared	Clear Drupal and CDN caches
Duplicate loader	Theme script plus GTM/plugin path both active	Keep one integration path
Consent defaults are late	Loader executes after Google tags	Move loader earlier or use GTM Consent Initialization
Banner not visible	Existing consent, non-banner region, or invalid Settings ID	Reset consent and verify Settings ID