Skip to content
CYBEXO Developer Docs

Deployment and Environments

Last updated: February 18, 2026

Use this guide to separate staging and production consent behavior safely.

1. Environment Model

Section titled “1. Environment Model”
  • Staging: non-production settings ID and test domains/apps.
  • Production: production settings ID and live domains/apps.

Do not reuse the same settings ID across both environments.

2. Rollout Strategy

Section titled “2. Rollout Strategy”

Recommended sequence:

  1. Deploy in staging and run full audit checklist.
  2. Release to limited production scope if available.
  3. Validate logs, Tag Assistant traces, and support telemetry.
  4. Expand rollout to all traffic.

3. Cache and Propagation Notes

Section titled “3. Cache and Propagation Notes”
  • Document config cache behavior in your runbook.
  • Define expected propagation time from dashboard changes to client runtime.
  • Purge site cache and any upstream caching layer after major CMP configuration changes.

4. Change Control

Section titled “4. Change Control”
  • Track settings changes with release ticket IDs.
  • Keep rollback plan for script deployment and settings revert.
  • Announce planned changes to stakeholders before launch windows.

5. Rollback Checklist

Section titled “5. Rollback Checklist”
  • restore previous settings profile or settings ID
  • verify consent defaults and update events
  • confirm banner appears exactly once
  • collect debug report after rollback