Package Builder
Assemble groups, placements, windows, offsite tags, and audience extension into one sellable package with an outcome forecast.
A package is a sellable bundle of inventory and outcomes. Package Builder puts the groups, placements, and offsite reach a buyer wants into one offer, with a forecast attached. Genuin drafts each package priced against your floors and brand safety profile, and money never moves on a change you didn't approve.
This capability arrives as a proposal when your network needs it, filled in from your brand context, and goes live when you confirm it. It's part of Marketplace, and Paid Partner Posts and Paid Partner Takeovers explains what a package sells and how it's priced.
When to use it
Use it for any direct or marketplace sale. The buyer's classification sets which package types fit them, as Brand Network: core concepts and how brands are classified explains.
| Buyer | What the package carries |
|---|---|
| Endemic demand brand, such as a shoe brand on a running site | Category groups and Paid Partner Posts |
| Non-endemic brand, such as a bank on a sports site | Takeovers and audience extension |
| Data brand | Segments you co-target with the brand |
How it works
- Inventory is your groups and placements, plus offsite tags and audience extension.
- A Paid Partner Post is priced per thousand views or per post, and a Takeover per window. You can bundle Takeovers with Posts and offsite tags into one package.
- Genuin forecasts views, engagement, and attributed conversions from history, cohort size, and seasonality. That forecast becomes the package's outcome block.
- Sell directly with a proposal link the partner accepts in their own BCC. Or list the package in Marketplace and AdCP, covered in Marketplace Listing and Discovery.
- Creative goes through Monetize > Approvals, or Canvas approves it within your guardrails.
- Canvas's Monetization fleet builds packages from your inventory and audience. Learn more in Canvas Monetization Fleet.
Set it up
Octo proposes the package with these steps already done. You review the result and confirm it.
- Create the package under Monetize > Packages. Learn how in Paid Partner Posts and Paid Partner Takeovers.
- Add inventory, such as groups and placements, and the outcome forecast. Learn how forecasts are built in Attribution: closed-loop commerce and conversion forecasts.
- Sell directly, or list the package. Learn how in Marketplace: list packages and transact with demand partners.
Settings
| Setting | What it controls |
|---|---|
| Inventory | The groups, placements, offsite tags, and audience extension in the package |
| Window | When the package runs, such as a launch day, a weekend, or a season |
| Price model | How the package is priced: fixed, CPM, or request-a-quote |
| Forecast | The projected views, engagement, and attributed commerce shown with the package |
Change them on the package under Monetize > Packages, or let Canvas move prices within the bounds you set.
What it reports
Each package reports delivery against its forecast, so renewals rest on outcomes. Reports > Revenue also breaks revenue down by package and partner.
- Delivered views: the views the package delivered, against the forecast.
- Engagement: delivered engagement, against the forecast.
- Attributed commerce: sales linked to exposures from the package.
- Net margin on ad spend: the gross margin on attributed sales minus the partner's spend, divided by spend. Margin reporting: revenue per impression and net margin on ad spend explains how it's counted.
Build on it
Packages are built and sold in Brand Control Center, so the package itself needs no code. Serve your first ad covers giving ads a place to render: in your feeds, in an IAB ad unit in your app, or on a partner's page.
The package calls in the Business Account API are proposed, not live. Live API today and the Business Account API roadmap maps what you can call now to what's planned.
