This work extends an existing production recommendation model to a causal architecture using holdback data that is already collected as part of routine experimentation infrastructure, and shows that joint training with holdback data improves calibration of the treated head relative to the production baseline, and argues this can be taken as evidence that causal models learn more generalisable representations than models trained on observational data alone.
Abstract
Recommendation impressions are a finite resource, hence delivering a recommendation to a user who would discover the content organically yields no incremental value and displaces other recommendations that could. We address this by extending an existing production recommendation model to a causal architecture using holdback data that is already collected as part of routine experimentation infrastructure, requiring no new data collection. A central challenge is that attribution windows differ between treated and holdback observations: treated users are attributed a stream within a short direct-response window, while holdback users are attributed organic streams over a multi-day window. This mismatch makes naive treatment-effect subtraction invalid. We resolve this with a dual-threshold targeting policy that delivers a recommendation only when the probability of a treated stream is high and the probability of organic stream is low. In a production-scale A/B test on millions of Spotify users, this policy reduces recommendation impressions by 7% with no statistically significant reduction in overall recommended content consumption. We further show that joint training with holdback data improves calibration of the treated head relative to the production baseline, and argue this can be taken as evidence that causal models learn more generalisable representations than models trained on observational data alone.
The end-to-end treatment policy delivered a statistically significant $+7.20\% lift in the primary long-term-value metric, demonstrating the feasibility of production-scale causal optimization under business constraints.
Changshuai Wei, John Bencina, Phuc Nguyen et al.· 0 citations
This paper trains a recommender LLM to generate personalized explanations for its reccomendation, based on the user's watching history at a large video streaming service, and concludes that an LLM-based recommender can be fine-tuned on other complex tasks without compromising its original recommendation performance.
How well does a recommender system know you? These systems are typically trained on the silhouette of user activity to predict immediate engagement, yet this narrow focus may paradoxically expose how incomplete the system’s knowledge of the user really is. Rather than recommending from established user preferences, thi...
Daniel Nemirovsky, Priya Nirmal Singh Khokher, Adarsh Jois et al.· Proceedings of the 20th ACM...· 0 citations
Control via Request-Aware Masking for Editing Recommenders (CRAMER), a framework that takes users' natural-language requests to immediately change sequential recommendation models' behavior, establishing a new paradigm for request-aware sequential recommendation.
Zhiyuan Su, Naihe Feng, Zhen Qin et al.· 0 citations
Sequential recommendation predicts the next item from a user's interaction history, but not every interaction is equally informative. Real logs combine persistent preferences with temporary needs, exploration, and incidental behavior, so some interactions can distort history representations or provide unreliable superv...
Zichun Jin, Zihan Zhou, Yinan Liu et al.· 0 citations
Carousel interfaces are widely used in modern recommendation systems. Unlike traditional interfaces that present a single ranked list, carousels simultaneously present several ranked lists to the user, as horizontally swipeable rows stacked on top of each other. In this design, the rankings are closely tied to the two-...
Jingwei Kang· Proceedings of the 20th ACM...· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.