{"id":192,"count":0,"description":"","link":"https:\/\/tenjin.com\/es\/glossary\/impression-level-revenue-data-ilrd\/","name":"Datos de ingresos por impresi\u00f3n (ILRD)","slug":"impression-level-revenue-data-ilrd","taxonomy":"glossaries","parent":0,"meta":{"status":["1","1"],"order":["0","0"],"glossary_term_description":["
\r\n\r\nDefinition:<\/b>\r\n\r\nImpression-level revenue data (ILRD) is ad revenue data mapped at the level of each individual ad impression. Rather than reporting revenue in aggregated totals, ILRD connects each dollar of ad revenue to the specific impression that generated it, including when it happened, on which device, and under what conditions.<\/span>\r\n\r\nThis data is sent to your mobile measurement partner (MMP) by your ad mediation provider, giving you a granular view of how your ad inventory is actually performing.<\/span>\r\n\r\n<\/div>\r\n\r\n

What is an Impression?<\/strong><\/h2>\r\nAn impression is a single instance of an ad being displayed to a user. Every time an ad appears on a user's screen, that counts as one impression. In a mobile app context, this typically happens when a user opens the app and an ad is served to them.<\/span>\r\n\r\nImpressions are one of the foundational metrics in mobile advertising. They sit at the top of the measurement funnel, before clicks, installs, or any downstream action. Understanding how much revenue individual impressions generate is where ILRD comes in.<\/span>\r\n

Tracked Impressions vs Reported Impressions<\/strong><\/h2>\r\nAs with clicks and installs, impressions can be measured in two ways:<\/span>\r\n\r\n\r\n\r\n\r\n\r\n
Metric<\/b><\/td>\r\nWhat It Measures<\/b><\/td>\r\n<\/tr>\r\n
Reported Impressions<\/b><\/td>\r\nThe total number of impressions as reported by the ad network<\/span><\/td>\r\n<\/tr>\r\n
Tracked Impressions<\/b><\/td>\r\nThe number of impressions independently recorded by Tenjin<\/span><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\nBoth metrics are available in the Tenjin dashboard. Comparing the two gives you a more complete and reliable picture of your impression volume, and helps surface any discrepancies between what the network is reporting and what Tenjin is independently recording.<\/span>\r\n

How ILRD Works<\/strong><\/h2>\r\nILRD is calculated by mapping the revenue generated by each ad to three key pieces of information: the time and date the ad was displayed, the device it was displayed on, and the specific impression event itself.<\/span>\r\n\r\nThis mapping happens at the individual impression level, which is what makes ILRD different from standard aggregated ad revenue reporting. Instead of knowing that your app generated $500 in ad revenue on a given day, ILRD lets you see which specific impressions contributed to that total and how much each one was worth.<\/span>\r\n\r\nThat level of detail opens up a range of analytical possibilities that aggregated revenue data simply cannot support.<\/span>\r\n

Why ILRD Matters<\/strong><\/h2>\r\n

Granular Revenue Attribution<\/strong><\/h4>\r\nILRD connects ad revenue directly to the user, session, and impression that generated it. This means you can attribute revenue not just to a day or a campaign, but to specific users and the moments within their session when they saw an ad.<\/span>\r\n

Better Campaign Optimization<\/strong><\/h4>\r\nWhen you know which impressions are generating the most revenue, you can make more informed decisions about ad placement, format, frequency, and targeting. Optimization based on impression-level data is significantly more precise than optimization based on daily or campaign-level totals.<\/span>\r\n

User-Level LTV Modeling<\/strong><\/h4>\r\nBecause ILRD ties revenue to individual devices and users, it feeds directly into lifetime value calculations. You are not estimating ad revenue contribution to LTV at a population level; you are measuring it at the user level.<\/span>\r\n

ROAS Campaign Support<\/strong><\/h4>\r\nILRD data can be sent back to ad networks via impression-level ad revenue callbacks. Ad networks can then use this signal to run ROAS-focused campaigns that optimize toward users who are likely to generate higher ad revenue, not just users who are likely to install.<\/span>\r\n

ILRD and Ad Revenue Callbacks in Tenjin<\/strong><\/h2>\r\nTenjin supports impression-level ad revenue callbacks, allowing you to pass ILRD data back to your ad networks directly. This creates a feedback loop between your revenue data and your acquisition campaigns, enabling ad networks to find users who are more likely to generate meaningful ad revenue over their lifetime.<\/span>\r\n\r\nFor teams running hybrid monetization models or ad-heavy apps, this connection between ILRD and UA campaign optimization is one of the more powerful levers available.<\/span>\r\n\r\n
\r\n\r\n

Related Terms<\/b><\/h2>\r\n