Introducing the Google Publisher Tag

What is the Google Publisher Tag (GPT)?

GPT is an ad tagging library with which you can dynamically build ad requests. GPT takes key details from you such as ad unit name, ad size, and custom targeting, builds the request, and displays the ad on web pages or mobile apps (learn more about tagging for mobile sites and applications). You can define shared settings such as targeting at a page level instead of defining the same targeting for individual ads on the page. You can also control how and when ad requests are made. For example, you can render ads asynchronously so that they don't block other elements on the page and you can use single-request architecture to call all ads once in the header of your page.

Benefits of using GPT

There are multiple benefits of using these tags:

  • Five-level inventory hierarchy: The Google Publisher Tag allows you to use more granular levels of inventory in the DFP front-end. With five levels of hierarchy, you'll be able to create much more specific targeting based on your site content. For example, you could create inventory on an electronics site to target the following structure:

    Electronics > TVs > LCD > Brand > Under_1000

  • Faster page loads: An asynchronous JavaScript fetch means that instead of waiting for the JavaScript to be returned from the DoubleClick servers, the page continues rendering and loads the ads into iframes when the creatives are returned from the server.

  • Google Publisher Console: The tag comes with a built-in debugging and support tool called the Google Publisher Console, which is enabled on all pages containing the Google Publisher Tag. To activate the Publisher Console, load your webpage containing Google Publisher Tags into a browser and append ?google_console=1 to the URL and use the keyboard shortcut Ctrl+F10 to toggle the console. Alternatively, you can append ?google_force_console=1 to your page's URL. This causes the console to be automatically displayed when the page is loaded, rather than requiring the keyboard shortcut. The console provides checks for common tagging errors, visual highlights of all ad units and creatives on the page to help with debugging, and an alternative point of entry into the DFP front-end.

  • Single request mode: Instead of sending individual ad requests to DoubleClick servers, the browser is able to send one request notifying the server of all ad units on the page. This enables advanced roadblocking and improves page load time.

  • Automated setup for interstitials: DFP lets you specify that your tags are for an out-of-page unit and automatically adds the additional code. There's no need to add code manually.

How GPT works

The Google Publisher Tag is used to define available ad slots on your organization's website/network. Placing a tag on a page creates a communication path between the ad server and a user’s browser. When a page containing a Google Publisher Tag is rendered, the following sequence of events occurs:

  1. A request is made from the user's browser to the ad server for gpt.js, the tagging JavaScript.

  2. The tagging JavaScript builds and sends one or more requests (depending on whether single-request mode is enabled) to the ad server for ads tagged on the page.

  3. The ad server recognizes the ad units and any custom targeting contained within the request.

  4. The ad server selects and returns the best matching ad.

  5. The JavaScript code associated with the ad tag displays the ad on the page.

GPT and secure pages (https://)

GPT works automatically with secure webpages whose URLs begin with https://. There's no need to modify the tag in any way for serving on a secure page.

HTTPS stands for HyperText Transfer Protocol Secure. It's a communications protocol that's built on top of the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols. These protocols encrypt certain elements of the communication between the server and the client in order to prevent tampering and eavesdropping by third parties.