Preference management platform (PMP) implementation overview (web)

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.

In this article, we will provide a general implementation path to create, configure, and launch the Didomi PMP solution on a website.


Prerequisites

Preferences widgets (the front-end interface your end-user uses to provide their preferences) need to be embedded in an authenticated environment. That is, Didomi needs a way to verify the end-user's identity and store/match the preferences record to the correct user.

Authentication must be performed in your organization's backend. Click herearrow-up-right to learn more about the various ways your organization can authenticate an end-user.

circle-info

Additionally, if your organization is configuring a preference center and plans to host the preference center using a custom domain, the custom domain must be configured.

Overview

Console configuration

Use the table below to track the necessary configurations that need to be performed within the Didomi console before adding the required code onto your website.

circle-exclamation

Deploy/embed preferences widget

How your organization deploys or embeds its preferences widget on your website is dependent on the preferences widget format. Follow the links below to learn more based on your preferences widget format:

circle-exclamation
Format
Resource

Single or Multi purpose preferences widget

Last updated