> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/integrations/firebase-analytics/how-to-check-analytics-in-firebase.md).

# How to check Analytics in Firebase?

* Once all the setup is done, you can check the anlaytics under the firebase analytics dashboard.
* Events will start getting captured right away but the data can reflect in 24 hrs.
* We are not tracking the clicks in preview app. So if you want to test, you can test via installing live app from Playstore and Appstore or install apk file for Android and install iOS app from testflight.

1. Go to <https://console.firebase.google.com/> and login to your account.
2. Click Analytics from left side menu.<br>

   <figure><img src="/files/tlvYgd4fCUsEk6SJRLbH" alt=""><figcaption></figcaption></figure>
3. Go to Events and check all the details by clicking on that event.

   * All the events with "tabname\_viewed" are auto tracked event by Twinr.
   * All the other events are created by you in custom anaytics.<br>

   <figure><img src="/files/FT6KnteLWsCUznNgLsEC" alt=""><figcaption></figcaption></figure>


---

# 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://help.twinr.dev/integrations/firebase-analytics/how-to-check-analytics-in-firebase.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.