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": "CYBEXO-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.