Marketplace: list packages and transact with demand partners
Marketplace is where your packages (Paid Partner Posts, Takeovers, offsite tags, audience extension, Extended O&O destinations) are listed for buyers to discover and purchase, with contracts, creative approval, delivery, and billing handled in BCC. Reading time about 5 minutes.
Listing a package
- Create the package under Monetize → Packages (see Paid Partner Posts and Paid Partner Takeovers).
- Choose List in Marketplace. Add the outcome block: projected views, engagement, attributed commerce forecast, and net margin on ad spend where you have the data (see Attribution: closed-loop commerce and conversion forecasts and Margin reporting: revenue per impression and net margin on ad spend). Packages with outcome blocks are ranked higher for buyers.
- Set price (fixed, CPM, or request-a-quote), availability windows, and the brand safety profile buyers must accept.
- Publish. The listing appears to buyers in Marketplace and, if enabled, to AI buyer agents over AdCP (see AdCP: make your inventory discoverable to AI buyer agents).
Buying
A buyer (a brand partner, an agency, or another network) requests, you approve, creative goes through approvals, delivery runs, and the invoice and payout settle under your agreement (see Plans, billing, and invoices and Revenue reporting, payouts, and the Creator Wallet). Buyers never need to leave their BCC.
Capabilities buyers see
Each listing shows which network capabilities back it: Paid Partner Exchange, Affiliate and Commerce Link-Out, Retargeting Activation with the buyer's audiences, AgenticStudio production, Extended O&O syndication. Capabilities are switched on by your model and agreement.
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}/packages | Build a package from placements, feeds, and capabilities with a forecast |
| POST /packages/{packageId}/listings | List a package on the Marketplace (and AdCP) |
| GET /packages/{packageId}/forecast | Outcome forecast block: reach, eCPM lift, revenue range |
| POST /media-buys | Buyer side: buy a package or a Paid Partner Post |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.packages.create(brandId, { placements, feeds, price });
await genuin.listings.create(packageId);
await genuin.packages.forecast(packageId);Live today: Serve your first ad.
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.
