AdMob Announcements

You can now navigate to Automatically add your ad partnerand opt in to the Automatically add ad sources as ad partnersfeature, which will automatically add ad sources you set up using mediation as ad partners for consent collection via the Google CMP. Learn more .

The US state regulations messages available in the Privacy & messaging tool have been updated to support publisher compliance with new state privacy regulations in Indiana, Kentucky, and Rhode Island. We have also launched a new toggle to allow you to target a US state regulations message to "All current and future supported US States." To use these new settings:

• Existing US state regulations messages: Edit the message in Privacy & messaging to adjust the Targeting settings in the message builder to include the newly added states. The Geography selector now includes a "select all" option for "All current and future supported US States". Selecting this option will target your message to all currently regulated US states and automatically extend targeting to new states as their regulations go live and are supported by Google CMP.
• New US state regulations messages: All available US states will be selected by default in the Targeting settings in the message builder, and the "All current and future supported US States" feature will be toggled "on" by default.

Learn more about US state regulations messages .

Similar to other US states (for example: Colorado, Connecticut, Montana, Nebraska, New Hampshire, Texas, Minnesota, New Jersey, and Maryland), additional new US states, namely Delaware and Oregon, have similar universal opt-out mechanism or opt-out preference signals provisions. Starting November 17, 2025, for users in Delaware and Oregon, Google will receive Global Privacy Control (GPC) signals directly and trigger Restricted Data Processing (RDP) mode for those ad requests.

On January 1, 2026, Indiana, Kentucky, and Rhode Island will have privacy law provisions coming into effect, namely Indiana Consumer Data Protection Law, Kentucky Consumer Data Protection Act, and Rhode Island Data Transparency .

Google's approach in these states is similar to that of existing US states with active comprehensive laws . Activating Restricted Data Processing (RDP) mode turns off ad personalization, which may assist publishers in honoring opt-outs for targeted advertising and avoiding activities that could be considered a "sale" or "sharing" of user data.

Publishers can also choose to send RDP via GPP National v2 , which supports these new states.

Please note that publishers should still work with their legal teams to understand if RDP is the appropriate solution for their compliance. Publishers who currently leverage the RDP should work with their legal teams to understand if they should expand their use of RDP in additional states.

Consent syncing for apps synchronizes user consent decisions across your apps, improving the user experience by eliminating redundant consent prompts. This feature is available if you use European regulations messages in the Google CMP. By minimizing consent fatigue, you can increase user engagement and potentially boost ad revenue. To use this feature, you'll need to have multiple apps with overlapping users and be able to pass a cross-app user ID to Google via the UMP SDK. Get started in your Privacy & Messaging settings .

To align with evolving industry standards for user transparency and consent, all publishers and CMPs are required to transition to the IAB Europe's Transparency and Consent Framework (TCF) v2.3 by February 28, 2026. Google’s systems can accept and process TCF v2.3 strings today. As such we recommend that you begin this transition well ahead of the deadline to avoid disruption to ad serving. For details, visit Publisher integration with the IAB Europe TCF .

We’re expanding the Google AdSense, AdMob, and Ad Manager payout options. Building on the successful launch in the US, publishers in China and Argentina can now choose to receive their AdSense, AdMob, or Ad Manager earnings directly to their Hyperwallet account.

PayPal and cash pickup will be available for even more flexibility on how publishers get their payouts. Learn more about PayPal Hyperwallet .

Google AdMob publishers can send IDFV from your iOS apps to RTB demand (Authorized Buyers, Open Bidders, and SDK Bidders) when ads personalization is permitted. For now, IDFV for RTB demand is only available outside of the EEA, UK, Switzerland, and some US states.

Learn more about First-party identifiers and data .

Google AdMob now supports GPP National v2 strings. We will also continue to support GPP National v1 strings. Learn more about how Google supports the IAB's Global Privacy Protocol .

You will now be asked to declare if your AdMob campaigns include EU political content via a new Campaign-level "EU political content" field. If you declare "Campaign contains EU political content", restrictions will automatically apply once the new EU political ads policy launches in September.

We’ve launched the ad load latency metric in the Ads Activity Report. The ad load latency metric measures the time it takes from when an ad request is initiated to the time the ad response is returned from each ad source, and helps you:

• Better manage ad sources within mediation setup
• Understand the average latency by mediation groups, thus better manage the overall mediation chain
• Troubleshoot latency issues when any occurs

Learn more about the ad load latency metric .

From July 30 2025, we'll start to remove the "Significant Skin Exposure" sensitive category from Blocking controls. This change is part of an ongoing effort to give publishers more precise brand safety controls. Once this happens you will not be able to broadly block creatives that appear to show bare skin via this sensitive category.

If you don't have any existing blocks that use this category

You don't need to take any action. On July 30 2025, we'll remove the "Significant Skin Exposure" sensitive category from your Blocking controls.

If you do have existing blocks that use this category

On July 30 2025, we'll add a "Deprecated" label to the "Significant Skin Exposure" category in your Blocking controls. Then, beginning September 30 2025, your existing blocks will no longer apply. You will still be able to block unwanted creatives with exposed skin using more precise categories. To block unwanted ads with significant skin exposure, we recommend blocking the following categories if you believe these types of ads are unsuitable for your users:

• "Reference to Sex", "Sexual Reproductive Health" and "Dating" in sensitive categories
• "Swimwear" and "Underwear" subcategories under "Apparel" in general categories

Ads that violate Google's ads network policy and Google’s platform program policies will continue to be filtered and won’t show up in your app.

We recommend that you review and update your existing general category and sensitive category blocks within your Blocking controls to ensure that your brand safety requirements continue to be met effectively.

We've introduced a new Privacy & messaging report  type. This new report type shows data related to the way users interact with the messages you display in your apps. The metrics available in the report can help you understand which messages are reaching users and how those users are interacting with your messages.

To use the new Privacy & messaging report type, click Reports, then click Privacy & messaging.