Partner Content Acceptance (Inbound)
Brands and networks you trust place content into named groups under your rules, filling feeds and creating Paid Partner inventory.
Inbound acceptance is the inbound half of every brand partnership. Partners send content into the groups you name on your properties, and Maya ranks it alongside your own. You decide which groups, which permissions, and what share the partner earns.
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 Network, and Accept partner content into your ecosystem explains what partner content can and can't do.
When to use it
Use it when your library is thin, or when you're a retailer with endemic brands. A library of 30 videos becomes hundreds the day you accept two partners, and Maya has more to rank.
How a partner relates to your category shapes the acceptance it gets:
| Partner type | What acceptance usually looks like |
|---|---|
| Endemic: sells what your audience comes to you for | Highest ranking weight in category groups, and eligible for category-group Paid Partner Posts |
| Adjacent: complements your category | Content acceptance on, with moderate weight |
| Non-endemic: wants your audience but sells something else | Content acceptance usually off; paid partnership instead |
How it works
- Each request shows the partner, their brand safety profile, the groups they want, and a sample of their content. The requesting brand is classified, and a recommendation comes with it.
- Accepted content appears only in the groups you named, even where the context matches elsewhere.
- Maya ranks partner content like your own. It can't bypass your moderation or your brand safety profile.
- The post carries the partner's brand, but it can't change your brand kit on the placement. It can't collect viewer data from your properties either.
- Studio re-cuts accepted content to your brand kit when the partner allows it.
- For retailers, endemic brands' content in category groups is the simplest Paid Partner Post inventory.
Set it up
Octo proposes acceptance with these steps already done. You review the result and confirm it.
- Review requests under Network > Requests. Learn how in Accept partner content into your ecosystem.
- Accept with conditions: groups, re-cut, paid content, and revenue share. Learn how in Add brand partners and demand partners.
- Pause a partner under Network > Partners. Learn how in Brand Partner Invitations and Permissions.
Settings
| Setting | What it controls |
|---|---|
| Group scope | The named groups the partner's content may enter |
| Permissions | Whether the content may be re-cut, and whether it can carry Paid Partner Posts |
| Share | The share the partner earns on revenue its content makes on your placements |
By default, a content partner gets the groups you name, with re-cut and paid content off. Change any of these per partner under Network > Partners, where each partner also has a toggle to pause it.
What it reports
Revenue reporting, payouts, and the Creator Wallet explains how revenue is counted and reconciled.
- Partner content views: views of accepted content on your placements.
- Partner content revenue: what accepted content earns on your placements.
- Moderation load from partners: how much moderation work partner content adds.
Network Reporting breaks views and revenue down by partner and placement.
Add it to your site
Accepted content reaches your pages through the groups your feeds already show, so acceptance needs no code.
Embed the Genuin Web SDK on your website covers rendering your brand, community, and group feeds. Deliver contextual feeds with page, user, and location context covers passing page context, including the network brand IDs a feed can draw from. Serve your first ad covers in-feed ads, which need no ad-specific code.
The acceptance 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.
