NexaGuard
  1. Developer-Reference
NexaGuard
  • Getting-Started
    • NexaGuard Developer Documentation
    • Quickstart (5 to 10 Minutes)
    • Documentation Overview
    • Concepts and Glossary
  • Compliance-and-Standards
    • Compliance Overview
    • IAB TCF v2.3 Support
    • Google Consent Mode v2 Validation
    • TCF API Validation
    • Audit Checklist (Pre-Launch)
  • Web-and-CMS-Integrations
    • NexaGuard CMP SDK – Web & GTM Setup
    • Integrate NexaGuard CMP with Webflow and Wix
    • Integrate NexaGuard CMP with WordPress
    • Integrate NexaGuard CMP with Drupal
    • Integrate NexaGuard CMP with Shopify
  • Mobile-SDKs
    • NexaGuard CMP SDK - iOS Setup
    • iOS SDK API Reference
    • NexaGuard CMP SDK - Android Setup
    • Android SDK API Reference
    • App Attribution Partner (AAP) Integrations
  • Developer-Reference
    • Web JS API Reference
    • Consent Event Schema
    • Deployment and Environments
    • NexaGuard Debug Tool
    • Troubleshooting Playbook
    • Performance and Best Practices
    • Accessibility and UX Guidelines
    • Localization Workflow
    • Migration Guide
  • Security-and-Privacy
    • Security Overview
    • Privacy Architecture
    • Data and Logging Transparency
    • Subprocessors
    • CSP and Network Allowlist
  • Enterprise-and-Legal
    • DPA and Legal Pack
    • RFP Feature Matrix
    • Status and Reliability
    • Support and Escalation
    • NexaGuard CMP SDK – Commercial Licence
  • Operations
    • Changelog and Version Policy
  1. Developer-Reference

Deployment and Environments

Last updated: February 18, 2026
Use this guide to separate staging and production consent behavior safely.

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#

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#

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#

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#

restore previous settings profile or settings ID
verify consent defaults and update events
confirm banner appears exactly once
collect debug report after rollback
Previous
Consent Event Schema
Next
NexaGuard Debug Tool