Preference Management Platform
The Preference Management Platform (PMP) is a 51Degrees cloud widget that asks if a user wants to fund their access with personalized or standard advertising, or if they would rather pay for access.
It signals the choice through the standard __tcfapi as a
TCF string, which is sent to the cloud to issue a matching
51Did.
Your advertising preference
The 51Did your preference triggered
No 51Did issued for this preference.
The PMP dialog appears on your first visit and remembers your choice. Change my preference re-opens the dialog so you can pick a different option. Wipe all data clears every bit of stored state (preference, identifiers and session data) so the demo starts completely fresh, as if you had never visited.
Change my preference Wipe all data and start againHow this works
-
The PMP widget collects the visitor's choice and
exposes it through the IAB
__tcfapias a TCF v2 string (the same API a conventional CMP exposes). -
The advertising service reads that TCF string and sends
it to
cloud.51degrees.comas thetcstringevidence. - The cloud works out the marketing tier from the TCF string and returns the matching 51Did (or none, if the preference does not permit advertising).
- The advert is then rendered as either personalized or standard at the top of the page.
TCF compatibility
The PMP is technically compatible with the IAB Europe TCF wire format and deliberately not compliant with IAB Europe TCF policy. It is not an IAB Europe-certified CMP, by choice.
The dialog emits a TCF v2 string, the same format any TCF-aware system already knows how to read. Ad servers, supply-side platforms, analytics tags and audience tools that already understand TCF string structure can consume the output without modification.
The PMP is not, and was never built to be, an IAB Europe-policy-compliant CMP. It asks how a visitor wants to fund their access, not whether they permit data processing. No personal data flows through it and no legal permission is being requested, so the policy framework that IAB Europe certification attests to does not apply. Using the TCF wire format keeps the visitor's funding preference portable across downstream tooling without making any claim of compliance the PMP cannot back.
Current TCF string
Waiting for your preference…
Unpack the string into its underlying purpose and vendor bits at the IAB Tech Lab GPP / TCF decoder.
The link appends the current TCF string as a URL fragment, so the decoder pre-loads it on arrival, no copy-paste needed.