Search
Clear search
Close search
Google apps
Main menu

Google Publisher Console

If your network uses Google Publisher Tags (GPT), you can troubleshoot delivery problems using the Google Publisher Console. This on-screen debugging tool 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 webpage.

View the Publisher Console

There are three ways to view the Publisher Console on webpages containing Google Publisher Tags.

Option 1 (recommended): javascript:googletag.openConsole()

This JavaScript function call opens the Google Publisher Console at any point while viewing a page that has the GPT library loaded.

You can create a bookmark that executes the JavaScript necessary to open the Google Publisher Console. You can set this on any browser in desktop or mobile web environments.

To create the bookmark in Chrome:

  1. In Chrome, click the More icon More and then select Bookmarks and Bookmark Manager.
  2. In the Bookmark Manager, right-click where you’d like to add the bookmark and click Add page....
  3. Enter a name (e.g., Publisher Console).
  4. Copy and paste this code into the “URL” box:
    javascript: googletag.openConsole();
  5. Navigate to a website.
  6. Click on your newly created bookmark to open the Publisher Console.
    • The bookmark will appear where you placed it in step 2. For example, it may be in the bookmarks bar under the address bar.
    • For mobile web, you may need to load the bookmark through the address bar.
Option 2: googletag.openConsole()

After loading the page, enter googletag.openConsole() in your browser’s JavaScript console.

Option 3: google_console=1
This option doesn’t work on all websites.

Before loading the page, append one of these query string parameters to your page’s URL:

  • google_console=1: Makes the Publisher Console toggleable using a keyboard shortcut (see below).
    Example: http://www.example1.com?google_console=1
  • google_force_console=1: Causes the Publisher Console to display automatically after the page is loaded.
    Example: http://www.example2.com?p1=AAA&p2=BBB&google_force_console=1

Turn the Publisher Console on or off

After you’ve loaded the Google 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 fn+control+F10).

To prevent the Google Publisher Console from loading on subsequent page loads, be sure to close out of the Console. Click the x button in the upper right corner of the Console.

See page information

The Publisher Console has two main tabs that display page information: "Ad Slots" and "Page Request", as well as a settings page under the Settings icon Settings in the top right corner.

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

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. This is useful for understanding why a line item did or did not serve to this slot.
  • Open Creative in 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 Publisher Console is not restricted to the site owner, private network information through these links are not accessible to the public.
Page Request tab

The Page Request tab can help troubleshoot why a page is loading slowly by showing the sequence of events that occurs during a page load. It displays the following:

  • Tag checker, which shows 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

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

  • Normally: Requests and renders ads.
  • Without ads: Does not request or render ads.
  • 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.
Was this article helpful?
How can we improve it?