> For the complete documentation index, see [llms.txt](https://docs.adlibertas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adlibertas.com/data-integrations/custom-integrations/impression-level-tracking-with-admob-mediation.md).

# Impression level tracking with Admob Mediation

Firebase and Admob have an automatic integration, but the revenue amount [is not exported to BigQuery.](https://stackoverflow.com/questions/51202704/can-i-get-ad-impression-and-ad-click-from-bigquery-linked-with-firebase-anal#comment91341767_51202704) Not being able to export this information means you won’t be able to export or utilize impression-level data outside of the Firebase dashboard. This article outlines our recommended way to implement impression-level tracking with Admob mediation.

You can gather the impression value by using the Admob paid event handler.

* [iOS](https://developers.google.com/admob/ios/early-access/paid-events) documentation
* [Android](https://developers.google.com/admob/android/early-access/paid-events) documentation
* [Unity](https://developers.google.com/admob/unity/paid-events) documentation

Implementing the paid event handler will allow you to capture the earned value of the ad impression and relay via Firebase analytics method [logEvent](https://firebase.google.com/docs/analytics/events).

This will be similar to how other mediation platforms recommend tracking impression-level ad revenue at the app level (e.g [ironSource ](https://docs.adlibertas.com/data-integrations/ad-impression-level-revenue-connections/ironsource-ad-revenue-measurement-integration)and [MAX](https://docs.adlibertas.com/data-integrations/ad-impression-level-revenue-connections/collecting-mopub-impression-level-data-as-a-firebase-event)). Be sure you include as much detail from the impression as possible (bare minimum should be value and currency).

We recommend you call the impression event something other than ad\_impression since it would generate duplicate counts in the Firebase dashboard.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adlibertas.com/data-integrations/custom-integrations/impression-level-tracking-with-admob-mediation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.