Relevance OS: reading the analytics dashboard
Relevance OS is the analytics layer that treats relevance as the leading indicator of revenue: it shows, in four tiers, how well each feed matched its viewer, what that did to engagement, what that did to revenue, and what to change next. Reading time about 6 minutes.
The four tiers
| Tier | Question it answers | Key measures |
|---|---|---|
| Relevance | Did the right video reach the right viewer in the right context? | Match score, exploration share, repeat rate |
| Engagement | What did viewers do? | Watch time per user per minute, lift vs holdout, completion, follows (see Measure engagement: watch time, lift, and cohorts) |
| Revenue | What did engagement earn? | eCPM, fill, revenue per minute, attributed commerce (see Revenue reporting, payouts, and the Creator Wallet and Attribution: closed-loop commerce and conversion forecasts) |
| Adaptation | What should change? | Studio adaptation suggestions, Canvas actions, floor and pacing recommendations |
Reading it
Every tier is rolled up along the grid (see The Hierarchical Grid: one spine for inventory, layout, and reporting) and filterable by cohort (see Audience segments: onsite, offsite, and offline signals), experience (see Player experiences: Shorts, Shoppable, Community, and Live), content source, and partner. Maya's contribution is isolated by a standing holdout per placement, so lift is read directly rather than inferred.
The Adaptation tier
This is where the dashboard becomes an operator. Each recommendation (re-cut this video for PDPs, raise this floor, run a Quest in this group, pause this partner) shows the expected effect, and can be sent to Studio, Canvas, or Monetize with one click, or executed automatically under Canvas guardrails.
Scope
Relevance OS reports for US customers by default; other regions follow the data residency settings in Security, data residency, and compliance.
How it runs
These reports are reviewed on a cadence and the three recommended changes are brought to you; the ones you approve are applied. Any question about the numbers can be asked in plain language from the report.
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 /reports/relevance | Relevance OS dashboard data |
| GET /reports/engagement | Watch time, completion, lift, cohorts by placement, feed, community |
| GET /reports/revenue | Revenue by placement, partner, source, tier; payouts and creator shares |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.reports.relevance({ brandId });
await genuin.reports.engagement({ brandId, from, to, by: 'placement' });
await genuin.reports.revenue({ brandId, by: 'source' });Live today: Receive engagement events in your own analytics · Query Genuin event data in BigQuery.
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.
