What’s new in Google Ad Manager

Release notes for June 1, 2026

Follow along: Blog | YouTube | X | Optimization tips 

Review this article to learn about new Ad Manager features and enhancements. Updates are usually posted every other Monday. For previous releases, you can review the archive

Traffic and deliver ads

Day and time targeting for Private Auctions

From June 2026, day and time targeting will be available in Private Auctions. It will enable publishers to set time-based ad restrictions to run only during specific hours or days. Learn more about day and time targeting in Private Auctions.

Report and optimize

Interactive reports to replace legacy Reports

Starting this week, Interactive reports will be the official reporting tool for Ad Manager. Available to all publishers, Interactive reports offers an enhanced experience, including AI report generation, deeper analysis options, notification flags, charts, the ability to build and view reports on a single page, and more. All Ad Manager publishers should now be using Interactive reports, and finalizing their migration from the legacy Reports tool.
Image showing the "Reports" tool with a "Deprecated" label in Ad Manager reporting, with the "Interactive reports" feature labeled "new" above it

What to expect in June

Note the following changes happening in June as the migration to Interactive reports approaches completion:

  • Immediate redirects: Accessing the legacy Reports tool will now automatically redirect you to Interactive reports. You may navigate back to the legacy Reports landing page for a limited time.
  • Templates: The “Templates” tab is no longer accessible through the Ad Manager sidebar. Direct URL access will remain through the end of the month.
  • By the end of June: The Reports tool will be turned off. You may no longer create new reports or view previously saved reports in the legacy tool. However, you will still be able to migrate your old reports to Interactive reports for a limited time.

To learn more, visit About the migration to Interactive reports.

Manage network settings

Sync Ad partners with your bidder selections

Simplify your workflow with Bidder Syncing, a feature that automatically connects the Ad partners you collect consent for via the Google CMP to your chosen mediation and bidding sources. When enabled, your Google CMP ad partners are synced to match the Open Bidders, SDK Bidders, and Mediation Partners you’ve configured in your Ad Manager account.

To locate the setting, navigate to "Privacy & messaging," then click Settings on "European regulations," and scroll down to "Automatically add your bidders and mediation partners." The "Enable auto-adding" checkbox controls Bidder Syncing and is on by default. If desired, publishers can manually disable this setting before it goes into effect on or after June 17, 2026.

Policy

New signal for age-related compliance: Tag for age treatment (TFAT)

To help publishers navigate evolving global age-related regulations (such as US State App Store Bills, GDPR, and COPPA), Google is introducing the Tag for age treatment (TFAT). This new signal provides a unified way to manage ad request protections for different age groups.

  • Unified API migration: TFAT replaces the legacy tagForChildDirectedTreatment (TFCD) and tagForUnderAgeOfConsent (TFUA) settings, which will be deprecated in future GPT or SDK versions that support TFAT. 
  • Introduction of new TFAT setting:
    • CHILD: Functionally replaces TFCD/TFUA=True.
    • TEEN: (New) Publishers can now specifically signal for a "TEEN" age treatment. This applies specific ad-serving protections for teens.
    • UNSPECIFIED: Default state (equivalent to TFCD/TFUA=No or UNSPECIFIED).
      Passing UNSPECIFIED does not override user privacy consent strings (TCF/GPP) or other indications of sensitive users or content. Google will still apply the most conservative restriction present.
  • Publisher action required: Technical updates are needed to replace the deprecated tags with the new age treatment API in upcoming web (GPT) and app (GMA and IMA SDK) releases to facilitate compliance efforts and maintain access to the latest features.

Mobile app developers using the GMA SDK (iOS/Android) will see TFAT support in an upcoming minor release. While legacy TFCD/TFUA tags will continue through 2026, developers are encouraged to migrate to TFAT to avoid future compile errors when the tags are eventually removed in a major release (expected H1 2027). Support for Unity and Flutter is expected in H2 2026. Publishers should consult their legal counsel to determine the age treatment settings for their users based on their legal and regulatory obligations.

Policy Center access expanded to publishers with only reservation traffic

Access to the Policy Center interface is being extended to Ad Manager publishers who do not use Ad Exchange but use Ad Manager for reservation traffic. Learn more about Policy and Regulatory issues that may be affecting your app or web reservation inventory and how to fix them.

 

Coming soon

Sunset of the "Backwards" web interstitial trigger

Starting June 15, 2026, navigating backward using a browser's back button will no longer trigger an Ad Manager web interstitial across any supported browsers (including Chrome, Edge, and Opera). This update applies automatically to all publishers opted into the "Backwards" trigger and requires no publisher action. The change ensures compliance with Google Search's new policy against "back button hijacking."

Updated Ad Manager side navigation

We’re rolling out a positive, functional update to the side navigation interface to better align with Ad Manager's primary workflows and capabilities. It will be easier for publishers to find what they need, requiring fewer clicks to access the most used features. Note this is strictly an interface change and doesn’t impact product functionality. This update will rollout on May 19, 2026, for Ad Manager publishers, and on June 2, 2026, for Ad Manager 360 publishers.

Deprecation: Remarketing and interest based ads for non-Google demand
Soon, we will deprecate the "Remarketing" and "Interest-based category cookies" controls for non-Google demand in Protections to align our controls with corresponding fields in OpenRTB. Removing these controls will also remove the ID redaction behavior currently tied to them. We expect impact to be limited, and encourage you to use ads personalization settings for any serving restrictions. Note that the network level Google Demand control for "Remarketing" will remain for now.

See previous release notes

Was this helpful?

How can we improve it?
true
Unlock your revenue with personalized tips today!

Visit the Optimization tips for Google Ad Manager page to see personalized suggestions to maximize your revenue.

Unlock now

Search
Clear search
Close search
Main menu
5609214753379262600
true
Search Help Center
false
true
true
true
true
true
148
false
false
false
false
false