> 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/name-change-impact-on-pmp-metrics.md).

# Name change impact on PMP metrics

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

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

When generating data for PMP metrics Didomi will utilize the latest name configured for a widget, purpose and preference.

{% hint style="warning" %}
Whether your organization edits the name of a widget, purpose, preference from the data manager, configuration tree, or preferences widget configuration flow, it will not create a new widget, purpose, or preference within the analytics Didomi captures.
{% endhint %}

In the example below, the widget reflects everything in the preference tree (as shown in the screenshot below). If the value "Shoes" is selected, the value displayed in the analytics will be "Tennis - Shoes."

![](https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FPBR3TjcwFLIHRLRGCpS5%2FCapture%20d%E2%80%99e%CC%81cran%202023-10-05%20a%CC%80%2015.00.04.webp?alt=media\&token=0abb2cfe-0bfb-407d-87cb-45488f0dfe8b)

If you remove the "Tennis" preference value from the widget but let the tennis's articles preference values (as shown in the screenshot below) and users select "Shoes," in the analytics we will display the preference value name "Shoes" and "Tennis".

![](https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2Fz8kdVxFvLQMC8Gda6oFD%2FCapture%20d%E2%80%99e%CC%81cran%202023-10-05%20a%CC%80%2014.59.56.webp?alt=media\&token=92480b58-768c-4029-a449-90e66d8642a4)

In the analytics, the preference value names displayed are the reflection of the widget selection of preferences.


---

# 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/name-change-impact-on-pmp-metrics.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.