What is Google Ad Manager (GAM)?
Google Ad Manager (GAM) is Google's ad management platform for publishers, used to serve and manage ads across websites, apps, video and games, combining direct-sold campaigns with demand from Google and third-party exchanges and networks.
Also known as: GAM, Ad Manager
How it works
What does Google Ad Manager do?
Google's help centre describes Ad Manager as an ad management platform for large publishers who have significant direct sales, and lists support for AdSense, Ad Exchange and third-party networks and exchanges. It also positions Ad Manager as one place to monetize websites, mobile apps, videos and games, with detailed reporting across them (Google Ad Manager Help).
In everyday terms, GAM is the publisher's ad server: the system that makes the final call on which ad appears in each slot. When a page or app requests an ad, GAM looks at everything eligible for that impression, from a sponsorship sold months ago to programmatic bids arriving in real time, and picks the winner according to the publisher's rules.
How does GAM decide which ad to show?
Publishers set up their sales inside GAM as line items. A line item holds the terms of a campaign or demand source: the ad units it can run on, the targeting, the dates, the price and a priority. Guaranteed campaigns typically sit at a higher priority than open auction demand, so GAM protects what has been sold directly while letting programmatic demand fill the rest.
Header bidding fits into this through line items and key-values. A wrapper such as Prebid collects bids before GAM is called, then passes them in as key-values (labels such as a price bucket). GAM matches those labels to line items set up for the purpose and weighs them against everything else. Prebid's documentation warns that if the line items are misconfigured, winning header bids can be excluded from the final decision (Prebid).
Google also offers its own server-to-server option. With Open Bidding, third-party exchanges bid through Ad Manager directly, and Ad Manager handles trafficking, reporting and billing for them (Google Ad Manager Help).
Why it matters
Because GAM makes the final decision, how it is configured shapes revenue as much as which partners a publisher works with. Priorities, floors, line item setup and the balance between direct, private deal and open auction demand all play out inside the ad server. Small configuration errors, like a missing price bucket or an outdated floor, can quietly cost money for months.
Example
Example (illustrative)
A regional sports publisher sells a homepage sponsorship for a cup final weekend and books it in GAM at a high priority. During the same weekend, its Prebid wrapper sends bids for article pages into GAM through key-values, and Open Bidding partners compete server-to-server. GAM serves the sponsorship wherever it is due and lets the best of the programmatic bids fill every other impression.
IncrementX perspective
An ad server carries out decisions; it does not make the commercial ones. Which buyers to bring in, what to sell directly, and when a private deal beats the open auction are representation questions. IncrementX helps publishers with those questions through media representation, and its header bidding support covers wrapper setup support, demand partner integration and performance optimization, work that has to line up with how a publisher's ad server is configured.