Google Ad Manager (GAM) – Responsive Banner Ads

Follow

NOTE: Google's Ad Manager (GAM) was previously known as DoubleClick for Publishers (DfP). Google changed the name in 2018, though most features remain unchanged. In some videos and documentation you may still find reference to DfP.  

 


 

Part 01: Setting up GAM and scheduling a Responsive Ad

The video above demonstrates how to set up your GAM account and create a basic line item. 

 

Ad Units

dfp2-ads.jpg

Metro Publisher's integration with Google Ad Manager includes three default ad units to get you started. 

  1. 970x90 leaderboard top
  2. 970x90 leaderboard nav
  3. 970x90 leaderboard bottom

    NOTE: Use Sprockets to insert additional ad units on your section landing pages and within content.


    Deprecated
    As trends have evolved on the web and Metro Publisher has released new features, some of ad units have gone out of use. The three ad units below are used only by older clients and are considered deprecated:
  4. 300x250 mpu right
  5. 160x600 wallpaper left
  6. 160x600 wallpaper right

 

Part 02: Targeting your ads with Key Values

NOTE: GAM recently updated its interface. Please note that what formerly was labeled "Custom Targeting" or "Custom Criteria" are both now called "Key Values." 

This video shows how to use key value targeting within your line items to place ads in specific sections of your website. 

Using the tags automatically generated by Metro Publisher, you can use GAM's key value targeting to serve ads custom tailored to the needs of your advertisers.

Example Keys:

key: instance
types: sitename
 
key: section
types: @top, section_urlname
 
key: subsection
types: subsection_urlname

key: type
types: section, subsection, article, event_search, event, homepage, location_search, location, review, roundup.
 
key: tag
types: tag title
 
key: urlname
types: corresponding URL Name value on the page you're targeting
 
To target the homepage:
 
Targeting key = section
Targeting value = @top
 
OR
 
Targeting key = type
Targeting value = homepage
 
To target the the music section only:
 
Targeting key = section
Targeting value = music
 
 
To target a certain event search:
 
In this case, the event search has been assigned to a section called "Listings"
 
Targeting key = section
Targeting value = listings
 
To target an event page:
 
Events cannot be assigned to a section/subsection so can only be targeted by content type.
 
Targeting key = type
Targeting value = event

 


 

Related
 

NOTE: GAM is a service of Google. Troubleshooting delivery problems with GAM ads is outside of the scope of our standard support service. You are welcome to submit GAM questions, but many will require specialized support and will therefore require a Metro Publisher Custom Services contract. More information here: Custom Support Services. 

Have more questions? Submit a request

Comments

  • Avatar
    Roanoker Magazine

    So, with the new ad slots, will all 6 of those appear across the entire site? Homepage and sections? And, will the homepage still have the left rail?

  • Avatar
    Roanoker Magazine

    And will the "wallpaper" ads appear on mobile, or no?

    mpu right will still appear on mobile, and all three leaderboards, if loaded with responsive sizes, will appear on mobile, right?

  • Avatar
    Metro Publisher Support Squad

    Q: So, with the new ad slots, will all 6 of those appear across the entire site? Homepage and sections?

    A: Yes, they will appear on all pages. And with custom tagging you will be able to target them individually.

    Q: And, will the homepage still have the left rail?

    A: Yes.

    Q: And will the "wallpaper" ads appear on mobile, or no?

    A: No. They will only appear on desktop when the screen width allows for the minimum width of the canvas plus the width of the ads themselves.

    Q: mpu right will still appear on mobile, and all three leaderboards, if loaded with responsive sizes, will appear on mobile, right?

    A: That's correct. The 970x90 version will only appear if there is one. If not, the display will default to 728x90. So, you are not required to use the new wider leaderboard size. But on screen sizes less than 728px, the ad will be switched for the default size of 300x50. If none has been inserted into the line item in DFP, the ad will not serve.

  • Avatar
    Thorsten Adler

    Problem: If you insert an leaderpoard 728x90 it wont show on a normal website! Only a 970x90 version show up.

  • Avatar
    Metro Publisher Support Squad

    Yes, your comment is correct. You must use creatives for all three widths (970, 728, 300).

    Originally our code was written to allow the behavior above based on Google's DFP spec. However that particular behavior was not clearly defined in the spec. The DFP JS picks randomly from whatever ad sizes appear at that screen size. As a result, that feature has been disabled until Google updates it's code.

  • Avatar
    Barbara Melnyk

    Since I have two websites, how do you add instance_id to DFP? In the Custom targeting it won't take instance_id as a value exceeds 10 characters. How will I tell which site I want a ROS ad to run on?

  • Avatar
    Metro Publisher Support Squad

    Hello,

    The key value is just "instance" and the tag would be your site name which is displayed in the top of those tags on the DFP edit page within Metro Publisher.

  • Avatar
    Daniel O'Connor

    We need help, we have changed everything over in DFP - however the new ad units from Metro arent the correct sizes? giving us 728 x 90 still?
    Also the MPU seems to have disappeared from our site? HELP?

  • Avatar
    Metro Publisher Support Squad

    Hello,

    The new ad slots have a different naming convention from the previous integration with DFP. You Need to upload the new slots to your DFP account and retarget your ads to those slots. If you are having trouble, we suggest you switch back the the old integration until you have been able to test that your ads are targeting the new ads slots correctly. If you haven't changed the old orders in DFP, then they will still work when you switch back.

Powered by Zendesk