Publishers and media companies: launch a publisher media network
A publisher's brands become destinations across owned domains and Extended O&O inventory, operated by Genuin as a managed service, sold to brand partners directly and programmatically, with outcome-based packages.
Your five steps
| Step | What you do | Your choices |
|---|---|---|
| 1 Add Brand Elements | One Business Account, one brand per title with its own community, roles scoped per brand (see Create your Business Account on Brand Control Center (BCC), Set your brand identity: name, logo, colors, and voice, Connect your website, app, and podcast feed, and Invite your team and assign roles). Connect every domain and app. | A brand kit per brand |
| 2 Launch Media Network | Model: Extended O&O (see Choose your network model: Owned, Extended, Commerce, or Retail). Import the grid from your ad server's ad units (see Register your placements on the Hierarchical Grid and The Hierarchical Grid: one spine for inventory, layout, and reporting). Shorts on article pages, Live & Q&A for events (see Pick your first player experience). | Named launch destinations in your agreement |
| 3 Publish Communities | Groups mirror sections. Studio runs production lines per brand; Canvas on daily cadence (see Upload your videos or connect your social profile and Launch your first community: your owned-and-operated space). Launch (see Launch your first community: your owned-and-operated space) and embed feeds through your CMS; syndicate from the hub (see Post to your hub, then curate and schedule to other platforms); distribute section feeds by category and topic across the network (see Distribute your feeds across 7K+ apps and sites). | Adaptation for partner destinations |
| 4 Add Users | SSO for subscribers (see Bring your audience in with auto login and SSO). Hosts for talent (see Invite creators, hosts, and contributors). Strict moderation and a brand safety profile per brand (see Set moderation, roles, and brand safety). Invite endemic and non-endemic brand partners; connect your ad server (see Add brand partners and demand partners). | Accept partner content for section groups |
| 5 Sign Contract | Enterprise plan, managed service agreement (see Plans explained: Free, Self-serve, and Enterprise and Choose your monetization agreement). E-sign, ads.txt for every domain, blocklists (see Sign your agreement and authorize sellers). Switch on all sources; list Paid Partner packages in Marketplace and AdCP (see Activate monetization and see your first revenue). | Partner ad server as system of record |
Done in 30 days
First Extended O&O destination live, Paid Partner Post packages sold with outcome blocks, programmatic filling along the grid, and Reports → Revenue reconciled against the agreement.
How it runs
This playbook runs as a sequence of proposals, one per step, ordered for your company type; you confirm each one and the 30-day outcome is reported against the plan.
Support. Help is available 24/7 from Brand Control Center and from every page of these docs. Ask in plain language; when a person is needed, an account manager, developer, or Ops engineer joins the same thread and stays on it until it is resolved. Every Business Account owner has this on every plan (see 24/7 Octo-enabled support: how Octo brings in account managers, developers, and Ops).
API & SDK
Access: the calls in the table are the proposed Business Account API (see Business Account API: provisioning, OAuth, and the resource map), authenticated with a key scoped to the account and a role or an OAuth client acting for it; every confirmation in this article becomes a proposal you can approve by API (POST /proposals/{proposalId}:approve). Live today, the server API under /api/thirdparty authenticates with a gn-access-token (see Generate an access token), and Live API today and the Business Account API roadmap maps what is live to what is proposed.
| Call | Purpose |
|---|---|
| POST /accounts/{accountId}/brands:import | Bulk-create brands from a CSV or a list (aggregators: one per property or client) |
| POST /brands/{brandId}/placements:import | Import the grid from an ad server's ad units or an inventory map |
| POST /brands/{brandId}/videos:import | Import videos from a source, URL list, or upload session |
| POST /brands/{brandId}/destinations | Create an Extended O&O or Generative Destination on a Genuin domain |
| PUT /brands/{brandId}/ad-server | Genuin Ad Server or partner ad server connection, floors, and yield rules |
| POST /demand-sources/{sourceId}:activate | Switch a demand source on (or off) in order |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.brands.import(accountId, { rows });
await genuin.placements.import(brandId, { source: 'gam', rows });
await genuin.videos.import(brandId, { sourceId });Live today: Environments, credentials, and test data · Add a Genuin placement to your website · Embed the Genuin Web SDK on your website · Create a community.
SDKs: Web SDK 2.0.6 (see Embed the Genuin Web SDK on your website), iOS SDK 2.1.5 (see Integrate the Genuin iOS SDK), Android SDK 2.1.5 (see Integrate the Genuin Android SDK), React Native 3.0.3 (see Integrate the Genuin SDK with React Native apps), and Flutter (see Integrate the Genuin SDK with Flutter apps) render Genuin and sign members in; the Node (@genuin/sdk) and Python (genuin) server SDKs are proposed with Business Account API: provisioning, OAuth, and the resource map.
