Player Controls and Feed Settings
Autoplay, sound, captions, share and follow buttons, comment visibility, sticky player, and Maya's parameters, set per page type or placement without code.
Player controls set how the player behaves on a page. Feed settings set the parameters Maya, Genuin's relevance engine, uses to rank each feed. You change both in Brand Control Center, without a code change.
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 Controls, and Personalization and relevance: how Maya ranks every feed explains the signals Maya ranks with and the parameters you control.
When to use it
Use it any time, because changes apply without a code change or redeploy. Before you change a placement's feed settings, run an experiment so the change reads as lift. Several placements take their options from here:
| Placement | What you set here |
|---|---|
| Horizontal Video Player Placement | Carousel or inline layout per page type |
| Audio + Video Dynamic Player | Audio-first or video-first default per page type |
| Keywords Player | Minimum match score and maximum players per page |
| Community Wall Placement | Comment visibility and reactions |
| Sticky Mini-Player | The mini-player on or off per page type |
| Contextual Continuity | Repeat window and continuity weight |
How it works
- You set defaults per page type and override them per placement.
- Maya ranks from placement and page context, group and topic, session continuity, audience cohorts, and brand and partner rules. Feed settings are the parameters you control on top of those signals.
- Maya is measured on per-minute watch time per user and per-minute revenue.
- In a network of publishers, each publisher's placements inherit the house defaults unless their brand overrides them.
Set it up
Octo proposes the settings with these steps already done. You review the result and confirm it.
- Open Controls > Feed settings or Controls > Player controls.
- Set defaults per page type, then override them per placement where needed.
- Options set in code override both. The Embed configuration reference shows what each SDK accepts.
Settings
| Setting | What it controls |
|---|---|
| Exploration rate | How often Maya tests new or low-data videos |
| Freshness | Preference for recent content |
| Repeat window | Minimum time before a viewer sees the same video again |
| Pinned slots | Fixed positions for brand or partner content |
| Cohort use | Which connected cohorts Maya can use on this placement |
| Paid pacing | Maximum share of Paid Partner Posts per session |
| Player toggles | Autoplay, sound, captions default, share and follow buttons, comment visibility, and sticky player |
Feed settings hold the first six, and player controls hold the toggles. Both apply per page type or per placement.
What it reports
Relevance OS shows the effect of each change against the placement's standing holdout. Relevance OS: reading the analytics dashboard explains how each tier is read.
- Relevance: match score, exploration share, and repeat rate.
- Engagement: watch time per user per minute, completion, and follows.
- Lift: watch time against the holdout, set in Placement Experiments and Holdouts.
Add it to your site
The Web SDK renders the placements these settings shape. Add a Genuin placement to your website covers the placement and style IDs, and Embed the Genuin Web SDK on your website covers loading the script. Customize the Genuin video player sets size, tile layout, profile menu, and deep links in code on every SDK. It notes that a Player Controls change can take up to 15 minutes to reach views. Add moderators to a community gives accounts the moderator role in the communities your player draws from.
The placement settings 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.
