Feed Management Overview
A feed config bundles one or more algorithms with weights, fallbacks, cache settings, and page size. This is what you create in the Console's Feed Builder, and what powers production feed delivery via POST /deploy/serve.
How It Works
Algorithm A ──┐
├──→ Feed Config (config_id: 104) ──→ POST /deploy/serve ──→ Users
Algorithm B ──┘ │
weights: 60/40
fallback: algo A
cache: 1 hour
page size: 25
- Build algorithms in the Algo Builder — each algo produces a ranked feed
- Create a feed config that combines algos with interleaving weights and fallbacks
- Serve the config to users with pagination and cache management
Console Feed Builder
The Console Feed Builder lets you:
- Select algorithms — pick one or more saved algos from the dropdown
- Set weights — control what percentage of items come from each algo (e.g. 60% trending, 40% personalized)
- Configure fallbacks — what algo to use if the primary fails
- Set cache TTL — how long to cache results before rebuilding
- Preview — test the full config with real user inputs in the right panel
- Copy serve code — get a ready-to-use
curlcommand for yourconfig_id
The Feed Lifecycle
| Step | Console Action | API Equivalent | Guide |
|---|---|---|---|
| Create algorithms | Algo Builder | POST /deploy/algos | Building Algorithms |
| Bundle into config | Feed Builder | POST /deploy/configs | Feed Configs |
| Test config | Preview panel | POST /deploy/preview | Feed Configs |
| Set deployment status | Status toggle | Console only | Deployment Status |
| Serve to users | Copy serve code | POST /deploy/serve | Serving |
| Paginate | — | GET /deploy/serve/page | Serving |
| Check for new items | — | GET /deploy/serve/new_items | Serving |
| Clear cache | — | POST /deploy/cache/clear | Serving |
What's Next
- Feed Configs → Multi-algo interleaving, fallbacks, cache settings, exclusion rules
- Serving → Production serving with pagination, new items, and cache management
- Deployment Status → Draft, Group, and Live warmup tiers
Updated 8 days ago
