> 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/preference-management-platform-pmp/introduction.md).

# Introduction

{% hint style="success" %}
**Premium Feature**: Preference Management Platform
{% endhint %}

The Didomi Preference Management Platform (PMP) enables your organization to collect first-day data to build a thorough and centralized understanding of your end-user's choices and disseminate that information across your tech stack to create a better and more personalized marketing campaign.

Generally, the PMP solution is configured by performing the following:

1. Create distinct preferences within the preferences library
2. Define relationship between different purposes and the data collected through the preferences in your organization's PMP configuration tree
3. Configure a preferences widget using the preferences (and their associated purposes)

<figure><img src="/files/9pj4ROo2jgXSMaGFqVuW" alt=""><figcaption></figcaption></figure>

&#x20;


---

# 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 dynamically by asking a question.

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

```
GET https://docs.didomi.io/preference-management-platform-pmp/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
