Skip to main content

Engine

Engine is where you tune, tweak, and implement the recommender itself: the scenarios, rules, signals, models, and loops that decide what each member sees.

Where Studio answers "what should I make or fix next," Engine answers "is the recommender doing the right thing, and how do I change it."

Who this is for​

The people who operate the recommender: product managers shaping placements, data scientists reading quality, and developers wiring it up. Engine pages assume you are comfortable with the platform's own terms, and link down to the Platform docs for the deep reference (model math, connector configuration, the query language, the SDK) rather than repeating it.

What's here​

  • Scenarios — saved queries given stable, public names, so your app can keep calling one name while you change what it returns.

More Engine surfaces are documented as they ship.