Sunday 28 July 2013

Google Publisher Tag

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.


What are the benefits of using the new Google Publisher Tags?
There are multiple benefits of using these new tags:
  • 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 - Single request mode means that 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.

1 comment:

  1. If you are looking for a solid contextual advertising company, I recommend that you check out Chitika.

    ReplyDelete

Change to AdWords Enhanced CPC removes bid cap to account for location & audience

  AdWords users will notice a new alert in their accounts notifying them of changes to Enhanced CPC bidding.  The notice...