Content Pass with AdConsent

Content Pass is integrated with AdConsent as an out-of-the-box solution. However, working with Content Pass requires additional steps. Please 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 Snigel Account Manager for details.

General Tasks​

Here, all general tasks are listed. Contentpass does not directly obtain or store any user consent or any other personal data.

Stepsaccount 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:

0. Make sure no third-party resources are loaded without consentSign up for a contentpass account

1. Configure CNAME Record for contentpass content pass Session Management

2. Mention contentpass Content Pass in the Privacy PolicyIntegrate contentpass with your CMP

3. Sign DPA with Content Pass

4. Communicate with your Account Manager about changes

0. Load third-party resources after consent​

Before integrating contentpassContent Pass, make sure ensure your website is not loading any third-party resources without user consent. See this page for Content Pass provides a page with technical details on how to do so.

1. Sign up for contentpass​

AdConsent works with Contentpass out of the box - to use AdConsent with AdEngine please contact your Snigel Account Manager - they will sign up for content pass and manage the configuration steps.

...

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 don't no longer work reliably anymore in most browsers, contentpass 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, contentpass Content Pass provides an endpoint that must be configured behind a CNAME subdomain of the publisher's first-party domain.

In the following example we assume that the publisher's website is: https://www.example.com and the propertyId is 1234abcd. Please contact your Snigel Account Manager for details.

A CNAME must be set up as follows:

...

Your Account Manager will provide you with specific details during the onboarding process.

Once the CNAME has been set up, contentpass Content Pass will automatically provision provide the required SSL certificates.

...

2. Mention

...

Content Pass in the Privacy Policy​

While we do Content Pass does not process any data of non-subscribers , we receive the data, it receives your visitors' IP addresses of your visitors for technical reasons. Please inform your visitors about this data processing and link to our their privacy policy by including the following snippet on your privacy policy page:

Languages ….

Note:​

Link target for login:

...

...

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');Link

target for signup:Signup: cp('signup');

We recommend doing this in the privacy policy and similarly to CPPA in the footer.

javascript: <a href="https://www.contentpass.net/login/" onclick="cp('signuplogin'); 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

4. AdConsent contentpass integration

Contentpass is fully integrated with AdConsent - please contact your Snigel Account Manager for activation.

Please prepare a staging page - on which both the removal of 3rd party scripts as well as staging loader can be tested.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

}}); });