Audience Segments
Cohorts from onsite, offsite, and offline signals, joined through the ID graph under consent, usable for ranking, targeting, packaging, and export.
Audience segments are cohorts Maya, Genuin's relevance engine, builds from what viewers watch and do. Signals come from your properties, your offsite tags, and offline data you supply, such as purchases, loyalty, and store visits. Genuin joins them through the ID graph under your agreement and each viewer's consent.
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 Audience segments: onsite, offsite, and offline signals explains each signal source.
When to use it
Use it on commerce and retail models, and on any network with auto login. Each signal source needs a different setup.
| Source | Examples | Requires |
|---|---|---|
| Onsite | Groups watched, completion, follows, posts, products viewed | Nothing beyond the embed |
| Offsite | Offsite tag views and clicks, partner placement views | Offsite tags or distribution |
| Offline | Purchase files, loyalty tiers, store visits, CRM attributes | A commerce or retail agreement and the ID graph |
| Context | IP-level geography, device, time, weather, local events | Nothing |
How it works
- You combine conditions across sources. For example, "watched the trail-running group twice in 30 days and bought in the shoes category in 90 days."
- Size and overlap with your other segments appear as soon as you save. Segments then refresh continuously.
- Hashed identifiers you supply, such as email, loyalty ID, or device, are matched in Genuin's identity service. Raw identifiers never leave it, as Unified identity: auto login, SSO, and the ID graph explains.
- Segments contain cohort membership, never identifiers. Partners and buyers see sizes and names, never members.
- Consent is honored per viewer and per purpose, under the two-channel data flow in Privacy and VPPA.
- Auto login links a viewer's session to your user, so the same person is recognized across placements. Bring your audience in with auto login and SSO covers the setup.
Set it up
Octo proposes the segments your network needs with these steps already done. You review the result and confirm it.
- Create the segment under Audiences > Segments. Learn how in Audience segments: onsite, offsite, and offline signals.
- Choose its uses.
- Save it. Segments refresh continuously, with no further step.
Settings
| Setting | What it controls |
|---|---|
| Conditions | The signals, sources, and time windows a viewer must match |
| Uses | Maya ranking, Paid Partner targeting, audience extension on offsite inventory, Marketplace package definition, or export to your CDP |
| Partner visibility | Whether partners see the segment; they see its size and name, never its members |
Change conditions and uses under Audiences > Segments. For ranking, choose which cohorts Maya can use per placement in Player Controls and Feed Settings.
What it reports
Size and overlap show under Audiences > Segments, and engagement reports filter by cohort. Measure engagement explains how cohort engagement is counted.
- Size: how many viewers the segment holds.
- Overlap: how much the segment shares with your other segments.
- Performance by use: how the segment does in each use, such as ranking, targeting, or a package.
Connect your systems
Segments run in Brand Control Center, and the events behind them reach your stack today. Receive engagement events in your own analytics captures what members do in Genuin views, live from the SDKs and in batches to your warehouse. Query Genuin event data in BigQuery covers the genuin_data table and its first queries.
The 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.
