Here are the most frequently asked questions about Sortable-Hosted Consent Management Platform (CMP).
Where does it run?
The CMP only asks for consent from users located in the EEA. At this time, it is not possible to change the set of users being targeted.
How does the CMP work?
A detailed explanation of how the Sortable-hosted CMP works can be found here.
Which CMP will Sortable host?
The Sortable-hosted CMP is built based on AppNexus' reference CMP.
Is the Sortable-hosted CMP an IAB-registered CMP?
Yes. The Sortable-hosted CMP (ID 39) can be found on the IAB Europe's registered CMP list.
What do publishers need to do in order to use the Sortable-hosted CMP?
The instructions for how to use the Sortable-hosted CMP can be found here.
What happens if a user chooses to close the window?
The user can close the window by pressing the GOT IT, THANKS! button or the close button (X) in the top right corner. This is treated as if the user consented Yes to all listed vendors, and the CMP stores this result in the consent cookie. If the user customized their consent choices, they can close the window by pressing the SAVE AND EXIT button as well as the close button (X) in the top right corner. The CMP then saves the changes they made to the consent cookie.
What happens if the user does NOT consent to some or all purposes and vendors?
Some partners are able to serve non-personalized ads in this case. Other partners are not able to serve any ads at all. For details on how Google behaves, see here.
What happens when a user leaves the CMP pop-up window open?
The Sortable-hosted CMP pauses ad requests until the user gives consent.
How long does it take the Sortable-hosted CMP consent cookie to expire?
Currently, the Sortable CMP expires the cookie after 30 days. However, the expiration period may be subject to change in the future.
If I am a publisher using the Sortable-hosted CMP, can I customize the consent UI for my site(s)?
No. Sortable does not currently support customizing the appearance of the consent UI.