> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/analytics/preference-management-platform-pmp-analytics/pmp-metrics/new-choice-vs-updated-choice.md).

# New choice vs Updated choice

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

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

When viewing the [Preferences selection RAW dashboard](/analytics/preference-management-platform-pmp-analytics/pmp-dashboards/preference-selection-raw-dashboard.md), your organization can view the total number of new choices and updated choices made for your preferences widgets across your selected periodization. 

<table><thead><tr><th width="249">Metric</th><th>Description</th></tr></thead><tbody><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</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.</td></tr></tbody></table>

Both of these metrics are tied to the end-user's preferences record 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](/analytics/preference-management-platform-pmp-analytics/pmp-metrics.md).

New choices do not necessarily equate to new end-users. If an end-user is either entirely new to your platform **or** you have replaced your preferences widget on your domain, there will be no record of the previous choices made by the end-user so all choices will be counted as a new choice

If your organization adds a new purpose or preference to your preferences widget and the end-user subsequently resurfaces the preferences widget, makes selection for the additions, and resubmits their preferences selection then those choices will be counted as an updated choice since the end-user has a preferences record in regards to the preferences widget.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didomi.io/analytics/preference-management-platform-pmp-analytics/pmp-metrics/new-choice-vs-updated-choice.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.