# Marketing Preferences Center (additional module)

## What is our Marketing Preferences Center?

Marketing Preferences Center is part of our Consent management Premium offer. \
It allows you to build a personalized Preferences Center where online and offline consents are merged around unified users and stored in the same database.

Then, you can easily create and customize a web page to display this information to visitors who want to manage their consents and personal information.

It turns a legal page into a preference center that is way more valuable for a customer as it is more like a sharing space between the brand and their visitors/clients rather than just a way to collect the consent.

## How it works?

Marketing Preferences Center is a realtime searchable nosql database. We provide also a dedicated API to read and/or write consents on this database (<https://community.commandersact.com/trustcommander/api/get-consents>)

·      Consents are collected through our Trust Commander CMP solution (native integration)

·      Consents coming from a CRM database could be added with our FTP importer files or our API (<https://community.commandersact.com/trustcommander/api/get-consents>)

·      Our customers can personalize the look and feel of their marketing preferences center page, we don’t host the webpage.

·      Paid option: our customers can choose to receive regularly a full consents database copy to have a backup on their side

![](/files/-MdaMip8sHtVEL-2UONb)

### Limitations:

* The API accepts a <mark style="color:orange;">**maximum of 20 preferences**</mark>


---

# 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://community.commandersact.com/consent-management/marketing-preferences-center-1/marketing-preferences-center-trust-premium-only.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.