Consent Event Tracking

Ours Privacy CMP automatically tracks consent events and pipes them into your Ours Privacy account, allowing you to monitor consent patterns and access consent status on both visitors and individual events.

---

Automatic Consent Event Tracking

When you configure a Web SDK Token in your CMP settings, the platform automatically:

• Tracks CMP initialization: Sends a $consent_init event when the CMP initializes and is ready to manage consent. Contains the visitor's default consent based on your default opt-in/opt-out settings.
• Tracks first consent: Sends a $first_consent event when a visitor first expresses their consent preferences
• Tracks consent changes: Sends a $consent_change event whenever a visitor updates their consent preferences
• Links to visitor identity: Associates consent events with the visitor's unique ID for tracking over time
• Includes comprehensive data: Each consent event includes:
  • Consent type (all, custom, necessary)
  • Accepted and rejected categories
  • Accepted and rejected services
  • Geographic information (region, country)
  • Global Privacy Control (GPC) status
  • Timestamp and mount time

---

Accessing Consent Status

Once consent events are being tracked, you can access the latest consent status in several ways:

---

Configuration Requirements

To enable consent event tracking, you need to:

1. Set a Web SDK Token in your CMP General Settings
2. Publish your configuration to activate the tracking
3. Ensure the CMP script loads before other tracking scripts

The Web SDK Token can be found in your Ours Privacy source page for the Web SDK.

---

Next Steps

• JavaScript SDK: Programmatically access consent state
• General Settings: Configure the Web SDK Token