Paid Partner Posts and Paid Partner Takeovers
A Paid Partner Post is a brand's video placed in one of your groups and ranked by Maya with the disclosure and pacing you set; a Paid Partner Takeover gives a brand an entire placement or group for a period. Reading time about 6 minutes.
Paid Partner Post
- The partner supplies the video (or Studio produces it from their brief) and it enters the named group with a "Paid partnership" label.
- Maya ranks it like any other post within the pacing you set (Personalization and relevance: how Maya ranks every feed: maximum share of paid posts per session).
- Priced per thousand views, per post, or as part of a package; the partner sees views, watch time, engagement, and, when commerce is connected, attributed revenue.
- FTC and local disclosure fields are required on the post object and cannot be removed by the partner.
Paid Partner Takeover
- The partner's content fills a placement, page type, or group for a fixed window (a launch day, a weekend, a season).
- Your brand kit stays; the partner's brand appears on content and an optional banner.
- Priced per window; Takeovers can be bundled with Posts and offsite tags (see Offsite: generate IAB-standard tags for your media plan) into a package.
Selling them
- In BCC open Monetize → Packages and choose Create package: name, inventory (groups and placements), window, and the outcome block you forecast (projected views, engagement, attributed commerce).
- Choose Sell directly (send a proposal link to the partner, who accepts in their BCC) or List (Marketplace and AdCP, Marketplace: list packages and transact with demand partners and AdCP: make your inventory discoverable to AI buyer agents).
- Approve the creative under Monetize → Approvals, or let Canvas approve within your guardrails (see Canvas: run your network with growth and monetization agents).
Reporting
Each package reports delivered views, engagement, attributed commerce, and net margin against the forecast, so renewals are based on outcomes.
How it runs
The demand setup, packages, agreements, and seller files described here are drafted for you, priced against your floors and brand safety profile, and switched on only with your approval; money never moves on a change you did not approve.
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}/sponsorships | Paid Partner Post or Takeover: offer, budget, CPM, dates, placements |
| POST /brands/{brandId}/packages | Build a package from placements, feeds, and capabilities with a forecast |
| GET /reports/revenue | Revenue by placement, partner, source, tier; payouts and creator shares |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.sponsorships.create(brandId, { partnerId, kind: 'takeover', budget });
await genuin.packages.create(brandId, { placements, feeds, price });
await genuin.reports.revenue({ brandId, by: 'source' });Live today: Serve your first ad · 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.
