Consumer brands: build a brand commerce media network
A consumer brand's audience and first-party data become a commerce media network: shoppable placements onsite, reach offsite, closed-loop attribution, and an ID graph that makes every impression smarter.
Your five steps
| Step | What you do | Your choices |
|---|---|---|
| 1 Add Brand Elements | Account, brand kit, verify domains and apps, connect the product catalog and your creator content folders (see Create your Business Account on Brand Control Center (BCC), Set your brand identity: name, logo, colors, and voice, and Connect your website, app, and podcast feed). Invite Marketing, Revenue, and Developer roles (see Invite your team and assign roles). | Voice per product line |
| 2 Launch Media Network | Model: Commerce Media (see Choose your network model: Owned, Extended, Commerce, or Retail). Grid mirrors your site: Home, Category, PDP, Post-purchase (see Register your placements on the Hierarchical Grid). Shoppable on PDPs and categories, Community post-purchase (see Pick your first player experience). | Live & Q&A for drops |
| 3 Publish Communities | Groups by product category and by use occasion. Studio generates product videos from the catalog and clips from creator content (see Upload your videos or connect your social profile and Launch your first community: your owned-and-operated space). Launch (see Launch your first community: your owned-and-operated space); post to the hub first and syndicate (see Post to your hub, then curate and schedule to other platforms); distribute product-category feeds with sponsorships wrapped (see Distribute your feeds across 7K+ apps and sites). | Canvas Growth fleet on trends in your categories |
| 4 Add Users | Auto login with email_hash for the ID graph (see Bring your audience in with auto login and SSO). Invite ambassadors and loyal customers; run a Quest (see Invite creators, hosts, and contributors). Brand safety profile with competitive exclusions (see Set moderation, roles, and brand safety). Invite retail partners for Paid Partner Posts in their category groups (see Add brand partners and demand partners). | Audience extension through Genuin Ad Server |
| 5 Sign Contract | Enterprise plan, commerce media schedule with data-use terms (see Plans explained: Free, Self-serve, and Enterprise and Choose your monetization agreement). E-sign, sellers, blocklists (see Sign your agreement and authorize sellers). Switch on commerce (in-video linkouts to your checkout), partners, programmatic (see Activate monetization and see your first revenue). | Octo routing for intent your catalog cannot serve |
Done in 30 days
Shoppable placements on every PDP with attributed revenue in Reports → Attribution, segments built from onsite and purchase data, and the first Paid Partner package sold to a retail partner with a net margin on ad spend forecast.
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 /accounts | Create a Business Account (company, first brand, company type, owner email); returns the verification link and a sandbox key |
| POST /brands/{brandId}/kit:sample | Sample the kit from a URL (homepage, app listing) and return it rendered for review |
| POST /brands/{brandId}/studio/jobs | Studio job: catalog product videos, text-to-video explainers, adaptation per platform, live-to-clips |
| POST /brands/{brandId}/partners:invite | Invite a partner with direction, permissions, groups, and split or price |
| POST /brands/{brandId}/tags | Generate an offsite tag: VAST, JavaScript display, dynamic feed, audience extension |
| POST /accounts/{accountId}/agreements | Draft the agreement for the model (revenue share, platform, managed, commerce, buyer) |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.accounts.create({ company, brand, companyType, ownerEmail });
await genuin.brands.kit.sample(brandId, { url });
await genuin.studio.jobs.create(brandId, { kind: 'catalog', skus });Live today: Generate an access token · Environments, credentials, and test data · Create a community · Create a group in 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.
