Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Content Pass with AdConsent

AdConsent is Snigel CMP solution, if you are already working with Snigel and use AdConsent - Content Pass full activation would require few steps from Your - Publisher end, as well as from your Account Manager. However, thanks to integration we are skipping elements like “account creation with Content pass” or “integrate in 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 contact your account manager at Snigel. They will be able to guide you through the steps. If you are here just to read what is to be done, here is very general information.

Contentpass does not directly obtain or store user consent or personal data.

General steps:

  1. Make sure no third-party resources are loaded without consent

  2. Configure CNAME Record for content pass Session Management

  3. Mention contentpass in the Privacy Policy

  4. Sign DPA with Content Pass

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 is different, 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, so it can’t be delayed. However, all other sources that we load are delayed till the user gives their consent.

2. 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.

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, contentpass will automatically provision the required SSL certificates.

3. Mention Content Pass in the Privacy Policy​

While Content Pass does not process non-subscribers' data, they receive 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 currently available in seven languages and can also be found on Content Pass pages - here.

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/

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.

  • No labels