Media demand aggregators: route your advertisers' demand into the Genuin network
An aggregator that holds advertiser budgets (a DSP, an ad network, an agency trading desk, an affiliate or retail-media demand platform) runs each advertiser as a client brand under one Business Account and buys across the Genuin network, directly through Marketplace packages and Paid Partner Posts, programmatically through its own DSP, and through AdCP buyer agents, with attribution and net margin reported per client.
Your five steps
| Step | What you do | Your choices |
|---|---|---|
| 1 Add Brand Elements | One Business Account; your anchor brand plus one brand per advertiser, created from CSV or the Partner API (see Create your Business Account on Brand Control Center (BCC) and REST API: authentication and keys). Campaign Manager and Analyst roles scoped per client brand; Account Admin and Finance across all (see Invite your team and assign roles). | Verify a client's domains only where you will run onsite placements for them (see Connect your website, app, and podcast feed) |
| 2 Launch Media Network | You buy rather than own inventory: map the network to your taxonomy in Marketplace → Discover (see Marketplace Listing and Discovery). Register client properties on the grid only for clients with their own sites (see Register your placements on the Hierarchical Grid). Choose the player experience your creative is produced for (see Pick your first player experience). | AdCP discovery so buyer agents can see packages (see AdCP Discovery and Network Sales Agent) |
| 3 Publish Communities | Upload advertiser creative and licensed creator content per client brand; the AI classifies it (see Upload your videos or connect your social profile). A lightweight hub per client as creative library and landing page (see Launch your first community: your owned-and-operated space). Studio adapts every asset to placement size and partner brand kit (see Post to your hub, then curate and schedule to other platforms). Buy distribution: Paid Partner Posts, Takeovers, and sponsored network feeds (see Distribute your feeds across 7K+ apps and sites and Paid Partner Posts and Paid Partner Takeovers). | Creator content as ad creative for offsite (see Creator Content as Ad Creative) |
| 4 Add Users | Client marketing teams into their brands (see Invite creators, hosts, and contributors). Publishers you want direct deals with as Demand-side edges from your anchor brand (see Add brand partners and demand partners and Brand Network: core concepts and how brands are classified). DSP or ad server connected for programmatic (see Programmatic: Genuin Ad Server or your partner ad server). Auto login only for clients running onsite (see Bring your audience in with auto login and SSO). | Audience extension from a client's first-party segments (see Audience Extension Tag and Audience segments: onsite, offsite, and offline signals) |
| 5 Sign Contract | Buyer agreement with a platform fee on demand you bring (see Choose your monetization agreement); billing profile and insertion orders per client brand. Check the publishers you buy from list Genuin in ads.txt (see Sign your agreement and authorize sellers). Activate the first package and read delivery, attributed outcomes, and net margin on ad spend per client (see Activate monetization and see your first revenue and Margin reporting: revenue per impression and net margin on ad spend). | Outcome Forecast Blocks on every package before you commit (see Outcome Forecast Blocks) |
Done in 30 days
Every advertiser as a switchable client brand, the first packages and Paid Partner Posts delivered across endemic groups in the network, programmatic running through your DSP with Genuin as a seller, and one attribution and margin report per client that you can renew against (see Attribution: closed-loop commerce and conversion forecasts and Margin reporting: revenue per impression and net margin on ad spend).
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 /oauth/token | Exchange client credentials for an access token scoped to a Business Account |
| POST /accounts/{accountId}/brands:import | Bulk-create brands from a CSV or a list (aggregators: one per property or client) |
| GET /marketplace/listings | Buyer side: search listings by vertical, persona, journey, placement style |
| POST /media-buys | Buyer side: buy a package or a Paid Partner Post |
| GET /adcp/products | AdCP get_products for AI buyer agents |
| GET /reports/attribution | Closed-loop commerce, conversion forecasts, offsite attribution |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.auth.token({ clientId, clientSecret, accountId, scope });
await genuin.brands.import(accountId, { rows });
await genuin.marketplace.search({ vertical: 'auto' });Live today: Generate an access token · Environments, credentials, and test data · Serve your first ad · Receive engagement events in your own analytics.
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.
