Cold Start Problem

Cold start occurs when a recommender lacks enough interaction history for a new user, item, market, or context. Pure collaborative filtering cannot infer much from an empty row or column, so systems use content, priors, onboarding, or exploration until behavior arrives.

Serving-time fallbacks

A common serving-time fallback blends content and prior evidence:

For a new item, might come from metadata or image embeddings; for a new user, it might come from onboarding choices. Hybrid recommenders make this blend explicit.

Worked example

A new user profile can still score new items from content features and a popularity prior:

ItemContent vectorContent scorePopularity priorBlend
00.740.300.630
10.120.700.265
20.500.400.475

The rank is item 0, item 2, then item 1. The first new item wins because content aligns with the user profile, even before collaborative data exists. Exploration versus exploitation controls how aggressively cold items are exposed for learning.

Caveats

Cold-start fixes can become popularity defaults that bury new inventory. Onboarding adds friction and can collect noisy stated preferences. Content features may be missing or weak, so track cold-start segments separately in evaluation.

References