In the ad tech industry, Google Ad Manager (GAM) is the premier ad server for publishers. However, the platform is divided into two primary tiers: the free version (often referred to as GAM Standard or GAM for Small Businesses) and the premium enterprise version, Google Ad Manager 360 (GAM 360).
Choosing between them depends not only on your monthly impression volume, but also on the structural complexity and feature requirements of your Ad Ops team.
Feature Comparison Matrix
| Feature | Google Ad Manager (Standard) | Google Ad Manager 360 |
|---|---|---|
| Pricing & Limits | Free up to 90M to 200M/month (based on region) for display. Strictly capped at 800,000/month for video. | Paid (Negotiated CPM contract or via an MCM partner). Unlimited scale. |
| Ad Unit Hierarchy | Max 1 level below root (2 levels total) | Max 2 levels below root (3 levels total) |
| Audience Targeting (Audience Solutions) | No native support (Custom key-values only) | Yes (1st & 3rd party segments, DMP, PPIDs) |
| Open Bidding (S2S Header Bidding) | No (Client-side Prebid.js required) | Yes (Server-to-server bidding inside Yield Groups) |
| Data Transfer (Raw Logs) | No (Aggregated UI or API reporting only) | Yes (Raw hour-by-hour logs exported to Google Cloud Storage) |
| Access Isolation (Teams) | Global user roles only | Yes (Restrict user access to specific objects and inventory) |
1. Impression Limits & Pricing
GAM Standard is free, but imposes strict thresholds. If you exceed these caps, Google reserves the right to suspend ad serving or require migration to a paid tier.
- GAM Standard (Free):
- 90 million monthly display impressions for US, Canada, Australia, and New Zealand.
- 200 million monthly display impressions for Europe (EEA, UK, Switzerland), Russia, and other countries.
- 150 million monthly display impressions for all other countries.
- A universal cap of 800,000 monthly video impressions globally.
- GAM 360 (Paid):
- No upper limits on volume.
- CPM-based billing model (the exact rate depends on display, video, or programmatic guaranteed agreements).
Publishers approaching these limits often leverage a Multiple Customer Management (MCM) partner. The certified partner extends its GAM 360 license to the publisher in exchange for a revenue share.
🔗 For details on setting up accounts and prerequisites: Get started with Ad Manager
2. Ad Unit Hierarchy Limits
Google Ad Manager's API enforces strict limits on nested inventories. Exceeding these nesting depth thresholds yields a developer error code: AdUnitError.Reason.INVALID_DEPTH.
- GAM Standard: Supports up to one level below the root ad unit (2 levels total: root and child).
- GAM 360: Supports up to two levels below the root ad unit (3 levels total: root, level 1, and level 2).
If you require deeper segmentation, you must flatten the naming structure (e.g. homepage_sidebar) or use targeting rules with custom Key-Values instead of creating extra physical ad units.
🔗 Read more about system thresholds and limits: Google Ad Manager system limits
3. Audience Solutions
While key-value targeting is powerful, cross-session and behavioral tracking require native audience management.
- GAM Standard: No native Audience Suite. Behavioral segmentation must be managed via manual tags or client-side custom key-values.
- GAM 360 (Audience Solutions): Enables creation of audience segments directly in the ad server. These can be populated using tracking pixels, site behavior, or Publisher Provided Identifiers (PPIDs). It also allows direct integration with third-party DMPs.
🔗 For audience configuration guidelines: Introduction to Audience Solutions
4. Open Bidding
Traditional client-side header bidding (Prebid.js) runs in the user's browser, adding script execution latency and slowing page loads.
- GAM Standard: Requires running header bidding entirely client-side. Bidders must be mapped manually or through API scripts via thousands of line item CPM slices.
- GAM 360 (Open Bidding): Enables S2S (Server-to-Server) real-time bidding in parallel with Ad Exchange via Yield Groups. Response latency drops, and Google aggregates the billing for all Open Bidding partners.
🔗 For server-to-server yield configuration details: About Open Bidding
5. Data Transfer Reports
When running advanced database analysis, raw event streams are needed.
- GAM Standard: Restricted to aggregated metrics inside the user interface or API reporting services.
- GAM 360 (Data Transfer): Exports hourly raw log files to Google Cloud Storage (in CSV or Parquet format). These files log every ad request, impression, click, and bid response down to the second.
🔗 For details on configuring Data Transfer and log files: Introduction to Data Transfer
6. Teams & Access Control
When multiple divisions or brands share a single GAM account, managing access and partitioning data is essential.
- GAM Standard: Roles apply globally. Any user with a "Trafficker" role can view and edit any campaign in the network.
- GAM 360 (Teams): Partition access by grouping users into Teams. You can assign specific ad units, companies, or orders to separate teams, ensuring "Brand A" Ad Ops cannot edit or view "Brand B" campaigns.
🔗 For configuring teams and object scopes: Configure teams in Google Ad Manager
Who is each version for?
Google Ad Manager Standard
Best suited for independent publishers, professional blogs, and mid-sized e-commerce sites.
- Volume below 90M - 200M display impressions/month.
- Small monetization teams (1-3 people).
- Standard aggregate reports are sufficient.
- Client-side Prebid.js header bidding is preferred.
Google Ad Manager 360
Essential for enterprise media groups, multi-site ad networks, and global publisher networks.
- Need for data-silos across sites or brands (Teams).
- Large scale programmatic sales (Programmatic Guaranteed).
- Massive ad request volume requiring server-side Open Bidding.
- Audience segmentation with PPIDs.
4 Concrete GAM 360 Use Cases
Case 1: Regional Ad Ops Isolation (Teams)
A global publisher operates separate sales arms in APAC and EMEA. By setting up APAC and EMEA **Teams** in GAM 360, APAC traffickers are restricted to their local APAC ad units and regional advertisers, preventing inadvertent edits to EMEA campaign setups while maintaining a single, unified corporate GAM network.
Case 2: Custom Billing Audits & Anti-Fraud (Data Transfer)
An ad network wants to double check billing data against downstream logs and detect ad fraud. By enabling **Data Transfer**, they receive hourly raw event records in Google Cloud Storage. They load these logs into BigQuery, where they run custom anti-fraud algorithms and match impressions down to the second.
Case 3: Reducing Page Load Latency with Open Bidding
A high-traffic news portal wants to increase auction pressure. Client-side header bidding with many partners slows the site. By migrating several SSPs to **Open Bidding**, auctions happen server-side inside Google. Page performance improves, Core Web Vitals stay green, and CPM rates increase.
Case 4: Target Premium Behavioral Segments (PPID)
A classifieds app creates segments for users searching for "used cars." Using **Audience Solutions**, these segments are populated via PPIDs of signed-in users. When a car advertiser buys programmatic slots, the publisher targets this specific audience segment, capturing a 3x higher CPM rate compared to run-of-site placements.