> 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/creating-reports/custom-event-metrics.md).

# Custom Event Metrics

By default, AdLibertas will include some important metrics with your reports: impressions, daily active users, revenue earned, and others. Undoubtedly you'll have need for custom or additional metrics on your reports.

When [<mark style="color:blue;">**creating reports**</mark>](/the-platform/user-level-audience-reporting/creating-reports/creating-advanced-user-level-reports.md) you'll be able to choose custom event metrics. Below we walk you through how they work.

![](/files/yALJA231ExKw2sIzHBNo)

### Event Counts

Fairly straight-forward we'll return the total number of events, counted either [<mark style="color:blue;">by day or relative (cohort) day.</mark>](/the-platform/user-level-audience-reporting/report-layout/chart-type-module-absolute-vs.-relative-reports.md) This value will be included as a total, per user, and cumulative value.

Example: `Level_complete`. Counts the number of times the event `level_complete` was fired by the audience defined.

### Event Sum

In some cases, you'll want to sum the values and include the total. For instance, the sum of the `Revenue`field in the `ad_impression`event returns the total ad earnings. This is included automatically, so a better example (as pictured) is including the "sum" of the user\_engagement property which measures [<mark style="color:blue;">the time a user is active in the app.</mark>](/the-platform/user-level-audience-reporting/advanced-reporting-methods/adding-user-time-to-your-reports.md)

### Value Counts

In this case, you're able to include the count of certain parameter values in an event. A great example -- as pictured -- is the count of Applovin impressions in the impression event. But this could easily be the level pack earned from a reward video, or any other parameter value you would like to measure.


---

# 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/creating-reports/custom-event-metrics.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.