Skip to main content
Studio is the default console workflow for shaping outcomes. Instead of jumping between separate pages for contexts, rules, pipelines, and explainability, Studio keeps the full loop in one place:
  1. Choose a studio.
  2. Change logic.
  3. Preview output.
  4. Verify why it happened.
  5. Publish.
Studio workflow overview

​
What a studio is

A studio is the working surface for a recommendation experience. In practice that can be:
  • A homepage rail
  • A related content module
  • A campaign surface
  • A fallback global behavior
Studio is intentionally outcome-focused. You might pin an item, demote a class of items, add grouping, adjust retrieval, or change execution. The point is not only placement. The point is shaping what the user sees.

​
The workflow

​
1. Choose studio

Open Console > Studio and select the surface you want to work on.
  • Use Global studio when you want to change fallback behavior.
  • Use a named context studio when you want to shape a specific surface.
The Studio header shows the key live state for that surface:
  • active rules
  • pin rules
  • active pipeline status
  • most recent update

​
2. Change logic

Use the tabs to make changes without leaving the workflow:
  • Context for retrieval boundaries, grouping, dedupe, forced items, and ordering controls
  • Rules for boost, bury, pin, filter, cap, and diversity logic
  • Pipeline for stage execution and rule-stage availability
Studio-scoped creation happens inline. A rule or pipeline created inside Studio inherits the current studio scope automatically.

​
3. Preview output

Open the Preview tab and run the studio against a real user.
  • Enter a user ID
  • Choose the result limit
  • Run preview
The preview shows the actual ranked output you should expect the front-end to receive next. This is the fastest way to answer the question, “what would the user see right now?”

​
4. Verify why it happened

Open the Verify tab to confirm the result is not only visible, but explainable. Use Verify to confirm:
  • the item actually matched the rule you created
  • the active pipeline includes the rules stage
  • no experiment is silently excluding your rule
  • the item’s final position is consistent with the logic you expected
This is the step that prevents “the admin UI saved but nothing changed” failures.

​
5. Publish

Open the Publish tab before you leave the workflow. Studio shows the live publish model explicitly:
  • saving an active rule publishes immediately
  • saving an active pipeline publishes immediately
  • saving a context publishes immediately
There is no separate draft promotion step for these objects today. That makes Preview and Verify critical before you affect the front-end.

​
Example: newsroom emergency rail

This is a good Studio test because it has one unambiguous expected outcome. Scenario:
  • Industry: news publisher
  • Surface: homepage weather emergency rail
  • Goal: pin the item School closures and travel disruption map to slot 2
  • User impact: readers should see the closures guide immediately after the live blog, not in a variable position
Quantifiable pass condition:
  • the preview result in slot 2 is exactly School closures and travel disruption map
  • Verify shows the pin rule matched that item
That is the kind of change Studio is designed to make easy to prove end to end.

​
When to leave Studio

Use the advanced pages when you need lower-level control across many objects at once: