Audience segments: onsite, offsite, and offline signals
Audience segments are cohorts Maya builds from what viewers watch and do onsite, what they do on your offsite tags, and offline signals you supply (purchases, loyalty, store visits), joined through the ID graph under your agreement and the viewer's consent. Reading time about 5 minutes.
Signal sources
| 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 (see Offsite: generate IAB-standard tags for your media plan) or distribution (see Network distribution: place your content in partner inventory) |
| Offline | Purchase files, loyalty tiers, store visits, CRM attributes | Commerce or retail agreement (see Choose your monetization agreement), ID graph (see Unified identity: auto login, SSO, and the ID graph) |
| Context | IP-level geography, device, time, weather, local events | Nothing |
Building a segment
- In BCC open Audiences → Segments and choose Create.
- Combine conditions across sources ("watched the trail-running group twice in 30 days and bought in the shoes category in 90 days").
- Choose uses: Maya ranking (see Personalization and relevance: how Maya ranks every feed), Paid Partner targeting (see Paid Partner Posts and Paid Partner Takeovers), audience extension on offsite inventory (see Programmatic: Genuin Ad Server or your partner ad server), Marketplace package definition (see Marketplace: list packages and transact with demand partners), export to your CDP (see Intelligence SDK: bring Genuin signals into your own stack).
- Save. Size and overlap with other segments appear immediately; segments refresh continuously.
Privacy
Segments contain cohort membership, never identifiers. Partners and buyers see sizes and names, never members. Consent state is honored per viewer and per purpose (see Privacy and VPPA: the two-channel data flow).
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 /brands/{brandId}/segments | Audience segments from onsite, offsite, and offline signals |
| POST /brands/{brandId}/segments | Define a segment from signals and cohorts |
| PUT /brands/{brandId}/identity | ID graph settings: hashed identifiers, consent, channels |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.segments.list(brandId);
await genuin.segments.create(brandId, { rules });
await genuin.identity.update(brandId, { hashedEmail: true });Live today: Receive engagement events in your own analytics · Query Genuin event data in BigQuery · Serve your first ad.
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.
