Google is not currently a signatory to the IAB Privacy’s Limited Service Provider Contract. We have however integrated with the IAB CCPA Framework v1.0 Technical Specifications in Ad Manager, AdSense, and AdMob as detailed below.
Google supports the IAB Tech Lab’s v1.0 technical specifications for reading the
us_privacy string in our publisher ad products and applies restricted data processing when the string indicates a user has opted out (additional detail below).
Our ad tags will interact with the publisher’s page to retrieve the
us_privacy string. Publishers who choose to use the IAB signal should follow the technical specification provided by the IAB Tech Lab to implement the
us_privacy string on their pages.
- When the IAB string indicates a user has not opted out, there will be no changes to ad serving behavior and the IAB signal will not be propagated further to other vendors.
- When the IAB string indicates a user has opted out, Google will enable restricted data processing (as outlined in our help center for Ad Manager, AdSense, AdMob). When restricted data processing is enabled, Google does not call out to third parties via RTB and the signal would not be propagated further to other vendors.
AdSense for Search, AdSense for Shopping, and AdSense for Domains
For AdSense for Search, AdSense for Shopping, and AdSense for Domains, the IAB signal support will launch at the end of January. Publishers who wish to restrict data processing may do so by following these instructions.
Please see the app developer site for more information on implementing the
us_privacy string for the Google Mobile Ads SDK.
IMA SDK support
Please see the IMA SDK developer site for more information on implementing the
us_privacy string for the Google Interactive Media Ads SDK.
IMA DAI SDK
- HTML 5 IMA DAI SDK
- iOS IMA DAI SDK
- Android IMA DAI SDK
- tvOS IMA DAI SDK
- Google Cast IMA DAI SDK
- Roku IMA DAI SDK
Learn more about helping publishers comply with U.S. privacy laws.