Clear search
Close search
Google apps
Main menu

Google Publisher Console

If your network uses Google Publisher Tags (GPT), you can use an on-screen debugging tool called the Google Publisher Console to troubleshoot delivery problems. The console checks your page for many common JavaScript tagging errors, identifies all of the ad units and creatives on the page, and helps you visualize the ad request behavior of a web page.

There are several ways to view the Publisher Console on webpages containing Google Publisher Tags:

  • After loading the page, enter javascript:googletag.openConsole() in your browser’s address bar. You can bookmark this URL for easy access.
  • After loading the page, enter googletag.openConsole() in your browser’s JavaScript console.
  • Before loading the page, append the query string parameter google_console=1 to your page's URL to make the Publisher Console toggleable using a keyboard shortcut (see below) or google_force_console=1 to cause the Publisher Console to display automatically after the page is loaded. For example:

After you’ve loaded the Publisher Console using any of the above methods, you can subsequently toggle it on or off using the keyboard shortcut Ctrl+F10 (on a Mac, use Function+Ctrl+F10).

The Publisher Console has two main tabs that display page information: "Ad Slots" and "Page Request", as well as a settings page under the gear icon in the right top corner. These features are described in the sections below.

The Ad Slots tab

The Ad Slots tab displays the following information:

  • Publisher's DFP ID
  • Creative size
  • Time to fetch and render this ad
  • Links to helpful debugging information
  • Whether the ad slot uses SafeFrame, friendly iframes, or no iframe

There are three links within the Ad Slots tab that help you find the most important information quickly:

  • Open Ad Unit in DFP: Opens the ad unit in the "Inventory" tab in their network.
  • Delivery diagnostics: Opens a new window with information about which line item is serving and the other line items eligible to serve to that ad slot.
  • Open Creative in a New Window: Opens the creative in a new window.

To use the "Open Ad Unit in DFP" and "Delivery Diagnostics" links, you must be logged into a DFP network. Although the use of the Google Console is not restricted to the site owner, private network information through these links are not accessible to the public.

The Page Request tab

The Page Request tab displays the following information:

  • Tag checker will show a green checkmark with the message "Page tagged correctly!" if there are no tagging errors
  • Time to fetch and render ads
  • HTTP user agent information
  • Timeline of events in rendering ads, like the sequential view in a web proxy tool console

This tab can help troubleshoot why a page is loading slowly by showing the sequence of events that occurs during a page load.

From this tab, you can also reload the page by selecting one of the following options from the "Reload Page" drop-down:

  • Reload the page normally (requests and renders ads)
  • Reload without ads (does not request or render ads)
  • Reload without rendering ads (requests but does not render ads)
An ad request URL has a character limit, depending on the tag type. If the character count for your ad request exceeds the limit and gets truncated, the console will display an error: "Ad unit failed to fetch." Learn more

You can see a full list of Google Publisher Console warnings and error explanations.

Additional troubleshooting for tagged pages

You can analyze and optimize site performance using speed optimization tools, such as Google Pagespeed. This will ensure page loads are fast and reliable, including ad rendering time.

When optimizing for speed, the use of asynchronous GPT tags is recommended.

Was this article helpful?
How can we improve it?