# PMP metrics

The data collected through the Didomi PMP SDK is calculated to generate the metrics found in your PMP analytics dashboards. In this article, we will cover some important nuances surrounding the methodology Didomi employs to derive your organization's PMP metrics.

* [Data received for preference submission](#data-received-for-preference-submission)
* [Purpose status](#purpose-status)

***

### Data received for preference submission

When an end-user submits their preferences choices, Didomi receives, among other data, the following information and in turn uses it to calculate purpose and preference metrics:

<table data-header-hidden><thead><tr><th width="249"></th><th></th></tr></thead><tbody><tr><td>Available purposes and preferences</td><td>Purposes and preferences displayed to the user. </td></tr><tr><td>Previous (last) choices</td><td>Purposes and preference values selected in a previous submission. If it is the first time the end-user is submitting their preferences the previous value will be empty. In the example below, the end-user previously selected 3 preference values: basket, tennis, and football.</td></tr><tr><td>Current choices</td><td>List of the purposes and preferences that have been selected or remain selected by the end-user. In the example below, 3 preference values are selected, rugby is newly selected, and Football and Basket remain selected.</td></tr></tbody></table>

<img src="/files/UvpTxBLy7Qnlx2KWyfOd" alt="Capture d’écran 2023-10-02 à 15.17.41" width="516">

***

{% hint style="info" %}
The end-user's preferences submission is in regards to a particular preferences widget. When an end-user submits the preferences selections, each preference and purpose will have a record of **previous** and **current** choices. [Click here](/analytics/preference-management-platform-pmp-analytics/pmp-metrics/new-choice-vs-updated-choice.md) to learn more about how previous and current choices impact the calculation for new vs updated choices.&#x20;
{% endhint %}

### **Purpose status**

Purposes can have three states in the preference choices:

<table><thead><tr><th width="222">Status</th><th></th></tr></thead><tbody><tr><td>Empty</td><td>Purpose has never been selected/is not selected nor declined. If a purpose has been selected it can’t be empty (null) again. It will rather be true or false.</td></tr><tr><td>True</td><td>Purpose selected.</td></tr><tr><td>False</td><td>Purpose declined. Please note that a purpose can be "false/declined" but have a selected child preference value.</td></tr></tbody></table>

{% hint style="info" %}
[Click here](/analytics/preference-management-platform-pmp-analytics/pmp-metrics/pmp-metric-glossary.md#purpose-metrics) to learn more about how these statuses are used to calculate purpose metrics.&#x20;
{% endhint %}


---

# 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.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.