> 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/native-integrations/firebase-analytics/auto-tracked-analytics.md).

# Auto Tracked Analytics

The events Twinr records for you, with no setup.

Once [Firebase Analytics](/native-integrations/firebase-analytics.md) is set up, Twinr records these events on its own. There is nothing to configure — they start arriving as soon as your build is live.

| Event                                   | What it tells you                                                            |
| --------------------------------------- | ---------------------------------------------------------------------------- |
| **App install**                         | How many people installed your app.                                          |
| **Android & iOS specific installs**     | The same, split by platform.                                                 |
| **App open**                            | How often people come back — your clearest engagement signal.                |
| **Android & iOS OS version variations** | Which OS versions your customers are on.                                     |
| **App version variations**              | Which versions of your app are in use.                                       |
| **Device models**                       | Which phones your customers carry.                                           |
| **Bottom tabs**                         | A view event per tab, named after the tab — `Account_viewed`, `Shop_viewed`. |

## Reading them

**App open** against **App install** is the number worth watching. Installs tell you marketing is working; opens tell you the app is. A large gap between them means people are installing and not returning.

**Bottom tabs** shows which parts of your app people actually use. A tab nobody views is either in the wrong place or not worth its slot — see [Rearrange Screen](/screens/rearrange-screen.md).

**Device models** and **OS version variations** are what you check before dropping support for anything, and when a bug only appears for some customers.

{% hint style="info" %}
Tab events are named from your screen titles, so renaming a screen changes the event name. Firebase treats the new name as a separate event, and your history stays under the old one.
{% endhint %}

## Where they appear

In the Firebase console under **Analytics → Events**. Anything ending `_viewed` is one of these; everything else is yours from [Custom Analytics](/native-integrations/firebase-analytics/custom-analytics.md).

See [How to check Analytics in Firebase?](/native-integrations/firebase-analytics/how-to-check-analytics-in-firebase.md).