English

Campaign-2-PT-RAG: LLM-Guided Semantic Product Type Attribution for Scalable Campaign Ranking

Information Retrieval 2026-02-19 v2

Abstract

E-commerce campaign ranking models require large-scale training labels indicating which users purchased due to campaign influence. However, generating these labels is challenging because campaigns use creative, thematic language that does not directly map to product purchases. Without clear product-level attribution, supervised learning for campaign optimization remains limited. We present Campaign-2-PT-RAG, a scalable label generation framework that constructs user-campaign purchase labels by inferring which product types (PTs) each campaign promotes. The framework first interprets campaign content using large language models (LLMs) to capture implicit intent, then retrieves candidate PTs through semantic search over the platform taxonomy. A structured LLM-based classifier evaluates each PT's relevance, producing a campaign-specific product coverage set. User purchases matching these PTs generate positive training labels for downstream ranking models. This approach reframes the ambiguous attribution problem into a tractable semantic alignment task, enabling scalable and consistent supervision for downstream tasks such as campaign ranking optimization in production e-commerce environments. Experiments on internal and synthetic datasets, validated against expert-annotated campaign-PT mappings, show that our LLM-assisted approach generates high-quality labels with 78-90% precision while maintaining over 99% recall.

Keywords

Cite

@article{arxiv.2602.10577,
  title  = {Campaign-2-PT-RAG: LLM-Guided Semantic Product Type Attribution for Scalable Campaign Ranking},
  author = {Yiming Che and Mansi Ranjit Mane and Keerthi Gopalakrishnan and Parisa Kaghazgaran and Murali Mohana Krishna Dandu and Archana Venkatachalapathy and Sinduja Subramaniam and Yokila Arora and Evren Korpeoglu and Sushant Kumar and Kannan Achan},
  journal= {arXiv preprint arXiv:2602.10577},
  year   = {2026}
}

Comments

fix typo and author names