Google Ad Manager integration in Fusion
Google Ad Manager (GAM) is the ad server that hosts the final auction and where direct campaigns are trafficked. Every Fusion account can use Content Ignite's built-in GAM, or connect its own GAM to use Fusion on a SaaS basis.
What Google Ad Manager does in Fusion
Once your GAM is connected, Fusion checks on every change you make that the ad units its tag needs are present and correct, so ads always have a unit to serve from.
Good to know
- Every account can use Content Ignite's built-in Google Ad Manager account, preloaded with demand partners and run by our ad operations team.
- Connect your own GAM with Reporting & Management (Fusion creates ad units, handles MCM and site approval, and imports your reporting each morning) or Limited (Fusion only creates and syncs the ad units it needs).
- Fusion creates a child ad unit for each tag config, named like ci-cid-1234, under a parent unit for the site.
- Fusion doesn't change your ad serving: you target line items to its units however you like.
- IAB contextual categories are pushed into GAM as publisher provided signals when contextual is on.
Use GAM as your central ad server supplying demand via programmatic or direct bookings. In addition, handle MCM flow and site approval along with centralised reporting.
Google Ad Manager in Fusion: questions, answered
Do I need my own Google Ad Manager account to use Fusion?
Why does Fusion ask for full access to my Google Ad Manager?
What is the difference between Reporting & Management and Limited?
How do Prebid bids reach my Google Ad Manager?
What do I lose if I set up GAM ad units by hand?
More Ad Servers integrations in Fusion
Want a second opinion on your ad stack?
Get a free Revenue Healthcheck: your ad set-up, header bidding and Core Web Vitals scored and benchmarked against similar publishers.