ILRD Is Not a Setting. It’s the Foundation of Your Monetization Stack.
ILRD isn’t just a setting. It’s the base of your monetization stack. If you’re still looking at yesterday’s aggregate revenue and calling it “performance,” you’re flying blind. In modern user acquisition (UA), seeing $27,000 in daily revenue doesn’t tell you whether your campaigns are profitable, whether your ad frequency test is working, or whether your cheapest advertising channel is quietly hurting lifetime value (LTV). Impression-Level Revenue Data (ILRD), which measures revenue earned per individual ad impression, changes that. It connects every ad impression to a real user, specific device, and the original traffic source, turning return on ad spend (ROAS) optimization, analyzing groups of users over time (cohort analysis), and combining ads with in-app purchases (hybrid monetization) into measurable systems instead of relying on educated guesses. But IRLD isn’t just about turning it on. Waterfall floor math, bidding mechanics, alternative stores like RuStore, and Meta's platform restrictions can introduce discrepancies that quietly corrupt your signal and your UA decisions. In the full article, we break down what’s normal, what’s fixable, and what’s catastrophic. We also show you how to verify your IRLD before every build. If you’re using target Return on Ad Spend (tROAS) in 2026, this isn’t optional reading.
