> 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/the-platform/user-level-audience-reporting/advanced-reporting-methods/adding-user-time-to-your-reports.md).

# Adding user time to your reports

Firebase has a helpful feature where every event they fire, they’ll include a parameter in the event that will tell you how much time has elapsed since the last event. This parameter is called **engagement\_time\_msec.** When these parameters are added up, this can tell you the total time a user spends in the app. (Details on this event are available[ <mark style="color:blue;">in this article</mark>](https://firebase.blog/posts/2018/12/new-changes-sessions-user-engagement))

I walk through this in a video and with a couple of screenshots.

{% embed url="<https://www.youtube.com/watch?ab_channel=AdamLandis&v=dUXgnpYKMZQ>" %}
1.49s video walk-through of adding user-time to your app
{% endembed %}

When creating a report, under Custom Metrics, you can add “User’s Engagement Time in App” that will add up all the “elapsed time” that’s recorded in engagement\_time\_msec.

![Add the conversion from milliseconds of your choice when building a report](/files/bkMzEVRkx9WeeBukZ9S5)

Then when viewing the report, you’ll see a sum & count feature added. For the total time, you’ll want to view the sum! (The count is actually the number of events, not helpful in this context!)

![Here you can see the average user time (in minutes) for an audience. Cumulative, and total time will also be included.](/files/L2jo2HhM8aFTsZPCWv0x)


---

# 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/the-platform/user-level-audience-reporting/advanced-reporting-methods/adding-user-time-to-your-reports.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.