Marketers: run a partner campaign onsite and offsite
A marketer runs one campaign across a partner's groups onsite and the open web offsite, with one creative set, one audience, and one attribution report.
Steps
- Define the outcome. Pick the KPI: attributed sales, sign-ups, or watch time; set the attribution window (see Attribution: closed-loop commerce and conversion forecasts).
- Build the audience. A segment from onsite, offsite, and offline signals (see Audience segments: onsite, offsite, and offline signals), or the partner's segment if you are buying.
- Produce. Brief Studio with the creative set; it adapts to each placement size and the partner's brand kit (see Studio: produce brand video from podcasts, long-form, and catalogs).
- Buy onsite. Request a Paid Partner Post package in the partner's category groups, or a Takeover for launch day (see Paid Partner Posts and Paid Partner Takeovers and Marketplace: list packages and transact with demand partners).
- Buy offsite. Generate IAB tags with the same creative and audience for your DSP or the partner's ad server (see Offsite: generate IAB-standard tags for your media plan and Programmatic: Genuin Ad Server or your partner ad server).
- Measure. One report across onsite and offsite with incrementality where a holdout exists (see Attribution: closed-loop commerce and conversion forecasts), and net margin on ad spend (see Margin reporting: revenue per impression and net margin on ad spend).
- Renew. Compare delivered outcomes to the forecast in the package; renew or re-brief.
How it runs
This playbook runs as a sequence of proposals, one per step, ordered for your company type; you confirm each one and the 30-day outcome is reported against the plan.
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 |
|---|---|
| POST /brands/{brandId}/tags | Generate an offsite tag: VAST, JavaScript display, dynamic feed, audience extension |
| POST /brands/{brandId}/creatives | Turn community content into ad creative for a media plan |
| POST /brands/{brandId}/sponsorships | Paid Partner Post or Takeover: offer, budget, CPM, dates, placements |
| POST /conversions | Server-side conversion API for attribution postbacks |
| GET /reports/attribution | Closed-loop commerce, conversion forecasts, offsite attribution |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.tags.create(brandId, { kind: 'vast', feedId, sizes });
await genuin.creatives.create(brandId, { videoIds, sizes });
await genuin.sponsorships.create(brandId, { partnerId, kind: 'takeover', budget });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.
