Events and sampling

Didomi collects events through the SDKs deployed on your properties (websites, mobile apps, privacy centers, etc.). Those events are used to compute aggregated analytics like consent rates, page views, etc.

Topics

  • Events: Types of events collected by the Didomi SDKs
  • Sampling: How events are sampled by the Didomi SDKs

1- Events

🔍 The Didomi SDKs automatically collect events when a user interacts with your website, mobile app, etc.

The following events are automatically collected and used by Didomi for generating aggregated metrics. Some events are also stored as legal proofs of consent.

📊 Page view (Websites)

A page view event is fired on every page browsed by a user on your websites. Page views are only tracked when the Didomi SDK is present on the page so make sure to embed the Didomi SDK tag on every page of your websites.

This event includes the following data points:

  • Date and time
  • Consent status of the user for purposes and vendors
  • Domain name (but not the actual URL/page visited by the user)
  • Country of the user
  • Experiment (if any)

📊 App sessions (Mobile Apps)

App sessions are tracked every time a mobile app is launched. App sessions are only tracked when the Didomi SDK is initialized so make sure to embed the Didomi SDK in your app and initialize it on every app launch.

This event includes the following data points:

  • Date and time
  • Consent status of the user for purposes and vendors
  • Mobile app ID
  • Country of the user

📊 Notice shown

This event tracks when consent notices are shown to users for collecting their consent.

This event includes the following data points:

  • Date and time
  • Purposes and vendors shown to the user
  • Consent status of the user
  • Domain or mobile app ID
  • Country of the user

📊 Consent given

This event tracks choices made by the user (both positive and negative). It is sent every time a user agrees or denies to a consent notice (or any other UI displayed by Didomi) to register the new consent status of the user.

This event includes the following data points:

  • Date and time
  • New consent status of the user for purposes and vendors
  • Previous consent status of the user for purposes and vendors
  • Domain or mobile app ID
  • Country of the user

This event is stored as a legal proof of consent.

📊 Interactions with the UI

This event tracks the user interactions with the consent UI (showing the list of purposes, expanding vendor details, etc.).

This event includes the following data points:

  • Date and time
  • Identifier of the interaction with the UI
  • Domain or mobile app ID
  • Country of the user

2- Sampling

🔍 All "Consent given" events that happen are collected and stored by Didomi as they serve as a legal proof of consent and to demonstrate a user choice.

The other events collected by the Didomi SDKs on websites and mobile apps are sampled: events are collected from a random group of users. The sampling rate varies by event type and platform.

The sampling strategy that is applied is the following:

  • Every user is associated with a unique and random user ID
  • User IDs are uniformly distributed into N random buckets through hashing
  • Users from the top X% buckets are selected as being part of the sample
  • All events from users in the sample are collected

This strategy ensures that the sample is representative of the whole population (all users) by selecting purely random users and by logging all events from those users (which ensures that we capture the full behavior of those users).