Measure engagement: watch time, lift, and cohorts
Engagement on Genuin is measured as per-minute watch time per user, with lift against a holdout, broken down along the grid and by cohort, so you can see what Maya and your content decisions changed. Reading time about 5 minutes.
Core metrics
| Metric | Definition |
|---|---|
| Watch time per user per minute | Seconds of video watched per user, per minute of session, averaged across sessions on a placement |
| Lift | Difference in watch time, pages per session, or return rate between viewers who saw the placement and a matched holdout |
| Completion | Share of plays that reached 90 percent |
| Follow rate | Follows per thousand views |
| Return rate | Share of viewers who returned within seven days |
| Participation | Posts, comments, Quest entries per thousand members |
Where to read them
- Reports → Realtime – the last 60 minutes, per placement.
- Reports → Engagement – daily, rolled up along the grid (see The Hierarchical Grid: one spine for inventory, layout, and reporting), filterable by cohort (see Audience segments: onsite, offsite, and offline signals), experience (see Player experiences: Shorts, Shoppable, Community, and Live), and content source.
- Relevance OS (see Relevance OS: reading the analytics dashboard) – the same numbers reframed as leading indicators of revenue, with Maya's contribution isolated.
Exporting
Every report exports to CSV and is available through the Intelligence SDK (see Intelligence SDK: bring Genuin signals into your own stack) and webhooks (see Webhooks and events) for your own warehouse.
How it runs
The placements, feeds, destinations, and identity settings described here are proposed from your grid and audience, applied on confirmation, and tuned on a cadence from the reports.
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/engagement | Watch time, completion, lift, cohorts by placement, feed, community |
| GET /reports/distribution | Syndication and network distribution by platform, partner, feed |
| POST /accounts/{accountId}/webhooks | Subscribe to events (proposal.created, placement.published, member.subscribed, revenue.posted, moderation.flagged, …) |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.reports.engagement({ brandId, from, to, by: 'placement' });
await genuin.reports.distribution({ brandId });
await genuin.webhooks.create(accountId, { url, events: ['proposal.created'] });Live today: Receive engagement events in your own analytics · Query Genuin event data in BigQuery · Embed the Genuin Web SDK on your website · Integrate the Genuin iOS SDK.
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.
