This guide provides details on simply getting consent messages displayed on your site. (This setup would likely change for delivering other messages, such as adblock.)
Implementation can be divided into two steps:
Setting up the messaging domain
Please read through the content below regarding each of these implementation steps and feel free to reach out to your Sourcepoint account manager with any questions you may have.
The code-snippet consists of 3 script tags:
1. The first section of the tag is the Stub script. This sets up the IAB consent object “__cmp” and makes it available on queue to be called and released when needed. It is important to have this script tag always at the top in the first position to avoid errors and failure of the service.
a. accountId – This is set to the account ID you receive from your Sourcepoint account manager - The ID associates your data and property to your account in the Sourcepoint user interface.
b. cmpOrigin - 'https://sourcepoint.mgr.consensu.org' this is where the Sourcepoint CMP lives. Keep as is.
c. mmsDomain - 'https://mms.sp-prod.net' can be changed to a CNAMED subdomain in order to deliver 1st party cookies on Safari web browser (due to Safari’s ITP). Changing the mmsDomain is optional! More information about setting up an mmsDomain below.
Other optional params:
siteHref – maps the message to a specific URL
privacyManagerId – forces a specific privacy manager to be allocated for that message
waitForConsent – a Boolean that when is set to true disables interaction with the page until a user has given consent
siteId – maps the message to a specific property (website, app, OTT)
Once you have created the CNAME record, please inform your Sourcepoint Account manager so that they can create an SSL certificate for the subdomain. This will ensure that both secure and non-secure traffic are handled properly.
We also included additional information on how to leverage our key-value pair targeting features and our data callbacks. Key-value pairs are used to create highly targeted messages based on data points from external systems like DMPs and CRM platforms. Our callbacks can be used to set cookie values based on the messages a user have seen and to send data to external systems such as website analytics platforms and/or DMPs.