🔎 Didomi collects events through the PMP SDKs deployed on your properties. These events provide aggregated analytics on Didomi Console.
📊 The Analytics section is available from the left menu of the Console. The section provides a series of graphs and tables. You can also find a section dedicated to the PMP's dashboards.
- PMP dashboards are updated on a daily basis. You can read this article to learn more about dashboard updates.
|📊 Metric Name||📕 Description||✍️ Formula (based on events)|
|Authentication requested||Number of authentication requests displayed.||sum of the auth.asked|
|Authentication sent||Number of authentication requests answered.||sum of the auth.sent|
|Authentication bounces||Number of authentication requests not answered.||sum(auth.asked) - sum(auth.sent)|
|Authentication bounce rate||Ratio of authentication requests not answered over all the requests displayed.||(auth.asked - auth.sent)/auth.asked|
|Authentication response rate||Ratio of authentication requests answered over all the requests displayed.||auth.sent / auth.asked|
|Widgets displayed||Number of widgets displayed. A widget is considered as displayed only after the user authentication/identification.||sum of the consent.asked|
|Authentication completion rate||Ratio of widget displayed over all the volume of authentication sent.||consent.asked / auth.sent|
|Widgets completed||Number of consent given sent. In other words, the amount of widgets completed and validated.||sum of the consent.given|
|Widget bounces||Number of widgets displayed but not answered.||consent.asked - consent.given|
|Purpose selected||Number of times a purpose is selected in preference choices. Button "Yes" checked.||consent.given|
|Purpose selection rate||Ratio of purposes selected over the total number of times the widget has been answered.||consent.given of the purpose / total consent.given of the widget|
|Purpose rejected||Number of times a purpose rejected in preference choices. Button "No" checked.||consent.given|
|Purpose rejection rate||Ratio of purposes rejected over the total number of times the widget has been answered.||consent.given of the purpose / total consent.given of the widget|
|Purpose ignored||Number of times a purpose has no value checked in preference choices.||consent.given|
|Purpose no response rate||Ratio of purposes without value checked over the total number of times the widget has been answered.||consent.given of the purpose / total consent.given of the widget|
|Preference selected||Number of times a preference selected in a consent given.||consent.given (at any position)|
|First parent selection||Number of times a preference selected through propagation as a first parent.||count consent.given in first parent|
|Second parent selection||Number of times a preference selected through propagation as a second parent.||count consent.given in second parent|
|Direct selection||Number of times a preference selected directly.||count consent.given direct selection|
|Active users (pref.choice-based)||Number of distinct user IDs (organization_user_id) who have given a preference choice.||count distinct user IDs (organization_user_id|
|New preferences||Number of consents given with no previous consent attached.||count consent.given with no previous consent|
|Updated preferences||Number of consents given with a previous consent attached. The number of opt-ups and opt-downs is equal to the number of updated preferences.||count consent.given with a previous consent|
|Widget completion rate||Ratio between the number of widget answered (consents given) over the number of widget displayed (consent.asked).||consent.asked / consent.given|
|Widget bounce rate||Ratio of the widgets not answered (consent given) over the widget displayed.||(consent.asked - consent.given) / consent.asked|
|Preference selection Rate||Ratio of preference selected over the total number of times the widget has been answered.||consent.given with preference selected / total consent.given of the widget|
|Preference value selection Rate||Ratio of preference value selected over the total number of times the widget has been answered.||
consent.given with preference value selected / total consent.given of the widget
|New preference rate||Ratio of the number of new consents over the total consents given.||new preferences / consent.given|
|Updated preference rate||Ratio of the number of updated consents over the total consents given.||updated preferences / consent.given|
Purpose and preference selection
- If a purpose has the button No selected or choices are empty, the purpose is considered as not selected. The only way for a purpose to be considered has selected is to select Yes.
- The preference “Frequency” will be considered as selected as well as the preference value “Daily”.
- The preference values “Weekly” and “Monthly” won’t be considered as selected.
Anatomy of preferences
👉 In this example we have three preferences: “Clothing”, “Clothing items” and “Frequency”.
👉 In the example the “Frequency” preference has three values: “daily”, “weekly” and “monthly”. One of them is selected, (selected preference value): “daily”.
Embedded preferences and full preference value
👉 “Frequency” preference is embedded into “Clothing Items” preference and “Clothing Items” is embedded into “Clothing” preference.
Full preference value string
👉 The full preference value is the complete chain of preferences selection.
Clothing: Football > Clothing Items: Shoes > Frequency: Daily. In this example, even if only the value Daily is selected, this value is selected in the context of embedded preferences. Therefore, we will consider Football and Shoes as selected values.