AdConsent with Content Pass Activation
- Anna Wiśniewska
Content Pass with AdConsent
AdConsent is a Snigel CMP solution; if you are already working with Snigel and using AdConsent—Content Pass, full activation would require a few steps from your publisher end and your Snigel account manager. However, thanks to ready integration, you can skip elements like “account creation with Content pass” or “integrate into CMP,” as those are already done and managed by Snigel.
What needs to be done by you, the Publisher?
First of all, if you are interested, please get in touch with your account manager at Snigel. They will be able to guide you through the activation steps. If you are here just to read what must be done, here is general information.
General steps:
Make sure no third-party resources are loaded without consent
Configure CNAME Record for content pass Session Management
Mention Content Pass in the Privacy Policy
Sign DPA with Content Pass
Communicate with your Account Manager about changes
0. Load third-party resources after consent
Before integrating Content Pass, ensure your website is not loading any third-party resources without user consent. Content Pass provides a page with technical details on how to manage third-party resources. However, as each CMP implementation differs, please check with your Account Manager code to be used with AdConsent.
What are third-party resources? They are everything that is not loaded from your server and where you have no control over what data are sent out about users. Examples include YouTube embeds, Google Font API, and elements like Taboola or embedded Tweets.
What about the Snigel loader code? This code loads AdConsent with Content Pass, and we don’t collect user information; we only place a necessary cookie with consent information, so it can’t be delayed. However, all other sources we load are delayed until the user consents.
To help you manage third-party resources, we prepared a Playbook to guide you with implementation.
1. Configure CNAME Record for content pass Session Management
Since 3rd-party cookies no longer work reliably in most browsers, Content Pass subscribers must be identified using a 1st-party session. Contentpass does not directly obtain or store user consent or personal data.
To simplify handling of these 1st-party sessions, Content Pass provides an endpoint that must be configured behind a CNAME subdomain of the publisher's first-party domain.
Your Account Manager will provide you with specific details during the onboarding process.
Once the CNAME has been set up, Content Pass will automatically provide the required SSL certificates.
2. Mention Content Pass in the Privacy Policy
While Content Pass does not process non-subscribers data, it receives your visitors' IP addresses for technical reasons. Please inform your visitors about this data processing and link to their privacy policy by including the following snippet on your privacy policy page:
This is available in seven languages and can also be found on Content Pass pages - here.
Optional Content Pass login/signup link
Exposing the Contentpass login and signup is recommended as part of the privacy policy (already included in the Privacy Policy text) or somewhere else on the webpage. This is optional and only for publishers who want to expose the login/signup to the Content Pass option outside the Privacy Policy page.
Login: cp('login');
Signup: cp('signup');
We recommend doing this in the privacy policy and similarly to CPPA in the footer.
<a href="https://www.contentpass.net/login/" onclick="cp('login'); return false;"
target="_self">ContentPass Login</a>
In case of troubles with CMS types of sites, i.e., WordPress - it can be a simple link redirecting to https://www.contentpass.net/login/
3. Sign DPA with Content Pass
As Content Pass will receive your user's IP information, a Data Protection Agreement must be signed with them. You will be provided the document by Snigel via the DocuSign system.
4. Communicate with your Account Manager about changes
Snigel and Content Pass support must verify all required changes on-site before Content Pass can be fully activated. Please communicate with your Account Manager about all needed changes. At some point, Content Pass will be deployed to production on your site for a complete check, and if all goes well, it will remind there—with information that it’s still in configuration—until Content Pass can confirm that all is done correctly.
Success! All done, all confirmed. Content Pass is now fully functional for visitors of your site.
Default code to delay loading of 3rd party resources
The code that will be served using this delay code might need adjustments depending on the technology in which your site is created and what kind of resource it should load.
window.addEventListener('adnginLoaderReady', function() {
adconsent('isConsentWallUser', null, r => { if
(!r.hasSubscription) {
// load 3rd party resources here
}}); });