DoorDash builds a universal ranker with UCB exploration for homepage personalization
DoorDash's homepage used a fixed entity ordering (carousels first, stores second) that worked initially but became suboptimal as the carousel count grew dramatically, burying individual stores. Pure exploitation of known preferences also risked filter bubbles and unfair treatment of newer merchants.
A fixed ordering of carousels before stores stopped scaling as carousel count exploded. Building a dedicated ranking model per entity type was impractical, and calibrating scores across mixed entity types proved nontrivial.
The combined Universal Ranker and UCB framework showed consistent improvements in online experiments, driving more consumer engagement and conversions on the homepage and increasing consumer interest in new merchants.
Frequently asked questions
What did this team achieve with this AI workflow?
The combined Universal Ranker and UCB framework showed consistent improvements in online experiments, driving more consumer engagement and conversions on the homepage and increasing consumer interest in new merchants.
What tools did this team use?
ElasticSearch, PyTorch, Fabricator, LSTM.
What results were reported?
Homepage recommendation performance: consistent improvements in our online experiments; Consumer homepage engagement and conversion: more consumers to engage with our recommendations and convert on the homepage; Consumer exploration of new merchants: More consumers are interested in trying new merchants and items they never ordered before (source-reported, not independently verified).
What failed first in this deployment?
A fixed ordering of carousels before stores stopped scaling as carousel count exploded.
How is this ecommerce ops AI workflow structured?
FPR candidate retrieval → SPR filtering and pre-ranking → Universal Ranker pConv scoring → UCB uncertainty blending → Final ranked homepage output → Daily engagement data refresh.