Take the 2024 Google Publisher Tag developer survey

Monday, May 20, 2024

As we look forward to another year, it's time once again to check in with our developer community to see what's working well and what can be improved. Starting today, we're kicking off the 2024 GPT developer survey.

Take the survey
The survey should take no more than 10 minutes to complete, and it will be open through the end of June 2024. Most questions are optional and your answers are anonymous.
Remember that the feedback you provide influences what we work on over the course of the next year, so please let us know what matters most to you. Thanks in advance for taking the time to help improve the GPT developer experience!
- Jonathon Imperiosi, Google Publisher Tags Team

Take the 2022 Google Publisher Tag developer survey

Thursday, September 1, 2022

Since 2020, we've asked the Google Publisher Tag (GPT) developer community to provide their valuable feedback through an annual survey. This feedback influences what we work on each year, and has directly inspired improvements to our sample offerings, release notes, and much more. As we look forward to next year, it's time once again to check in with our developer community to see what's working well and what can be improved. Starting today, we're kicking off the 2022 GPT developer survey.

Take the survey

The survey should take no more than 10 minutes to complete, and it will be open through the end of October 2022. Most questions are optional and your answers are completely anonymous. Remember that the feedback you provide influences what we work on over the course of the next year, so please let us know what matters most to you. Thanks in advance for taking the time to help improve the GPT developer experience!

- Jonathon Imperiosi, Google Publisher Tags Team

Take the 2021 Google Publisher Tag developer survey

Tuesday, October 5, 2021

The survey should take no more than 10 minutes to complete, and it will be open through the end of October 2021. Most questions are optional and your answers are completely anonymous.

Remember that the feedback you provide influences what we work on over the course of the next year, so please let us know what matters most to you. Thanks in advance for taking the time to help improve the GPT developer experience!

- Jonathon Imperiosi, Publisher Ads Audits Team

Take the survey

- Jonathon Imperiosi, Publisher Ads Audits Team

Introducing Publisher Ads Audits for Lighthouse v1.5.0

Monday, July 12, 2021

- Jonathon Imperiosi, Publisher Ads Audits Team

Today, we're announcing the general release of Publisher Ads Audits for Lighthouse v1.5.0. The major highlights of this release are:

A number of smaller enhancements and fixes are also included. For complete details, see the release notes and the changelog on GitHub.

Try it out and let us know what you think

Publisher Ads Audits v1.5.0 is already available to use. You can try generating an updated report from the web app, or grab the latest CLI release from GitHub or npm to run locally. Updates to the Chrome DevTools version will land in Chrome Stable with the Chrome 94 release (est. Sept 2021).

Have questions about this or anything else Ad Speed related? Interested in contributing? Visit our GitHub repo.

- Jonathon Imperiosi, Publisher Ads Audits Team

Introducing Publisher Ads Audits for Lighthouse v1.4.1

Wednesday, February 10, 2021

- Jonathon Imperiosi, Publisher Ads Audits Team

Publisher Ads Audits for Lighthouse

New audits to check for Google Publisher Tag errors and warnings.

Updated thresholds for ad and bid requests when using simulated throttling.

Updates to support Lighthouse v7.0.0.

changelog on GitHubv6.5.0Helping ensure Google Publisher Tags are used correctly

deprecated-api-usage - this audit looks for usage of GPT API features that have been deprecated. These features may be removed in the future and are no longer actively maintained. Consult the GPT release notes for alternatives to use.

gpt-errors-overall - this audit surfaces all warnings and errors thrown by GPT during page load. The severity of these issues can vary depending on a number of factors, so you need to review the results and decide whether there's anything that needs to be addressed for your site.

Try it out and let us know what you thinkweb appGitHubnpmGitHub repo

- Jonathon Imperiosi, Publisher Ads Audits Team

Introducing Publisher Ads Audits for Lighthouse v1.3.0

Friday, November 20, 2020

- Jonathon Imperiosi, Publisher Ads Audits Team

Publisher Ads Audits for Lighthouse

A number of smaller enhancements and bug fixes are also included. For complete details, see the changelog on GitHub. Additional Lighthouse changes included in this release can be found in the v6.3.0 and v6.4.0 release notes.

Try it out and let us know what you think

Publisher Ads Audits v1.3.0 is available to use right now. You can try generating an updated report from the web app, or grab the latest CLI release from GitHub or npm to run locally. Updates to the Chrome DevTools version will land in Chrome Stable with the Chrome 89 release (est. March 2021).

Have questions about this or anything else Ad Speed related? Interested in contributing? Visit our GitHub repo.

- Jonathon Imperiosi, Publisher Ads Audits Team

Help improve the Google Publisher Tag developer experience

Wednesday, September 9, 2020

Take the survey

- Jonathon Imperiosi, Publisher Ads Audits Team

Introducing Publisher Ads Audits for Lighthouse v1.2.0

Friday, August 28, 2020

- Jonathon Imperiosi, Publisher Ads Audits Team

Today, we're announcing the general release of Publisher Ads Audits for Lighthouse v1.2.0. The major highlights of this release are:

A number of smaller enhancements and bug fixes are also included. For complete details, see the changelog on GitHub.

Measuring the impact of ads on the user experience

The new cumulative ad shift metric is the first publisher ads audit aimed at measuring the impact of ads on Core Web Vitals metrics. In particular, this metric provides insight into how ads affect the stability of your page's layout. To learn more about how ads affect layout stability and steps you can take to address this, see our article on minimizing layout shift with GPT.

The APIs for measuring layout stability are new and still evolving, so it's not currently possible to attribute layout shifts to ads with 100% accuracy. We'll be updating this audit as these APIs mature, so scores may change over time.

Try it out and let us know what you think

Publisher Ads Audits v1.2.0 is available to use right now. You can try generating an updated report from the web app, or grab the latest CLI release from GitHub or npm to run locally. Updates to the Chrome DevTools version will land in Chrome Stable with the Chrome 87 release (mid-November).

Have questions about this or anything else Ad Speed related? Interested in contributing? Visit our GitHub repo.

- Jonathon Imperiosi, Publisher Ads Audits Team

Improving the accuracy of Publisher Ads Audits for Lighthouse mobile reports

Wednesday, April 29, 2020

Today we're releasing an update to Publisher Ads Audits for Lighthouse, which focuses on improving the real-world accuracy of mobile reports via simulated throttling. Continue reading to learn more about the new simulated throttling option and how it will affect mobile audit scores.

What is simulated throttling?

Until now, all audit scores were based on the result of loading your page on a desktop CPU over an unthrottled, wired broadband connection. While mobile audits request the mobile version of your page (by identifying as a Nexus 5X phone), the results did not reflect actual mobile CPU and bandwidth constraints.

To address this, we are introducing a simulated throttling option. When enabled, mobile audit scores are calculated by first auditing your page under normal conditions, then using this data to simulate page load performance under mobile conditions. The simulation uses the Lighthouse mobile network throttling preset, which artificially limits both CPU speed and network bandwidth. This approximates the performance of an actual mobile device loading your site over a fast 3G connection.

Note that simulated throttling only applies to mobile audits. Desktop audits will not be throttled regardless of whether this new option is enabled or not.

How does this affect me?

The new simulated throttling option will be enabled by default for all newly generated reports, matching the behavior of other performance auditing tools such as Lighthouse, PageSpeed Insights, and the Chrome DevTools Audits' panel. It can be disabled on a per-report basis by toggling the option in advanced settings.

While metric thresholds have been adjusted to account for simulation, we expect this new option may cause scores to change for many pages that were previously audited without throttling. If you audit your page regularly and have established a performance baseline based on the previous mobile audit behavior, you may need to establish a new baseline to account for these differences.

Questions or feedback about this or anything else ad speed related? Reach out on our GitHub issue tracker.

- Jonathon Imperiosi, Publisher Ads Audits Team

Ads Developer Blog

Take the 2024 Google Publisher Tag developer survey

Take the 2022 Google Publisher Tag developer survey

Take the 2021 Google Publisher Tag developer survey

Introducing Publisher Ads Audits for Lighthouse v1.5.0

Introducing Publisher Ads Audits for Lighthouse v1.4.1

Introducing Publisher Ads Audits for Lighthouse v1.3.0

Help improve the Google Publisher Tag developer experience

Introducing Publisher Ads Audits for Lighthouse v1.2.0

Improving the accuracy of Publisher Ads Audits for Lighthouse mobile reports

Labels

Archive