# Audience Reporting

- [Why doesn't my daily active user count match Firebase?](https://docs.adlibertas.com/faqs/audience-reporting/why-doesnt-my-daily-active-user-count-match-firebase.md)
- [Why doesn’t my retention rate match?](https://docs.adlibertas.com/faqs/audience-reporting/why-doesnt-my-retention-rate-match.md)
- [Why aren't my install rates matching?](https://docs.adlibertas.com/faqs/audience-reporting/why-arent-my-install-rates-matching.md)
- [Why doesn't my relative user count match retention?](https://docs.adlibertas.com/faqs/audience-reporting/why-doesnt-my-relative-user-count-match-retention.md)
- [What is the probability projected LTV becomes actual LTV?](https://docs.adlibertas.com/faqs/audience-reporting/what-is-the-probability-projected-ltv-becomes-actual-ltv.md): The answer is it really depends.
- [Why doesn’t Firebase and AdLibertas revenue match?](https://docs.adlibertas.com/faqs/audience-reporting/why-doesnt-firebase-and-adlibertas-revenue-match.md): There are a few possibilities why revenue doesn’t match your Firebase console:


---

# 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/faqs/audience-reporting.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.