Prompt
How do I handle cold-start users and new items in recommendations?
Latest observation
Oct 9, 2026
OpenAI APIWeb search: off
Cold-start is the recommender problem where you have little or no interaction history for a user or item, so collaborative filtering alone struggles. The usual approach is to combine several strategies.
1) For cold-start users
Collect signal fast
- Ask for a few preferences at signup:
- favorite categories, brands, creators, price range
- “like/dislike” onboarding quiz
- Use implicit early signals:
- clicks, dwell time, searches, skips, saves
Use non-personalized or lightly personalized defaults
- Popular items overall
- Trending items in the user’s region/language/device segment
- Popular within a chosen category
- Editorially curated lists
Use content-based recommendation
Recommend items similar to what the user has explicitly liked or searched for:
- item metadata: category, tags, text, images, audio, embeddings
- user profile = aggregate of their stated preferences + early activity
Leverage context
- Time, location, device, referral source, seasonality
- Example: show local/trending content to a user from a new market
Segment-based bootstrapping
If you know the user belongs to a coarse segment:
- new parents, students, enterprise admins, etc. start with recommendations from that segment before enough personal data exists.
2) For cold-start items
Use item content/features
Before interactions exist, recommend based on:
- title, description, category, tags
- creator/brand attributes
- image/text/audio embeddings
- price, recency, inventory, quality flags
Seed exposure strategically
- Put new items into exploration slots
- Feature them in newsletters, category pages, “new arrivals”
- Use bandits/exploration to gather feedback quickly
Transfer from similar items
Use similarity to items with known performance:
- same category, style, or metadata profile
- embeddings from text/images can help a lot
Boost via business rules
- Give temporary exposure to new items
- Decay boost as engagement data accumulates
3) Hybrid models work best
Combine:
- Collaborative filtering for users/items with history
- Content-based for cold-start
- Popularity/trending as fallback
- Business rules and exploration
A common architecture:
- Candidate generation:
- popular items
- content-similar items
- collaborative candidates
- fresh/new item candidates
- Ranking model:
- uses user, item, and context features
- Re-ranking:
- diversity, freshness, constraints, exploration
4) Use exploration explicitly
If you never show new items, they’ll never get data.
- epsilon-greedy
- multi-armed bandits
- Thompson sampling
- contextual bandits
This helps you learn quickly while limiting risk.
5) Practical fallback hierarchy
A good fallback order is often:
- Highly personalized recommendations
- Content-based matches
- Segment-based popular items
- Global popular/trending
- Editorial defaults
6) Measure separately
Cold-start should be evaluated on:
- new users with 0–N interactions
- new items with 0–N impressions/interactions
- time-to-first-click, time-to-first-conversion
- coverage of new items
- retention and long-term engagement
7) Common pitfalls
- Over-relying on popularity, which can reinforce bias
- Showing too much exploration and hurting UX
- Ignoring metadata quality for content-based methods
- Treating all new users/items the same
- Failing to separate short-term click metrics from long-term value
If you want, I can also give you:
- a cold-start architecture diagram
- a modeling strategy for ecommerce / media / SaaS
- or example feature sets and ranking formulas.