Serve users with Limited Ads
Stay organized with collections
Save and categorize content based on your preferences.
As of January 14th 2021, the IMA HTML5 SDK
allows limited ads to be served
when the user does not give consent to cookies, the user denies consent to
cookies, or when IMA does not receive a valid TC string in GDPR and ePrivacy
regions following the grace period of IAB TCFv2 integration.
For DAI SDKs you must set the
ltd parameter using
StreamRequest.adTagParameters
.
Please see this
Limited ads guide for
more information.
Publishers using Google Publisher Tag (GPT) will need to also set
PrivacySettingsConfig.limitedAds
to disable GPT-related cookies. The following code snippet shows how to do this
based on
IMA's companion ads guide:
...
<!-- Register your companion slots -->
<script type='text/javascript'>
googletag.cmd.push(function() {
googletag.pubads().setPrivacySettings({
limitedAds: true,
});
// Supply YOUR_NETWORK and YOUR_UNIT_PATH.
googletag.defineSlot('/YOUR_NETWORK/YOUR_UNIT_PATH', [728, 90], 'companionDiv')
.addService(googletag.companionAds())
.addService(googletag.pubads());
googletag.companionAds().setRefreshUnfilledSlots(true);
googletag.pubads().enableVideoAds();
googletag.enableServices();
});
</script>
...
Publishers are still responsible for playback of the stream manifest. The
manifest URL continues to point to dai.google.com which is a cookied domain and
may carry cookies. Because of this, the player needs to be configured to
correctly request the manifest
withCredentials=false.
Please see the following links to set this for your specific player:
It is also possible to enable limited ads automatically through integrating with
a Consent Management Platform (CMP). This is supported on
the latest version of the HTML5 SDK as of January 14th 2021.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-20 UTC.
[null,null,["Last updated 2025-08-20 UTC."],[[["\u003cp\u003eAs of January 14, 2021, the IMA HTML5 SDK can serve limited ads even when users don't consent to cookies or in GDPR/ePrivacy regions without a valid TC string.\u003c/p\u003e\n"],["\u003cp\u003ePublishers using Google Publisher Tag (GPT) need to configure PrivacySettingsConfig.limitedAds to disable GPT-related cookies for limited ads functionality.\u003c/p\u003e\n"],["\u003cp\u003eWhen using limited ads, ensure the player is configured to request the stream manifest with \u003ccode\u003ewithCredentials=false\u003c/code\u003e due to potential cookies from dai.google.com.\u003c/p\u003e\n"],["\u003cp\u003eLimited ads can be automatically enabled through integration with a Consent Management Platform (CMP) using the latest HTML5 SDK version.\u003c/p\u003e\n"]]],[],null,["# Serve users with Limited Ads\n\nAs of January 14th 2021, the IMA HTML5 SDK\nallows [limited ads](//support.google.com/admanager/answer/9882911) to be served\nwhen the user does not give consent to cookies, the user denies consent to\ncookies, or when IMA does not receive a valid TC string in GDPR and ePrivacy\nregions following the grace period of IAB TCFv2 integration.\nFor DAI SDKs you must set the [`ltd`](//support.google.com/admanager/answer/7320899#ltd) parameter using [`StreamRequest.adTagParameters`](/interactive-media-ads/docs/sdks/html5/dai/reference/js/StreamRequest#adTagParameters) . Please see this [Limited ads guide](//support.google.com/admanager/answer/9882911) for more information.\n\n\u003cbr /\u003e\n\nPublishers using Google Publisher Tag (GPT) will need to also set [PrivacySettingsConfig.limitedAds](/publisher-tag/reference#boolean-limitedads) to disable GPT-related cookies. The following code snippet shows how to do this based on [IMA's companion ads guide](/interactive-media-ads/docs/sdks/html5/client-side/companions):\n\n\u003cbr /\u003e\n\n```carbon\n...\n\n\u003c!-- Register your companion slots --\u003e\n\u003cscript type='text/javascript'\u003e\n googletag.cmd.push(function() {\n googletag.pubads().setPrivacySettings({\n limitedAds: true,\n });\n // Supply YOUR_NETWORK and YOUR_UNIT_PATH.\n googletag.defineSlot('/YOUR_NETWORK/YOUR_UNIT_PATH', [728, 90], 'companionDiv')\n .addService(googletag.companionAds())\n .addService(googletag.pubads());\n googletag.companionAds().setRefreshUnfilledSlots(true);\n googletag.pubads().enableVideoAds();\n googletag.enableServices();\n });\n\u003c/script\u003e\n\n...\n```\nPublishers are still responsible for playback of the stream manifest. The manifest URL continues to point to dai.google.com which is a cookied domain and may carry cookies. Because of this, the player needs to be configured to correctly request the manifest `withCredentials=false`.\n\n\u003cbr /\u003e\n\nPlease see the following links to set this for your specific player:\n\n- [hls.js](//github.com/video-dev/hls.js/blob/master/docs/API.md#xhrsetup)\n- [JW Player](//developer.jwplayer.com/jwplayer/docs/jw8-player-configuration-reference#section-advertising) (scroll for `withCredentials` property)\n- [Shaka Player](//github.com/google/shaka-player/blob/master/docs/tutorials/ad_monetization.md#disabling-cookies-for-serving-limited-ads)\n\nIt is also possible to enable limited ads automatically through integrating with\na Consent Management Platform (CMP). This is supported on\n\nthe latest version of the HTML5 SDK as of January 14th 2021."]]
