Accept partner content into your ecosystem
Accepting partner content lets brands and networks you trust place their video into named groups on your properties under your rules, which fills your feeds and is the inbound half of every brand partnership. Reading time about 4 minutes.
Steps
- In BCC open Network → Requests. Each request shows the partner, their brand safety profile, the groups they want, and a sample of their content.
- Accept with conditions: which groups, whether their content may be re-cut, whether it can carry Paid Partner Posts, and the share on any revenue it earns on your placements.
- Partners appear under Network → Partners with a toggle to pause them.
What partner content can and cannot do
| Can | Cannot |
|---|---|
| Appear in the groups you named | Appear elsewhere, even if the context matches |
| Carry the partner's brand on the post | Change your brand kit on the placement |
| Be ranked by Maya like your own content | Bypass your moderation or brand safety profile |
| Earn the partner a revenue share you set | Collect viewer data from your properties |
Why accept content
A library of 30 videos becomes a library of hundreds the day you accept two partners, and Maya has more to rank. For retailers, endemic brands' content in category groups is also the simplest Paid Partner Post inventory (see Paid Partner Posts and Paid Partner Takeovers).
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 /brands/{brandId}/acceptances | Accept partner content into your placements under your rules |
| POST /partner-requests/{requestId}:decide | Accept or decline an incoming partner request |
| PUT /brands/{brandId}/brand-safety | GARM-aligned brand safety profile and competitive exclusions |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.acceptances.create(brandId, { partnerId, placements });
await genuin.partners.decide(requestId, 'accept');
await genuin.brandSafety.update(brandId, profile);Live today: Deliver contextual feeds with page, user, and location context · Embed the Genuin Web SDK on your website · Serve your first ad · Add moderators to 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.
