Skip to content
CYBEXO Developer Docs

Google Tag Manager Template Guide

Last updated: July 1, 2026

Use this guide to deploy CYBEXO Runtime Suite through Google Tag Manager.

1. Ownership Model

Section titled “1. Ownership Model”
  • Customer owns GTM container access, tag creation, trigger assignment, preview testing, and publishing.
  • CYBEXO owns the GTM template, loader runtime, documentation, and support path.

Installing the Community Template does not create a live tag by itself. A tag instance must still be configured and published in the customer container.

2. Prerequisites

Section titled “2. Prerequisites”
  • Active GTM web container.
  • Valid CYBEXO Settings ID.
  • No duplicate CMP loader. Use the GTM template or direct script/CMS injection, not both on the same page.

3. Install the Template

Section titled “3. Install the Template”
  1. In GTM, open Templates.
  2. Select Search Gallery.
  3. Add CYBEXO GTM Consent Template.
  4. Confirm the template is linked to the Gallery.

4. Create the CMP Tag

Section titled “4. Create the CMP Tag”
  1. Open Tags -> New.
  2. Select CYBEXO CMP.
  3. Enter the required Settings ID.
  4. Configure optional policy fields only when directed by your CYBEXO account configuration.
  5. Set trigger to Consent Initialization - All Pages.
  6. Save, preview, and publish.

Template behavior:

  • Loader endpoints are locked to CYBEXO domains.
  • Google Consent Mode v2 defaults are written before ordinary pageview/tag events when the tag fires on Consent Initialization.
  • The template supports the CYBEXO runtime contract used by Pulse and Command Center verification.
Section titled “5. Required Consent Mode Signals”

Consent Mode v2 requires these keys:

  • ad_storage
  • analytics_storage
  • ad_user_data
  • ad_personalization

Expected default values are resolved from your CYBEXO policy and visitor region. Do not hardcode a single global expectation for all regions.

6. Verify in Tag Assistant

Section titled “6. Verify in Tag Assistant”

Run validation in a fresh Tag Assistant preview session.

  1. On Consent Initialization, confirm the CYBEXO CMP tag fired.
  2. Confirm all four Consent Mode v2 keys are present.
  3. Confirm ordinary Google tags do not fire before consent defaults are available.
  4. For banner regions, interact with the banner and confirm a consent update appears.
  5. Confirm a network request to https://cmp.cybexo.com/loader.js.

7. Verify with Pulse

Section titled “7. Verify with Pulse”

After publishing, run CYBEXO Pulse against the production URL.

Pulse should show:

  • runtime status: installed and verified
  • surface: GTM where the template is detected
  • loader URL: https://cmp.cybexo.com/loader.js
  • artifact metadata: version, build, channel, commit when available
  • Consent Mode status: default keys present and update behavior observed where applicable

8. Common Failures

Section titled “8. Common Failures”
Symptom Likely cause Fix
No CMP tag in Tag Assistant Tag was not created or published Create a CYBEXO CMP tag and publish
Consent not configured Trigger is wrong Use Consent Initialization - All Pages
Duplicate banner GTM and direct/CMS loader both active Keep one integration path
Consent defaults are late Another tag writes before CMP Move CYBEXO CMP earlier and remove conflicting consent defaults
Banner does not show Existing consent, non-banner region, or invalid Settings ID Reset consent, confirm region policy, and verify Settings ID

9. Evidence Pack

Section titled “9. Evidence Pack”

For production audit records, capture:

  • Tag Assistant screenshot showing Consent Initialization and default consent state.
  • Tag Assistant screenshot showing post-action consent update for banner regions.
  • Network evidence for cmp.cybexo.com/loader.js.
  • Pulse report showing CYBEXO Runtime Verified.
  • Command Center runtime status for the property/domain.
Section titled “10. Related Docs”