Integrating AdMob revenue data into Google Analytics and leveraging it in Firebase A/B testing, Google Ads, and BigQuery offers powerful capabilities. This integration transforms monetization data into actionable insights, enabling you to optimize user acquisition, enhance in-app experiences, and ultimately drive sustainable revenue growth.
Integrate AdMob revenue data in Google Analytics for actionable insights
- Analyze user actions that contribute to the ad revenue generated by your app.
- Tailor ad experiences to maximize revenue from high-value users.
- Run experiments using Firebase A/B Testing to find what features drive improvements in your app ad revenue, or personalize ad experiences using Remote Config personalization.
- Create user audiences and tailor user experiences using Firebase Remote Config based on ad revenue levels.
Leverage AdMob revenue data in Google Ads for holistic ROAS analysis
Understand Return on Ad Spend (ROAS) performance and enable smarter user acquisition (UA) strategies in Google Ads by targeting users likely to generate higher ad revenue. For example, tROAS (target Return On Ad Spend) campaigns in Google Ads can leverage this data to maximize the return on ad spend.
- Enhance audience segmentation and targeting based on ad engagement and revenue metrics.
- Improve monetization with reporting of ad revenue with other app performance metrics.
To enable AdMob revenue data to flow to Google Ads, you will need to link your Google Analytics (GA4) property to Google Ads.
How AdMob revenue data shows up in AdMob Reporting vs. other sources
Revenue Types
Revenue type |
Definition |
---|---|
AdMob Network and bidding revenue |
Revenue from the AdMob Network and your bidding ad sources. |
Third-party AdMob Mediated Ad Revenue |
Revenue from AdMob Third-party-mediated sources. |
Impression-level Ad Revenue (iLAR) |
Revenue for each individual ad impression displayed to a user, available for publishers who enabled iLAR. |
Comprehensive view of AdMob ad revenue in different Google platforms
AdMob Network and bidding revenue |
Third-party AdMob Mediated Ad Revenue |
Impression-level Ad Revenue (iLAR) |
|
---|---|---|---|
AdMob Reporting |
Finalized AdMob revenue for validated clicks and impressions. |
Finalized Third-party AdMob Mediated Revenue after data processing and reconciliation. |
Not applicable. |
Google Analytics Reporting |
Finalized AdMob revenue for validated clicks and impressions. AdMob sends real-time revenue data to Google Analytics. However, this data will be adjusted within 72 hours to reflect finalized revenue, ensuring alignment with AdMob Reporting.
|
If impression-level ad revenue (iLAR) is not enabled, estimated revenue will be sent in real time. Within 72 hours, the estimated revenue will be adjusted to reflect the finalized Third-party AdMob Mediated Revenue after data processing and reconciliation. |
If impression-level ad revenue (iLAR) is enabled, this will be sent in real-time. |
Google Ads (by linking Google Analytics to Google Ads) |
Finalized AdMob revenue for validated clicks and impressions. |
If impression-level ad revenue (iLAR) is not enabled, estimated revenue will be sent in real time. |
If impression-level ad revenue (iLAR) is enabled, this will be sent in real-time. |
Firebase A/B Testing |
Finalized AdMob revenue for validated clicks and impressions. AdMob sends real-time revenue data to Google Analytics. However, this data will be adjusted within 72 hours to reflect finalized revenue, ensuring alignment with AdMob Reporting.
|
If impression-level ad revenue (iLAR) is not enabled, estimated revenue will be sent in real time. Within 72 hours, the estimated revenue will be adjusted to reflect the finalized Third-party AdMob Mediated Revenue after data processing and reconciliation. |
If impression-level ad revenue (iLAR) is enabled, this will be sent in real-time. |
Notes:
- Revenue reported for Meta Audience Network will always be estimated. Consider the revenue reported directly by Meta Audience Network as the definitive figures for Meta earnings.
- Third-party-mediated estimated revenue will be determined using the following formula:
Ad unit 1 est. earnings = Earnings reported by optimized third-party ad network / (Total number of impressions for all ad units that use the same mapping information) * Number of impressions for Ad unit 1
Understanding discrepancies in ad revenue between Google Platforms
Discrepancies in ad revenue data between AdMob Reporting and other Google platforms is expected due to differences in data collection, processing, and attribution methods, especially when data is coming from third-party ad networks.
AdMob Reporting should be considered the definitive source for your revenue figures, as it accurately reflects all valid clicks and impressions.
- Revenue reported in Google Analytics and Firebase A/B Testing should be largely consistent with AdMob reporting. However, do note that Google Analytics reporting might reflect some adjustments within 72 hours due to data refreshes and the exclusion of invalid activity during that time.
- You may see discrepancies between AdMob Reporting and other Google Platforms as AdMob Reporting will only reflect revenue figures for valid clicks and impressions to align with your payouts.
To minimize discrepancies and gain a comprehensive view of your ad revenue, it is essential to:
- Avoid data duplication: If you are using a third-party mediation platform, impression-level revenue data can be used to log Google Analytics
ad_impression
events. Do not link AdMob to Firebase to avoid duplicating revenue data. - Ensure Proper Linking: Verify that your AdMob app is correctly linked to your Firebase app, and your Firebase project is linked to your GA4 property.
- Validate Data Collection: Use GA4's DebugView and other debugging tools to confirm that
ad_impression
events are firing correctly and with the appropriate parameters. - Align Settings: Harmonize time zones and, where possible, attribution models between platforms for consistent reporting.
- Understand Platform-Specific Reporting: Recognize that each platform has a unique purpose and reporting methodology. AdMob focuses on ad performance, while GA4 offers a holistic view of user behavior across all channels, including ad interactions.