Network distribution: place your content in partner inventory
Network distribution puts your video into placements owned by other networks on Genuin, so your reach grows without buying media, and partners' feeds gain content their audience wants. Reading time about 5 minutes.
How it works
- In BCC open Network → Distribution and choose List network. Your groups, brand safety profile, and content policy become visible in the Genuin network directory.
- Choose which groups are distributable and whether partners may re-cut your content to their brand kit through Studio's Adaptation (see Studio: produce brand video from podcasts, long-form, and catalogs).
- Request access to specific partner placements, or let Maya place your content wherever a partner has accepted your network and the context matches.
- Approve or decline incoming requests from partners who want your content (Accept partner content into your ecosystem is the mirror of this article).
Economics
Distributed views count toward your revenue share (see Choose your monetization agreement); when a partner monetizes a view of your content, the split is set by the agreement both sides accepted when the partnership was created (see Add brand partners and demand partners).
Controls
Distribution respects your brand safety profile and the partner's; a view happens only where both allow it. You can pause distribution per partner or per group at any time, and content you remove is removed from partner feeds within minutes.
Reading the report
Reports → Network shows views, watch time, and revenue by partner and placement, and which groups travel best, which feeds back into what Studio and Canvas produce.
How it runs
The placements, feeds, destinations, and identity settings described here are proposed from your grid and audience, applied on confirmation, and tuned on a cadence from the reports.
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 /feeds/{feedId}:distribute | Approve where a feed may run and what wraps it; starts distribution |
| GET /network/directory | The network directory: brands, properties, and placements open to partners |
| PUT /brands/{brandId}/network/listing | How your network appears in the directory |
| GET /reports/distribution | Syndication and network distribution by platform, partner, feed |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.feeds.distribute(feedId, { scope: 'network', wrap: ['genuin-ads'] });
await genuin.network.directory({ category });
await genuin.network.listing.update(brandId, { … });Live today: Deliver contextual feeds with page, user, and location context · Embed the Genuin Web SDK on your website · Receive engagement events in your own analytics · Query Genuin event data in BigQuery.
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.
