On July 30, 2026, AdGlobeX Media said on LinkedIn that it would bring new optimization updates to its publishers first, and that every strategy is tested by the team before it is recommended. The first example it shared was Google Ad Manager's "Google optimized" refresh rate setting.

What AdGlobeX reported

In a team member's post on optimized refresh, reshared on the company page, the team said it had tested the optimized refresh rate across its inventory and found the results promising. It did not publish figures, so we will not quote any. Its recommendation was to test the feature on a small scale before switching it on everywhere.

The five-step test plan

AdGlobeX suggested the following process:

  1. Create a test ad unit. Give it an obvious name such as "Testing".
  2. Place it well. Put it in a high-visibility position, for example the header or main slot.
  3. Enable optimized refresh. Choose the right sizes when creating the unit and turn on the Google optimized refresh rate.
  4. Watch the numbers for one to two days. Track CPM, viewability, revenue and user experience.
  5. Roll out gradually. If the results hold up, apply the same refresh setting to more units.

The team added that the feature tends to suit publishers with large, high-quality inventory, where Google's machine learning has more data to time refreshes well.

What Google's documentation says

Google's help page on refresh rate describes the setting at the ad unit level for mobile app inventory, with three options: disabled (the default), Google optimized, or a custom interval between 30 and 120 seconds. Two details are easy to miss:

  • a refresh rate set on a parent ad unit does not carry over to its child units, so each one needs its own setting;
  • the refresh rate applies across all demand sources, so it must also respect the policies of indirect demand partners.

For websites, refresh is handled differently. Google requires publishers to declare refreshing inventory, including the trigger and the minimum interval, and treats undeclared or understated refresh as a policy violation. Time-based and event-based refreshes need at least 30 seconds between ads.

Why "test first" is the right habit

Refresh can lift impressions, but it can also reduce viewability and per-impression value if it fires too often. A controlled test on one unit shows the trade-off for your own audience before it affects the whole site or app.

We will keep testing features like this one before we recommend them. If you would like that approach applied to your own inventory, request a review of your Ad Manager account.