Intelligence SDK
Typed events, report queries, cohort membership, and Octo tools for your own applications and warehouse.
The Intelligence SDK is the proposed developer surface for the signals Genuin computes: relevance, engagement, cohorts, attribution, and revenue. As proposed, it delivers them as typed events and queries for your warehouse, your personalization, and your own AI applications. The SDK is proposed, not live, and the engagement data paths below work today.
This capability arrives as a proposal when your network needs it, filled in from your brand context, and goes live when you confirm it. It's part of Octo, and Intelligence SDK: bring Genuin signals into your own stack explains what it exposes.
When to use it
It's built for developers and analysts who want Genuin's signals next to their own data. These are the patterns that pay off with it.
| Pattern | What it gives you |
|---|---|
| Push watch-time cohorts into your CRM or CDP | Lifecycle marketing built on engagement |
| Join attributed commerce to your order data | True margin, as Margin reporting defines it |
| Read the relevance match score | A rule for when to show the player at all |
| Pull engagement by placement into your warehouse | The same numbers BCC reports, next to your business data |
How it works
As proposed, the SDK exposes four kinds of signal.
- Events: impression, play, watch milestones, follow, post, Quest entry, linkout click, conversion, and payout. They arrive as webhooks or a stream; server webhooks are proposed too, as Webhooks and events explains.
- Queries: the same reports as Brand Control Center (BCC), by grid dimension and cohort.
- Cohort membership: for a viewer identified through auto login, the cohorts Maya placed them in, under your data-use terms.
- Octo tools: calls to Octo Ask and Octo Resolve from your own application.
Each report in BCC already exports to CSV. Today, engagement events reach your stack through SDK callbacks and scheduled exports.
Set it up
The Intelligence SDK is proposed, not live. As proposed, Octo prepares these steps and you confirm them.
- Install the Intelligence SDK package.
- Authenticate with your API key. REST API: authentication and keys covers how keys and tokens work on the live API.
- Query reports or subscribe to events.
Settings
| Setting | What it controls |
|---|---|
| Key scope | Which reports, events, and cohorts a key can read |
| Event selection | Which events the key receives |
As proposed, a key never exceeds the role it was issued for. Roles come from Invite your team and assign roles.
What it reports
The SDK reports its own use. REST API: authentication and keys explains how keys are issued per brand and environment.
- Usage by key: how much each API key uses the SDK.
Connect your systems
These live paths deliver Genuin's engagement data today:
- Receive engagement events in your own analytics: SDK callbacks for live events in your app or page, plus scheduled warehouse exports.
- Query Genuin event data in BigQuery: the
genuin_datatable, column by column, with first queries on engagement. - Receive zero-party data in BigQuery: connect a dataset under Settings > Data Sources for daily, weekly, or monthly exports.
- Push analytics data to Mixpanel: sync engagement events to a Mixpanel project with a service account.
- Push analytics data to Amazon S3: land analytics exports in your bucket as CSV or Parquet files.
The signal and segment 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.
