This article covers the scenario of a publisher using their own CMP to handle consent for Holid.io's ad delivery
It's important to secure consents from users in order to be compliant but also to increase the revenue possibilities for your ads. Holid.io thereby makes sure to look for possible consents on your site before starting the ad auction.
Holid.io's checks if there is consents available on the site every few milliseconds, but for optimal performance, we recommend to include a CMP directly from Holid.io.
Checklist when using your own CMP
- The CMP must trigger for worldwide traffic, and depending on specific country regulations, let your CMP show the relevant information to users.
- The CMP must be a TCF 2.2 IAB validated and activated CMP (see list here of validated TCF 2.2 CMPs, under TCF v2.2 CMP Service)
- The TCF 2.2 is a framework and provides a standardized way of transmitting consents, making it possible for Holid.io to work with several different CMPs
- Your CMP must include GPP parameters for EU and US traffic.
- Your CMP must make sure your CMP includes the demand partners that Holid works with. This list is mentioned below. We ask to specifically make sure to add Holid AB, Vendor ID 1177, in your vendor declaration. If you're working with Google CMP, learn how to add Holid to your Google CMP vendor list.
- Your CMP code must be initiated at the topmost location within the <head> </head> section of your site
- This is to make sure your CMP pauses all relevant scripts afterwards but also is shown to the user as early as possible for optimal user friendliness.
- Your CMP code must be initiated before the Holid.io-header code.
- Most CMPs are designed to pause some scripts before getting a user-answer, which is needed in this case.
Vendors to make sure your CMP includes
The full list is as follows. Vendor ID is mentioned on the left, and Vendor name on the right:
What happens if Holid.io doesn't find a CMP on your site?
For EEA, UK, Switzerland, Canadian, Brazilian and US users, Holid.io checks your site for CMP consent data every 100 milliseconds after our code is initiated for up to 2 seconds.
1. If we find consent data from your CMP within the 2 seconds, at any of the 100 ms checks:
Holid.io launches an auction including the consent data
2. If we do not find any consent data before the 2 second timeout:
Holid.io publishes a CMP automatically on your site and launches an auction including the consent data.