What's new in Google Ad Manager

Release notes for November 18, 2019

Traffic and deliver ads

Trafficking improvements

The trafficking experience has recently gone through some significant changes. We're actively listening to your feedback and continue to work hard to improve your experience. In the coming months, you can expect improvements to the targeting picker, creative bulk upload, calendar input, bulk actions, and more. Learn more

Report and optimize

New reporting experience for Ad Manager

We’ve designed an improved Ad Manager reporting experience, including several updates across the reporting user interface to streamline common processes. Reporting will gradually transition to this new experience over the coming month. Learn more

Improved compatibility for ad speed

Custom dimensions in the Ad speed report and the Ad speed Home dashboard are now compatible with metrics in the “Creative load time” and “Non-viewable reason” metric families. This increases the flexibility of ad speed reporting in Ad Manager and offers you greater insight into the latency across your network.

Forecast inventory

Forecasting for European Economic Area traffic

You can now more accurately forecast on line items by specifying how traffic is expected to be served to users in the European Economic Area (EEA). The “Limit EEA serving” dropdown, which already appears in line item settings, now also appears when you check inventory. Note that this forecasting launch has no impact on delivery.

To use the new forecasting setting:

  1. In Ad Manager, navigate to Delivery and then Orders or Delivery and then Line items.
  2. Next to “New order,” click Forecasting.
  3. On the “Ad type” page, keep the default of Standard and click Select.
  4. In the “Adjust Delivery” section, make a selection from the “Limit EEA serving” dropdown and complete your forecast.

Note that "Limit EEA serving" doesn’t always appear in forecasting settings:

  • If you're using the new forecasting user interface: The "Limit EEA serving" setting appears if you have elected to "Limit line items" on the "EU user consent" page. The default setting is Don't serve for any EEA ad requests.
  • If you revert to the previous forecasting user interface: You won't see the "Limit EEA serving" setting. However, if you have you have elected to "Limit line items" on the "EU user consent" page, the default setting, Don't serve for any EEA ad requests, will still be applied to the forecast.

Learn more about setting up forecasts and about the “Limit EEA serving” setting.

Other product news and updates

Market study by the UK Competition & Markets Authority (CMA)

The UK Competition & Markets Authority (CMA) is conducting a market study into online platforms and the digital advertising market in the UK. In connection with the market study, at the CMA's direction, Google is providing the CMA with a very small random sample of UK ad impression data covering the period June through September 2019 and representing less than $5,000 revenue in aggregate across all included impressions.

 

Coming soon

  • Updates to Demand Channel reporting dimension
    Beginning in January 2020, the Demand Channel reporting dimension will be updated. Exchange Bidding will be renamed Open Bidding, both retroactively and moving forward for consistency within the product. Additionally, for publishers involved in the beta for Network Bidding, this reporting dimension will also be renamed Open Bidding. If this causes changes to your reporting process, we encourage you to plan accordingly before this change occurs next year.

  • Preparing for changes to mobile app impression counting
    The new “Ad server provisional impressions” metric and the new “Ad server SDK status” dimension will be introduced soon to help you prepare for upcoming changes to the counting methodology used for mobile app impressions. You will be able to use the new metric and dimension to learn more about the impact of these changes on your network and whether you need to update the Google Mobile Ads SDK in your apps. Learn more

See previous release notes

Was this helpful?
How can we improve it?