What happens when conversion postbacks are delayed? How can bidding still optimize?
Delayed postbacks occur when users take hours or days to complete actions after seeing an ad. If bidding engines assume all conversions occur immediately, they prematurely penalize slow-converting inventory. Bidding engines solve this by modeling historical conversion arrival curves, discounting recent cohorts and attributing mature values over time.
Detailed Explanation
In mobile gaming, e-commerce, and financial apps, user decision-making takes time. A user might download a banking app on Monday, complete identity verification on Tuesday, and make their first deposit on Thursday.
A naive bidding engine that only looks at 24-hour performance will conclude that Monday's impressions were unprofitable and slash bids across high-converting publisher sources.
To optimize accurately under latency, modern bidding algorithms maintain conversion lag distribution functions. The engine estimates what percentage of total conversions have arrived based on elapsed hours (e.g., 40% on Day 1, 75% on Day 3, 100% on Day 7) and scales current conversion probabilities accordingly.
The time elapsed between the initial ad impression or click and the recorded conversion event.
Cohort Maturation Scaling
An ad placement delivered 10,000 impressions on Monday ($50 spend). By Tuesday morning, only 1 conversion has been reported ($50 CPA vs $25 target).
Arrival curve modeling prevents false-negative optimization stops on high-value supply.
What to Do Next
- 1Map your app's median time-to-convert (TTC) from click to purchase across 30 days of historical MMP data.
- 2Align your optimization lookback window to at least 2× your median time-to-convert.
- 3Avoid evaluating intra-day CPA metrics on cohorts younger than 48 hours.
Related Questions
Break-Even Bid Calculator
Factor in conversion lag and customer lifetime value when calculating allowable bid ceilings.