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

Consent Event Schema

Last updated: February 18, 2026
Use this schema for internal analytics and audit logging integrations.

1. Example Event#

{
  "event_name": "consent_changed",
  "timestamp": "2026-02-18T12:34:56Z",
  "settings_id": "NXG-EXAMPLE",
  "region": "EEA",
  "frameworks": {
    "tcf": true,
    "gpp": false,
    "gcm_v2": true
  },
  "consent": {
    "ad_storage": "denied",
    "analytics_storage": "granted",
    "ad_user_data": "denied",
    "ad_personalization": "denied"
  },
  "state": "custom"
}

2. Field Notes#

event_name: stable event identifier.
timestamp: UTC ISO-8601 format.
settings_id: CMP configuration identifier.
region: policy region used for decisioning.
frameworks: framework activation flags.
consent: Consent Mode v2 signal values.
state: default, accept, reject, or custom.

3. Data Handling Requirement#

Do not include direct personal data in consent event payloads.
Previous
Web JS API Reference
Next
Deployment and Environments