EU user consent policy

Publisher EU user consent journeys

Publishers may choose several different paths to obtaining consent from their EEA users to comply with Google’s updated EU Consent policy, and can still work with Google publisher products.

1. Publisher builds their own consent solution

  1. Go into AdSense and choose your Ad Technology Providers (ATPs)
  2. Use GPT API to pause ads loading on page load (disableInitialLoad())
  3. Trigger consent tool, ask for consent for Google and selected ATPs
    • User consents to Personalised Ads – resume ads loading (refresh())
    • User consents to Non-Personalised Ads – load NPA ads (setRequestNonPersonalisedAds(1) + refresh())
    • User doesn't consent to Google – don't make an ad call to Google

More details can be found in the Ads Personalisation Settings in Google’s publisher ad tags help page.

2. Publisher uses IAB Framework

We haven't yet integrated with the IAB Transparency & Consent Framework (TCF). We've been working with IAB Europe over the last several months to explore how our products and policies can support the TCF, but our technical integration isn't complete.

Until Google’s IAB integration is complete, Google will return personalised ads for the Ad Technology Providers selected in the publisher ATP controls. Publishers will continue to have the option to include the non-personalised ad signal in their ad request or choose to serve only non-personalised ads to all users in the EEA in the AdSense UI. Also note that the IAB TCF technical specifications support web; the specifications for mobile app aren't finalised.

Was this helpful?
How can we improve it?