Impression-level ad revenue data (ILRD) is the money attached to one ad impression. Instead of a daily total from an ad network, the app or mediation layer reports a value, a currency, and often a precision flag at the moment the impression pays.
Mobile games and other ad-funded apps need that grain because install counts do not show which players earned ad revenue. The figure is still an input to a report. It is not, by itself, profit.
How does it work?
Three common sources expose the same idea with different field names.
- Google Mobile Ads SDK. An
OnPaidEventListenerreceives anAdValue.getValueMicros()is the revenue in micros of the currency fromgetCurrencyCode().getPrecisionType()is one ofUNKNOWN,ESTIMATED,PUBLISHER_PROVIDED, orPRECISE. - Firebase. With the Google Analytics link turned on, the SDK can log an
ad_impressionevent. Parameters includead_platform,ad_source,ad_format,ad_unit_name,currency, andvalue. Herevalueis in currency units, not micros. - Mediation. A mediation SDK reports the winning network and a revenue amount for the impression it served. The network name and the precision rules are the mediation platform's, and they do not always match AdMob's enum.
Summing impressions into a day is straightforward only when every row uses one currency and you have decided what to do with ESTIMATED and UNKNOWN. Mixing micros and currency units multiplies revenue by a million.
A concrete example
A rewarded video pays. The Android callback returns getValueMicros(), getCurrencyCode() of USD, getPrecisionType() of ESTIMATED, and the ad unit name rewarded_end_level.
The app records an event named ad_impression with value set to those micros divided by 1,000,000, plus currency USD, precision ESTIMATED, ad_format rewarded, and ad_unit_name rewarded_end_level. If Firebase also logs its automatic ad_impression for the same show, the two events need one shared ID or the daily sum counts the impression twice. See event deduplication.
The divide-by-1,000,000 step is the unit difference between valueMicros and the Firebase value parameter. It is not a statement about what a rewarded video should earn.
A PRECISE impression can sit in a settled-revenue column. An ESTIMATED impression can sit in a separate column so a finance report does not treat a forecast as cash.
What are the limits?
ILRD is advertising revenue, not in-app purchase revenue. A player can produce both on the same day. Adding them without a label double-counts nothing, but it does hide which source moved.
Precision is not quality of the player. PUBLISHER_PROVIDED means you supplied the number. UNKNOWN means the SDK could not classify it. Dropping unknown rows changes the total. So does keeping them and labeling them as exact.
Currency conversion, refunds of ad spend, and mediation waterfalls that report the same impression from both the mediator and the network will inflate a naive sum. Compare the impression count with the mediator's own total before you send the sum to an ad platform as a conversion value.
A server-side forward of ad_impression does not bypass App Tracking Transparency and does not reveal the Identifier for Advertisers. The revenue event can travel without a cross-app identifier.
How Hardal handles it
If the app or your backend sends the ad revenue event, Hardal can store it with your other first-party events and forward the value you allow to an ad platform. Send value, currency, and the precision flag together so an estimated amount is not optimized as settled revenue. When the SDK and the server both emit the impression, use one event ID.
Hardal does not replace the mediation platform's payout report. Reconcile the summed events with that report before you treat the pipeline as the books. For why ad revenue belongs next to install optimization, read why an MMP needs revenue signals, how ILRD and IAP combine into one ROAS signal, and the gaming solution.
Related terms: Events, Event deduplication, Predicted lifetime value, Receipt validation
Frequently asked questions
What does ILRD stand for?
ILRD means impression-level ad revenue data. It is the revenue figure for one ad impression, usually with a currency and a flag that says whether the figure is exact, estimated, or provided by the publisher.
What are the AdMob AdValue precision types?
The Google Mobile Ads SDK reports AdValue.PrecisionType as UNKNOWN, ESTIMATED, PUBLISHER_PROVIDED, or PRECISE. PRECISE is a settled figure for that impression. ESTIMATED is not. Keep them apart when you sum revenue.
Is the Firebase ad_impression value in micros?
No. The automatic Firebase ad_impression event records value in currency units, with a currency code. The raw AdMob paid-event callback reports valueMicros instead. Divide micros by 1,000,000 before you compare the two.
Does sending ad revenue server-side bypass ATT?
No. A server hop does not grant access to the advertising identifier or permission to track people across apps. Send the revenue event your app is allowed to send, and do not attach an identifier ATT did not allow.