# Ad Impression-Level Revenue Connections

- [AppLovin Max User Revenue API](https://docs.adlibertas.com/data-integrations/ad-impression-level-revenue-connections/applovin-max-user-revenue-api.md)
- [ironSource Ad Revenue Measurement Integration](https://docs.adlibertas.com/data-integrations/ad-impression-level-revenue-connections/ironsource-ad-revenue-measurement-integration.md): IronSource makes it easy to collect impression-level data. While they do provide a post-back app event, it’s much easier for AdLibertas to collect the impression-level data from the ironSource API.
- [Impression level tracking with Admob Mediation](https://docs.adlibertas.com/data-integrations/ad-impression-level-revenue-connections/impression-level-tracking-with-admob-mediation.md)
- [Collecting MoPub Impression-Level Data as a Firebase Event](https://docs.adlibertas.com/data-integrations/ad-impression-level-revenue-connections/collecting-mopub-impression-level-data-as-a-firebase-event.md): Today MoPub doesn’t offer an API providing impression-level events. The information is only allowed as a post-back to the app.


---

# Agent Instructions: 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:

```
GET https://docs.adlibertas.com/data-integrations/ad-impression-level-revenue-connections.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.