Partner Ad Server Integration
Your own ad server (GAM, FreeWheel, Beeswax, others) stays the system of record and receives Genuin inventory as line items. Genuin configures your tags inside Genuin Ad Server for specific placements.
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 demand then fills what your server passes back.
This capability arrives as a proposal when your network needs it, filled in from your brand context, and goes live when you confirm 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 and paste their tags into BCC per placement. Genuin ad operations configures them inside Genuin Ad Server for those placements.
- You set priorities in your ad server as usual. Genuin demand fills what your server passes back.
- Floors live in your ad server, and BCC mirrors them.
- Blocklists apply before any ad renders. BCC 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.
- Choose Partner ad server, pick your platform, and paste your ad server's tags into BCC per placement. 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; BCC mirrors them |
| Blocklists | Kept in BCC and handed to your ad ops |
Change priorities and floors in your ad server as you do today. Edit blocklists in BCC with Blocklists and Ad Quality, then pass the updated list to your ad ops.
What it reports
Your ad server's reporting stays the system of record. BCC adds reconciliation along the grid. Revenue reporting, payouts, and the Creator Wallet explains how revenue is reconciled and paid.
- Ad server reporting: delivery and revenue in your ad server's own reports.
- BCC 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 partner-sold revenue and a revenue share on the Genuin-sold remainder.
Connect your systems
Line items and tags live in your ad server and Brand Control Center, and ads are configured there, not in code. Serve your first ad 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.
