Glossary
Fixed terms used across every article; each term is the link target for its first use in any article.
| Term | Definition |
|---|---|
| Brand Control Center (BCC) | The centralized hub for your brand on Genuin: the dashboard where a Business Account runs each of its brands (identity, grid, communities, partners, monetization, reports), with a brand switcher to move between brands |
| Business Account | The container for a company on Genuin: brands, team, billing, and agreements; one Business Account holds many brands |
| Brand switcher | The control in the BCC header that changes which brand every screen, setting, and report refers to |
| Brand Context | What you give Octo to work from: the website crawler, brand guidelines, audience notes, catalog, partner rules, policies, technical notes, and legal paper under Brand → Context |
| Website crawler | Octo's reader of your properties: it extracts brand kit, page types, categories, content sources, sign-in, and partners, and keeps them current on a schedule |
| Octo autonomy | The level each kind of change runs at (ask every time, do and report, off) and the standing rules your approvals become |
| Octo-enabled support | 24/7 support where Octo answers or acts first and brings the right account manager, developer, or Ops engineer into the thread when a person is needed |
| Media Supply Aggregator | A company that represents many publishers, apps, or sites and brings their inventory to Genuin as one supply network: one Business Account, one brand per property, one grid, per-publisher splits |
| Media Demand Aggregator | A company that holds many advertisers' budgets (a DSP, ad network, or trading desk) and buys across the Genuin network: one Business Account, one client brand per advertiser, buyer agreement, per-client attribution and margin |
| Media network | A brand's own distribution and monetization system on Genuin: inventory, communities, and demand |
| Network model | Owned, Extended O&O, Commerce Media, or Retail Media; sets which capabilities are on |
| Hierarchical Grid | The single tree Network → Property → Page type → Placement that inventory, layout, and reporting share |
| Placement | A named slot on the grid with a size, allowed experiences, context, floor, and brand safety profile |
| Context | Topics, categories, or product taxonomy attached to a page type or passed by the embed |
| Player experience | Shorts, Shoppable, Community, or Live & Q&A |
| Brand community | The home of one brand's content, members, and rules |
| Group | A topic feed inside a community, matched to placement context |
| Quest | A brief with a deadline and a reward that invites creators or members to post |
| Creator Wallet | The account where a creator's shares, rewards, and tips settle |
| Maya | Genuin's relevance engine; measured on per-minute watch time per user and per-minute revenue |
| Studio | Production: turns sources into brand-ready vertical video |
| Canvas | Agentic operations: Growth and Monetization fleets that run a network on a cadence |
| Octo | The orchestration and generative commerce layer: Ask, Act, Resolve |
| Relevance OS | The four-tier analytics layer: relevance, engagement, revenue, adaptation |
| Intelligence SDK | Typed access to Genuin signals for your own stack |
| Onsite | Video on your own properties |
| Offsite | Your video as IAB-standard tags on other inventory |
| Network distribution | Your content in partner placements on Genuin |
| Extended O&O | Your brand run as a destination on partner inventory, operated by Genuin as a managed service |
| Paid Partner Post | A partner's video placed in your group with disclosure and pacing |
| Paid Partner Takeover | A partner's content filling a placement, page type, or group for a window |
| Package | A sellable bundle of inventory and outcomes |
| Marketplace | Where packages are listed, bought, delivered, and billed |
| AdCP | Ad Context Protocol; lets AI buyer agents discover and buy packages |
| Genuin Ad Server | Genuin's programmatic ad server, connected to exchanges |
| Partner ad server | Your own ad server as the system of record, receiving Genuin inventory as line items |
| ads.txt / sellers.json | The files that authorize sellers of your inventory |
| Brand safety profile | GARM-aligned description of inventory attached to every placement |
| Auto login | Token exchange that signs your users in to Genuin |
| ID graph | Matching of hashed identifiers across onsite, offsite, and offline under your agreement |
| Segment | A cohort built from onsite, offsite, and offline signals |
| Attribution | Linking exposures to outcomes under a chosen model |
| Net margin on ad spend | Gross margin on attributed sales minus spend, divided by spend |
| Revenue per impression | All attributed revenue divided by impressions |
| Two-channel data flow | Viewing history and identity kept apart and joined only under agreement and consent |
| API key / signing key | Credentials for the API and for auto login tokens |
| Webhook | Signed HTTP callback for network events |
| Brand network | The brands connected to yours through content, inventory, audience, data, and demand; a graph with your brand as the anchor |
| Anchor brand | The brand that owns a network: its grid, communities, agreement, and reports |
| Node / edge | A brand in the network (its community) and a typed relationship between two brands (distribution, content acceptance, paid partnership, audience extension, destination hosting, reselling) |
| Endemic / non-endemic | A partner that sells what your audience comes to you for, versus one that wants your audience but sells something else |
| Brand classification | The five axes every partner is tagged on: assets, role, market relationship, company type, scale and model |
How it runs
None of this has to be implemented by hand: the snippets, keys, tags, and calls are generated for your stack and opened as changes in your repository or CMS where connected, for your Developer to 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 |
|---|---|
| GET /glossary | Glossary terms as JSON (also served as llms.txt) |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.glossary();Live today: Embed the Genuin Web SDK on your website · Integrate the Genuin iOS SDK · 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.
