Octo: what it does and where to start
Octo is the AI layer. It answers questions about your data, acts across products, and resolves commerce intent in the player. Relevance OS and the Intelligence SDK are how its signals reach you.
Octo operates your Brand Control Center with you. It reads your brand context, proposes each change, and carries it out once you approve. Each kind of change runs at the autonomy level you choose, and every action is logged with the approval that allowed it. Octo operates your Brand Control Center explains the model.
Each capability below arrives as a proposal when your network needs it, filled in from your brand context, and goes live when you confirm it. Read Octo: the orchestration and generative commerce layer first for the full picture.
Get started
- Give Octo your brand context. Point the crawler at your properties and add guidelines, catalog, and policies.
- Set Octo's autonomy and approvals. Choose which changes Octo asks about every time, and which it does and reports.
- Read the Relevance OS dashboard. See relevance, engagement, revenue, and adaptation along your grid.
Ask, act, and resolve
| Capability | What it does | Where it fits |
|---|---|---|
| Octo Ask | Answers questions from your reports, with the chart and rows behind the answer | Any BCC user |
| Octo Act | Turns instructions into drafted actions across products, run on your approval | Any BCC user with the role for that action |
| Octo Resolve | Turns a tagged moment or a viewer's question into a commerce outcome at serve time | Commerce and retail models |
| Generative Commerce Routing | Routes intent your catalog can't serve to retail assistants and marketplaces | Brands whose products sell elsewhere |
| Generative Player for LLM Applications | Renders your video and products inside AI assistants, under your rules | Early access, for brands that want presence in assistants |
Read the signals
- Relevance OS Dashboard: four tiers along the grid, with Maya's contribution isolated by holdout.
- Audience Segments: cohorts from onsite, offsite, and offline signals, joined under consent.
- Attribution Models: last touch, multi-touch, incrementality, and exposure-to-purchase models.
- Margin Reporting: revenue, cost, and net margin per impression, by placement and partner.
Build it
Engagement data reaches your systems today in two ways. The SDKs send engagement events to your own analytics as they happen. Scheduled exports send event rows to BigQuery, Mixpanel, or Amazon S3. Query Genuin event data in BigQuery shows the first queries to run.
The Intelligence SDK and the Octo calls in the Business Account API are proposed, not live. Live API today and the Business Account API roadmap maps what you can call now to what's planned.
Questions people ask
- How do I make Octo smarter about my brand? Asked by founders and business owners.
- Does Octo change our code, and who approves it? Asked by developers and engineering.
- Which routine work can Octo do without asking? Asked by operations and ad ops.
