Partner Ad Server Integration
Your own ad server stays the system of record and receives Genuin inventory as line items. Google Ad Manager (GAM) connects directly, and other ad servers, such as FreeWheel or Beeswax, connect through a VAST or VMAP link.
Partner ad server integration keeps your direct deals, priorities, and reporting where they already live. Your Genuin placements become ad units or line items in your ad server. Genuin network demand then fills what your server passes back.
Octo, Genuin's Supervised Intelligence interface in your Business Account, proposes this capability when it finds a fit on your sites and apps. It completes the steps under Set it up from your brand context. Nothing goes live until you approve it. It's part of Monetize, and Programmatic: Genuin Ad Server or your partner ad server compares it with Genuin Ad Server.
When to use it
Use it if you're a publisher or retailer whose direct deals and priorities already sit in an ad server. Your ad server stays the system of record, and Genuin inventory joins it.
Setup takes three to ten business days, compared with the same day for Genuin Ad Server. If you have no ad server or no ad ops team, Genuin Ad Server is the faster path.
How it works
- The placement CSV from your grid maps one to one to ad units or line items. The Hierarchical Grid generates it from Network > Grid > Import/Export.
- You create the ad units in your ad server, then connect it in Demand Settings. You select it in the preset that covers those placements and embeds.
- You set priorities in your ad server as usual. Genuin network demand fills what your server passes back.
- Floors live in your ad server, and Business Account mirrors them.
- Blocklists apply before any ad renders. Business Account shows the list to hand to your ad ops, or your Genuin CSM applies it on a managed plan.
- Viewability, your brand safety profile, and context pass in bid requests through standard IAB fields. Ad tag reference: VAST, IAB sizes, and macros lists them.
Set it up
Octo proposes the integration with these steps already done. You review the result and confirm it.
- Export the grid CSV, then create ad units and line items in your ad server. Learn how in The Hierarchical Grid.
- Under Settings > Ad Configuration, open Demand Settings and add your Google Ad Manager account. Then select it in the preset for those placements and embeds. Learn how in Programmatic: Genuin Ad Server or your partner ad server.
- Add your ad server's seller lines to ads.txt. Genuin's lines and your platform's lines must both be present. Learn how in Set up ads.txt and sellers.json.
Settings
| Setting | Where it lives |
|---|---|
| Priorities | Set in your ad server |
| Floors | Set in your ad server; Business Account mirrors them |
| Blocklists | Kept in your Business Account and handed to your ad ops |
Change priorities and floors in your ad server as you do today. Edit blocklists in your Business Account with Blocklists and Ad Quality, then pass the updated list to your ad ops.
Ad servers in Demand Settings
In your Business Account, you add your own ad server accounts under Settings > Ad Configuration, in the Demand Settings drawer. You can add several Google Ad Manager (GAM) and Pangle accounts.
Google Ad Manager connects in one of two ways:
- Connect Your Account: sign in with Google, then select at least one ad unit from the list. Connected ad units are listed with their traffic rate.
- Manual: enter an account name, up to 100 characters, and a valid VAST or VMAP link.
Editing a connected account reopens the ad unit list, where you can add or remove units. You can't change an existing unit's name, network code, or ID.
If you disconnect the Google account, the ad units you already added stay listed.
Pangle takes an account name, a numeric App ID, and up to 5 slot rows. Each row pairs a numeric Slot ID with one ad format: interstitial, native, rewarded, banner_320x50, or banner_320x250. Each format can be used once per account.
Each GAM and Pangle server has its own traffic rate. It's required and can't exceed 100%.
Each preset lists the ad servers from Demand Settings, and the default ad server is preselected on new presets. To make your ad server the default, hover over it, click Set as default, and confirm. Existing presets keep their current ad server.
You can't delete an ad server while a preset uses it, or while it's the default. Remove it from the preset, or set another default, first.
What it reports
Your ad server's reporting stays the system of record. Business Account adds reconciliation along the grid. Revenue reporting, payouts, and the Wallet explains how revenue is reconciled and paid.
- Ad server reporting: delivery and revenue in your ad server's own reports.
- Business Account reconciliation: Genuin revenue by network, property, page type, and placement in Reports > Revenue.
A platform agreement fits this model. It covers a platform fee on revenue from your own partners and a revenue share on Genuin network demand for the remainder.
Connect your systems
Line items and tags live in your ad server and Business Account, and ads are configured there, not in code. Go live with monetization in your feeds, apps, and partner pages covers ads inside your embeds and IAB units rendered from a tag in your app.
The ad server connection calls in the Business Account API are proposed, not live. Live API today and the Business Account API roadmap maps what you can call now to what's planned.
