# PMP metric glossary

{% hint style="success" %}
**Access Type:** Analytics - Viewer

**Premium Feature**: Preference Management Platform
{% endhint %}

In this article, we provide an overview of the various metrics your organization can find within Didomi PMP analytics dashboards. Generally, PMP metrics can be organized into:

* [Authentication metrics](#authentication-metrics)
* [User & choice metrics](#user-and-choice-metrics)
* [Purpose metrics](#purpose-metrics)
* [Preference metrics](#preference-metrics)

{% hint style="warning" %}
**Note**: In order to facilitate your organization's understanding of how individual metrics are calculated we encourage you to review our [resources on statuses, choice types, etc...](/analytics/preference-management-platform-pmp-analytics/pmp-metrics.md)
{% endhint %}

***

### Authentication metrics

Authentication metrics enable your organization to analyze how end-users are navigating through the authentication funnel for your PMP widgets (i.e. end-user movement from when they first authenticate to when they provide their preference selections).

<table><thead><tr><th width="242">Metric/Indicator</th><th>Description</th></tr></thead><tbody><tr><td>Auth Asked</td><td>Total count of how many times the authentication request is displayed (times <a href="/pages/tQRyILrNHg5DwSafCvn4#measured-events"><code>authentication.asked</code></a> was triggered)</td></tr><tr><td>Auth Sent</td><td>Total count of how many times the authentication request confirmation is displayed (times <a href="/pages/tQRyILrNHg5DwSafCvn4#measured-events"><code>authentication.sent</code></a> was triggered)</td></tr><tr><td>Consent Asked</td><td>Total count of how many times end-users have accessed the preferences widget (times <a href="/pages/tQRyILrNHg5DwSafCvn4#measured-events"><code>consent.asked</code></a> was triggered)</td></tr><tr><td>Choice</td><td>Total count of how many times end-users have submitted their preference selections (times <a href="/pages/tQRyILrNHg5DwSafCvn4#measured-events"><code>consent.given</code></a> was triggered)</td></tr></tbody></table>

### User & choice metrics

User and choice metrics enable your organization to analyze the overall number of end-users who are making preference submissions (choices) via your preferences widget.

<table><thead><tr><th width="266">Metric/Indicator</th><th>Description</th></tr></thead><tbody><tr><td>Users</td><td>End-users who made a preference selection</td></tr><tr><td>Total Choices</td><td>Total number of new and updated choices made by end-users</td></tr><tr><td>New Choices</td><td>Total number of preference submissions made by end-users where a preference record was not found for the specific preferences widget<br><br><mark style="background-color:$warning;"><strong>Note</strong>: Please review our resource on the difference between</mark> <a href="/pages/vXcsOdpuvYGJQ5gSyueq"><mark style="background-color:$warning;">new choices and updated choices</mark></a> <mark style="background-color:$warning;">on how these metrics are calculated.</mark></td></tr><tr><td>Updated Choices</td><td>Total number of preferences submissions made by end-users where a preference record was found for the specific preferences widget.<br><br><mark style="background-color:$warning;"><strong>Note</strong>: Please review our resource on the difference between</mark> <a href="/pages/vXcsOdpuvYGJQ5gSyueq"><mark style="background-color:$warning;">new choices and updated choices</mark></a> <mark style="background-color:$warning;">on how these metrics are calculated.</mark></td></tr><tr><td>AVG Choice by User</td><td>Average number of preference submission (whether new or updated) made by end-users</td></tr></tbody></table>

***

### Purpose metrics

Purpose metrics enable your organization to analyze how end-users are setting and changing their choices for purposes configured in your preferences widget.

{% hint style="warning" %}
**Note**: In order to facilitate your organization's understanding of how individual metrics are calculated we encourage you to review our [resources on statuses, choice types, etc...](/analytics/preference-management-platform-pmp-analytics/pmp-metrics.md)
{% endhint %}

<table><thead><tr><th width="253">Metric/Indicator</th><th>Description</th></tr></thead><tbody><tr><td>Selected (purpose)</td><td>Total number of purposes that is selected by end-users when they give their preferences selection</td></tr><tr><td>Not-Selected (purpose)</td><td>Total number of purposes that is not selected by an end-user. The end-users have not made a choice and have never made a choice on the purpose (i.e. purpose status is <code>null</code>)</td></tr><tr><td>Maintained-Selected (purpose)</td><td>Total number of purposes where the previous purpose was selected and the current purpose is selected.</td></tr><tr><td>Propagation (purpose)</td><td>Total number of purposes where the previous purpose status was not selected but a child preference value was selected and the current purpose status is still not selected but a child preference value still is.</td></tr><tr><td>Denied (purpose)</td><td>Total number of purposes where the previous purpose status was not selected or selected and the current purpose status is <code>false</code>.</td></tr><tr><td>Maintained-Denied (purpose)</td><td>Total number of purposes where the previous status of the purpose was <code>false</code> and the current purpose status is <code>false</code>.</td></tr><tr><td>Purpose Select Rate</td><td><p>Ratio of purposes selected over the total number of times the preferences widget has been answered.<br></p><p><strong>Purpose selection rate</strong> = selected purposes/preference choices</p></td></tr><tr><td>Purpose Denied Rate</td><td><p>The ratio of purposes rejected over the total number of times the preferences widget has been answered.<br></p><p><strong>Purpose denied rate</strong> = purposes denied/preference choices</p></td></tr><tr><td>Activation Rate</td><td>The ratio of opt-in purposes over the total number of preferences widget has been answered.<br><br><strong>Purpose activated rate</strong> = (Selected + Maintained_Selected + Propagation)/total choices made by users</td></tr></tbody></table>

Refer to the example below for more information on purposes:

<img src="/files/y0bIcXRKma2qfiTWyadS" alt="" width="516">

**Purposes selection status**

1. In the **first** pref. choice:
   1. Purpose A is not selected but a preference is selected the purpose status is ***propagation***
   2. Purpose B purpose is ***selected***
   3. Purpose C is also ***selected*** even if no preference is selected below
   4. Purpose D is ***denied***
2. In the **second** pref. choice:
   1. Purpose A, despite not being selected, benefits from “propagation from the bottom” as child preferences have been selected.
   2. Purpose B is ***denied*** because its status has been changed to false
   3. Purpose C is ***maintained-selected*** because the purpose is still selected.
   4. Purpose D is ***maintained-denied,*** even if a preference value has been selected. The change in the child preference value doesn’t impact the preference status when selected or declined.

### Preference metrics

Preference metrics enable your organization to analyze how end-users are setting and changing their choices for preferences configured in your preferences widget.

{% hint style="warning" %}
**Note**: In order to facilitate your organization's understanding of how individual metrics are calculated we encourage you to review our [resources on statuses, choice types, etc...](/analytics/preference-management-platform-pmp-analytics/pmp-metrics.md)
{% endhint %}

<table><thead><tr><th width="256">Metric/Indicator</th><th>Description</th></tr></thead><tbody><tr><td>Selected</td><td>Total number of preference values where the previous preference value is not selected and the current preference value is selected.<br><br><mark style="background-color:$warning;"><strong>Note</strong>: As long as a preference is selected (has a value of <code>selected</code>) the preference will be counted as selected regardless of the parent value of its purpose.</mark></td></tr><tr><td>Not Selected</td><td>Total number of preference values where the previous preference value is not selected and the current preference value is still not selected.</td></tr><tr><td>Denied</td><td>Total number of preference values where the previous preference value is selected and the current preference value is not selected.</td></tr><tr><td>Maintained</td><td>Total number of preference values where the previous preference value is selected and the current preference value still is selected.</td></tr><tr><td>Preference activated rate</td><td><p>The ratio of opt-in preferences over the total number of preferences has been answered.<br></p><p><strong>Preference activated rate</strong> = (maintained + selected) / preference choices</p></td></tr></tbody></table>

Refer to the example below for more information on preferences:

<img src="/files/b1BHQOdmfuTAjwT1FuvC" alt="" width="516">

In the schema above we have 3 preference choices:

* coming from 1 **unique user.**
* for 2 distinct widgets: widget 1 and widget 2.
* widget 1 has 2 deployments/versions: widget 1.1 and widget 1.2. In widget 1.2 Rugby preference value has been removed.
* All values below are **preference values**

**Preference values selection status**

1. In the **first** pref. choice:
   * Basked, football, and rugby are ***selected***
   * MMA and Tennis are ***not selected***
2. In the **second** pref. choice:
   * Basket and Rugby are ***maintained***
   * Football is ***denied***
   * MMA is ***not selected***
3. In the **third** pref. choice:
   * daily is ***not selected***
   * weekly and monthly are ***selected***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.didomi.io/analytics/preference-management-platform-pmp-analytics/pmp-metrics/pmp-metric-glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.