Delayed feedback describes the temporal gap between a user action, like an ad click, and the subsequent observable label, such as a product purchase that occurs days later. In real-time CTR prediction, training pipelines that naively join clicks with conversions within a short window will incorrectly label recent clicks as negatives, poisoning the model with false negatives and biasing it against items with longer conversion cycles.
Glossary
Delayed Feedback

What is Delayed Feedback?
Delayed feedback is a critical data integrity challenge in real-time click-through rate (CTR) prediction where the true label for a training instance, such as a conversion, is not immediately observable, leading to false negatives if not explicitly modeled.
To mitigate this, specialized techniques like the delayed feedback model (DFM) jointly train on a conversion prediction model and a time-delay model, treating the unobserved label as a latent variable. Alternative approaches include importance sampling to re-weight observed positives or waiting for a full observation window before labeling, trading off model freshness for label accuracy.
Core Characteristics of Delayed Feedback
Delayed feedback is a fundamental data integrity problem in online advertising where a conversion label (e.g., a purchase) arrives hours or days after the click event. This latency creates a critical modeling hazard: training instances without an immediate label are incorrectly treated as negative examples, poisoning the model with false negatives.
The False Negative Problem
In standard binary classification for CTR/CVR prediction, training instances are labeled immediately. With delayed feedback, a click that will eventually lead to a conversion is temporarily labeled as 0 (negative). This introduces systematic label noise.
- Impact: The model learns to underestimate the true conversion probability.
- Mechanism: The loss function penalizes the model for correctly predicting a high probability on a positive example that hasn't been labeled yet.
- Scale: In long-cycle products (e.g., auto insurance, travel), the delay window can exceed 30 days, meaning a significant fraction of training data is mislabeled at any given time.
Observation Window & Censoring
The observation window is the fixed period after a click during which a conversion label is expected to arrive. Data is considered censored if the window has not yet elapsed.
- Fixed Window: A click is only labeled negative if no conversion occurs within W days (e.g., 7 days).
- Censored Instances: Clicks that are younger than W days are either excluded from training or modeled with a survival analysis approach.
- Trade-off: A longer window reduces false negatives but increases the staleness of the training data, as you must wait W days to finalize labels.
Delayed Feedback Models (DFM)
Specialized architectures that jointly model two probabilities: the conversion probability and the expected delay time.
- Chapelle's Model (2014): A seminal approach that assumes delay follows an exponential distribution and trains a model to predict both P(conversion) and E[delay].
- NoDelay (2020): A neural network approach that uses a survival analysis framework, treating the delay as a censored time-to-event problem.
- ES-DFM (2021): An importance-sampling method that re-weights recent, unlabeled data to correct for the false-negative bias without waiting for the full observation window.
Importance Sampling Correction
A statistical technique to re-weight training instances based on the probability that their true label has been observed.
- Inverse Propensity Weighting: Each instance is weighted by 1 / P(label observed | elapsed time).
- Fake Negative Weighting: The model assigns a small, non-zero weight to the possibility that a currently negative instance is actually a fake negative.
- Benefit: Allows the model to train on fresh, recent data immediately without waiting for the full observation window, dramatically reducing model staleness.
Feedback Loop Contamination
Delayed feedback doesn't just affect offline metrics; it creates a self-reinforcing bias in production systems.
- Downward Spiral: A model trained on false negatives underestimates CTR/CVR, leading to lower bids and reduced exposure for affected items.
- Reduced Opportunity: Lower exposure means fewer clicks and fewer observed conversions, further starving the model of positive labels.
- Mitigation: Requires explicit exploration mechanisms or counterfactual evaluation to break the cycle and collect unbiased data.
Evaluation Under Delayed Feedback
Standard metrics like AUC and Log Loss are biased when evaluated on data with unobserved labels.
- Delayed AUC: Only evaluates on instances where the observation window has fully elapsed, ensuring label certainty.
- Expected Calibration Error (ECE): Measures if predicted probabilities match eventual observed frequencies, requiring a waiting period for ground truth.
- Streaming Evaluation: Continuously re-evaluates predictions as labels trickle in, updating metrics retroactively when a previously negative instance converts.
Frequently Asked Questions
Addressing the core challenge of training click-through rate models when conversion labels arrive hours or days after the initial click, and the specialized techniques required to maintain model accuracy.
Delayed feedback is a critical data integrity challenge in click-through rate (CTR) prediction where the true label for a training instance—specifically a conversion event like a purchase or app install—is not immediately available at the time of the click. In real-time advertising and recommendation systems, a user may click on an item but only convert days later. If a model is trained naively before the conversion label arrives, that positive instance is incorrectly marked as a false negative, poisoning the training dataset. This temporal discrepancy between the click timestamp and the conversion observation window introduces a systematic bias, causing the model to underestimate the true CTR. The challenge is pervasive in real-time bidding (RTB) and e-commerce personalization, where the median conversion delay can range from minutes to weeks depending on the product vertical. Properly handling delayed feedback requires specialized modeling techniques that treat unlabeled recent data as temporarily uncertain rather than definitively negative.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Core concepts and modeling techniques used to address the challenge of missing labels in real-time prediction systems.
Fake Negative Calibration
A critical preprocessing step where negative labels observed shortly after an action are treated as unlabeled rather than true negatives. This prevents the model from incorrectly learning that a user who will convert tomorrow is a non-converter today. The observation window is dynamically adjusted based on the expected conversion delay distribution.
Importance Sampling Reweighting
A statistical technique that corrects for the selection bias introduced by waiting for labels. Since training only on 'mature' examples skews the dataset toward short-delay conversions, importance sampling assigns higher weights to examples with longer observed delays. This ensures the model's expected loss on the biased sample matches the true loss on the full distribution.
Observation Window Strategy
The fixed duration an engineer waits before finalizing a negative label. A short window introduces label noise (false negatives), while a long window introduces model staleness. Advanced systems use a sliding window with incremental model updates, where the label for a single click transitions from 'unknown' to 'negative' only after the window expires without a conversion.
Churn-Aware Labeling
A heuristic that distinguishes between a true negative and a delayed positive by analyzing user session patterns. If a user returns to the platform multiple times without converting after a click, the label is more likely a true negative. If the user churns immediately after the click, the label remains highly uncertain, and the instance is down-weighted or held in a pending state.
Multi-Stage Training Pipelines
An architectural pattern where a real-time model is trained on click-through rates with immediate feedback, while a separate delayed model handles post-click conversions. The delayed model uses a time-decayed loss function that reduces the penalty for negative labels on recent clicks, effectively acting as a soft label prior that hardens over time.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us