OKO Digital

The ad optimisation people

  • Home
  • Publisher Solutions
    • Website Monetization
    • Header Bidding
    • AdX – Google Ad Exchange
    • App Ad Monetization
    • WordPress Monetization
  • About us
    • OKO & the OKO team
    • Careers
  • Blog
    • Latest blog posts
    • Ad Blocking
    • Ad Exchange (AdX)
    • Ad Optimisation
    • Ad Performance & Page Speed
    • Ad Publishing Landscape
    • AdSense
    • DoubleClick For Publishers (DFP)
    • Exchange Bidding
    • Google Ad Manager
    • Google Certified Publishing Partners
    • Header Bidding
    • Privacy & GDPR
    • Program Policy
    • Open Bidding
    • Traffic
  • Contact

Privacy and GDPR . 11th July 2019

Integrating Quantcast Choice with Google Ad Manager

How to integrate Quantcast Choice with Google Ad Manager

Quantcast Choice is a popular Consent Management Platform (CMP) for publishers for good reasons. It’s well proven, easy to set-up, free to use and utilises the IAB Consent Management Framework.

That framework ensures that the consent users give is passed to every demand partner who has also adopted the standard framework. The problem that publishers face is that Google aren’t signed up to that framework, so additional steps are needed to ensure that any Google ads served to a user honour that user’s consent preference.

Tying ads behind a yes/no to consent

Quantcast choice now makes it easier to honour user preference and meet Google EU User Consent standards as it now has out of the box compatibility with support for Google’s advertising products.

The simplest solution is to delay showing ads to the user until after consent has been gained. Great! But how do you actually do that?

Firstly, you’ll want to make sure you are not going to serve ads until the user has agreed to your consent popup. To do this we need to use the disableInitialLoad() function within Google’s API.

Quantcast1

You’ll need to make sure that the disableInitialLoad() function is before enableServices().

To get the ads to fire after consent is recorded we will use the refresh() function, but more on that later.

Implementation within Quantcast choice CMP

In order for the CMP to perform its duties, we need to link our decision to serve personalized ads with what consent is recorded by the CMP.

To do that we will use the following code, appended to the bottom of the ‘out of the box’ Quantcast choice code:

Quantcast2

How does this work?

Once the CMP has loaded, this extra snippet will make the decision on whether or not personalized ads are shown.

If the CMP records a positive result and the user has given their consent for personalized ads, the refresh() function is called, overriding the previous disableInitialLoad() function and your Ad Manager ad units will fire as normal.

If no consent is given by the user, the CMP will change the request to Ad Manager to only retrieve non-personalized ads using the function: setRequestNonPersonalizedAds(1).

For more information on the EU User Consent Policy, download our free guide.

Privacy and GDPR . Tips

About Abbey Colville

SEARCH

TOPICS

  • Ad Blocking
  • Ad Exchange (AdX)
  • Ad Optimisation
  • Ad Performance & Page Speed
  • Ad Publishing Landscape
  • AdSense
  • DoubleClick For Publishers (DFP)
  • Exchange Bidding
  • Google Ad Manager
  • Google Certified Publishing Partners
  • Header Bidding
  • Open Bidding
  • Privacy & GDPR
  • Program Policy
  • Traffic

Could the ads on your site be earning more?

Find out how OKO help publishers earn more from their ads.

LEARN MORE
Insticator

OKO Digital, The Cake Shed, Manor Farm, Manor Road, Hayling Island, Hampshire, PO11 0QW

Google Certified Publisher Partner Logo

OKO is a registered trademark and trading style of OKO Digital Limited. Registered in England company number 03867231. © OKO Digital Limited 1996-2018. All Rights Reserved.

  • Privacy Policy
  • Cookie Policy
Manage Cookie Consent
We use cookies to optimise our website and our service.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage vendors Read more about these purposes
View preferences
{title} {title} {title}