Offsite: generate IAB-standard tags for your media plan

Offsite extends your network beyond your properties by packaging your video as IAB-standard ad tags that any media plan, DSP, or publisher ad server can run, with return on ad spend as the measure. Reading time about 6 minutes.

What an offsite tag is

A Genuin player, sized to a standard IAB unit (see Player card sizes and IAB footprint spec), delivered as a VAST tag or a JavaScript tag (see Ad tag reference: VAST, IAB sizes, and macros), carrying a chosen group, experience, and brand kit, plus the tracking macros your buyer uses. The viewer sees your brand's video in someone else's placement; the engagement comes back to your network.

Steps

1. In BCC open Offsite → Tags and choose Create tag.
2. Choose the content: a group, a Quest's winners, a Paid Partner Post, or a dynamic feed Maya fills by context.
3. Choose the size and format: VAST 4.x for video slots, JavaScript for display slots, or both.
4. Add macros for the destination (click, impression, viewability, consent string, and the buyer's placement ID).
5. Choose Generate. Copy the tag into your DSP, ad server, or partner's trafficking sheet, or hand it to your agency.
6. Watch Reports → Offsite for impressions, viewability, engagement, and clicks back to your properties.

Attribution

When an offsite viewer later lands on your property, the unified identity layer (see Unified identity: auto login, SSO, and the ID graph) links the two under your privacy settings, and attribution (see Attribution: closed-loop commerce and conversion forecasts) credits the tag. Conversions can also be reported back to your DSP through the macros.

Creative from community content

Offsite tags can run community and creator content as ad creative, with the creator's consent captured on their post; each creative keeps its attribution to the creator for the revenue share (see Revenue reporting, payouts, and the Creator Wallet).

How it runs

The placements, feeds, destinations, and identity settings described here are proposed from your grid and audience, applied on confirmation, and tuned on a cadence from the reports.

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.tags.create(brandId, { kind: 'vast', feedId, sizes });
await genuin.tags.get(tagId);
await genuin.conversions.create({ event, value, hashedEmail });

Live today: Serve your first ad · Receive engagement events in your own analytics.

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.