Feed Management

Feeds are served from saved algorithms through feed configs. In Console, use Algo to build and save algorithms, then use Feed to decide how those algorithms are served in production.

Current Console Flow

Build and save one or more algorithms in Algo.
Open Feed.
Create or edit a feed config.
Add the saved algorithms as the main feed candidates.
Set weights when mixing multiple algorithms.
Add fallback algorithms for sparse or cold-start cases.
Configure cache TTLs and exclusion rules.
Save and test the feed config.

What A Feed Config Controls

Area	What it does
Main algorithms	The saved algorithms used for normal feed requests
Weights	How much each main algorithm contributes when several are mixed
Primary fallback	A broader algorithm used when the main set is sparse
Secondary fallback	A final fallback for cold start or empty results
Cache age	How long results can be reused before rebuilding
Exclusion rules	Hide items recently shown, consumed, dismissed, or otherwise excluded
Test panel	Runs the saved config and shows served output

Feed configs do not create a new ranking system. They orchestrate saved algorithms, fallback behavior, caching, and exclusions.

Recommended Setup

Start simple:

Use one strong main algorithm.
Add one fallback algorithm that is broader than the main algorithm.
Set a cache TTL that matches the feed freshness requirement.
Add exclusion rules only after the feed is producing useful results.
Test the served feed after each change.

Only add weighted mixes after each individual algorithm has been validated.

Example Feed Config Plan

Slot	Algorithm type	Weight	Why
Main	Fresh token discovery	0.7	Primary product experience
Main	Wallet or trader activity	0.3	Adds active-user signal
Primary fallback	Broad token discovery	1.0	Handles sparse main results
Secondary fallback	Recent market items	1.0	Prevents empty cold-start feeds

Cache Guidance

Feed type	Cache suggestion
Fast-moving trading or notification-style feeds	Shorter cache age
Discovery feeds with slower-changing items	Longer cache age
Cold-start fallback feeds	Longer cache age is usually acceptable

Lower cache age improves freshness but increases rebuild cost. Higher cache age improves stability but can feel stale.

Exclusion Rules

Use exclusion rules to prevent repeated output. Common examples:

Hide items shown recently.
Hide consumed or dismissed items.
Hide a field-based group when another related item has already appeared.

Start with recent-shown exclusions first. Add more rules only when you see repeated or unwanted items in the test panel.

Test Before Shipping

Always test the feed config, not only the algorithm preview. The config test is the closest match to production serving because it includes weights, fallback, cache behavior, and exclusions.

Build source algorithms in Building Algorithms.
Configure serving in Deploy Feed Configs.
Check search sources in Supported Indices.