With IAB's recent changes to the consent framework for GDPR, Sortable is transitioning publishers using our hosted CMP to a hosted Quantcast CMP. This and other articles will be updated in coming weeks to reflect these changes.
This page describes how to integrate Sortable's hosted CMP on a site.
1. Set up Google Demand
Note: This step only applies to Sortable Select (formerly Enterprise) customers (e.g. customers who integrated Sortable using their own Google Ad Manager account).
Follow Google's recommendations to prepare your Ad Manager account.
If you choose to have Sortable manage Google consent, the hosted CMP prompts the user for their consent. If the user has not consented, Sortable will call
googletag.pubads().setRequestNonPersonalizedAds(1) to serve non-personalized ads.
If you choose to manage Google consent yourself, follow Google's guide on how to configure your Google tags.
2. Configure your custom purposes
If you have partners that collect data on your site that are not listed on the IAB Vendor list, you can choose to create a custom purpose for these partners. In order to configure the hosted CMP, Sortable needs the custom publisher purposes you want to display (provide this information to your account manager).
3. Link to the consent tool
Once the CMP is configured, it is automatically injected on any page where the Sortable ad script is loaded, for users in the EEA.
The GDPR requires that websites provide a way for a user to review and revoke consent after the initial pop-up. Therefore, publishers may need to provide a link/button to trigger the consent tool pop-up for the user.
Sortable provides an API window.deployads.showConsentTool() to trigger the consent pop-up.
The following example creates a link that the user can click to show the consent UI:
Sortable provides a mechanism to only show the link to users where the CMP is active. An element with the class name sortable-consent can be placed on a page and Sortable displays this element only to users where the CMP is active. Here is an example:
<li class="sortable-consent" style="display:none">