Attribution: closed-loop commerce and conversion forecasts

Attribution links video exposures to outcomes (clicks, add-to-carts, purchases, sign-ups, offline sales) through the ID graph and your connected commerce events, reports them per placement and partner, and forecasts conversions for packages before they are sold. Reading time about 6 minutes.

Models available

• Last touch – default for self-serve networks.
• Multi-touch, time-decayed – default for commerce and retail agreements.
• Incrementality – holdout-based lift, the standard for Extended O&O and Paid Partner packages.
• Exposure-to-purchase – links earlier exposures to a later purchase using the viewer's historical propensity; used for offline and store sales.

Connecting outcomes

1. In BCC open Audiences → Conversions.
2. Add a source: the SDK's track call from your checkout, a server-side conversion API call (see REST API: authentication and keys), an offline purchase file, or a partner's postback.
3. Map events to outcomes and values (order value, margin where available).
4. Choose attribution windows per outcome.

Forecasts

For any package or placement, Genuin forecasts views, engagement, and attributed conversions from history, cohort size, and seasonality; the forecast is the outcome block shown to buyers in Marketplace and AdCP (see Marketplace: list packages and transact with demand partners and AdCP: make your inventory discoverable to AI buyer agents) and is reconciled against delivery.

Reading attribution

Reports → Attribution shows outcomes by placement, partner, cohort, and content, with incrementality where a holdout exists, and feeds the margin report (see Margin reporting: revenue per impression and net margin on ad spend).

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.

// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.reports.attribution({ brandId, model: 'last-touch' });
await genuin.conversions.create({ event, value, hashedEmail });

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.