Dynamic in-video linkouts and affiliate commerce

A dynamic in-video linkout is a product, offer, or destination attached to a video at the moment and context it is viewed, resolved at serve time by Octo, so one video can sell different products on different pages, partners, and days. Reading time about 6 minutes.

How linkouts resolve

1. A video carries tagged moments (Studio detects products, places, and mentions; you can edit them).
2. At serve time, Octo (see Octo: the orchestration and generative commerce layer) matches the moment to your catalog, a partner's catalog, or an affiliate network, using the placement context, the viewer's cohort, and availability.
3. The player renders the linkout: buy, add to cart, save, or go to partner. Your own checkout is used when connected; affiliate links are used otherwise.
4. The click and any conversion are attributed (see Attribution: closed-loop commerce and conversion forecasts) and reported with revenue and net margin (see Margin reporting: revenue per impression and net margin on ad spend).

Steps

1. Connect a catalog (see Connect your website, app, and podcast feed) or an affiliate network under Monetize → Commerce.
2. Choose default behavior per placement: your checkout, partner checkout, or affiliate.
3. Set rules: minimum margin, excluded products, and which partners' catalogs may resolve on your placements.
4. Publish. Linkouts appear on tagged moments immediately.

Generative commerce routing

For intent that your catalog cannot serve, Octo can route to large retail assistants and marketplaces under your agreement, so the viewer still completes and you still earn an affiliate or referral share.

How it runs

The demand setup, packages, agreements, and seller files described here are drafted for you, priced against your floors and brand safety profile, and switched on only with your approval; money never moves on a change you did not approve.

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.linkouts.create(brandId, { videoId, destination });
await genuin.octo.resolve({ placementId, intent });
await genuin.reports.attribution({ brandId, model: 'last-touch' });

Live today: Serve your first ad · Receive engagement events in your own analytics · Query Genuin event data in BigQuery.

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.