Events

Note.
The report was updated on April 28, 2022. What's new:
  • You can now use a flexible dimension and metric builder.
  • There are new metrics by event parameter.
  • The filter by session type has been updated. Now, the report shows events from all sessions by default. Previously, background sessions were only counted in metrics for devices.

The report displays statistics on custom events. You can set up sending these events in the app. For more information, see Sending your own events.

  1. The report will help you:
  2. Working with the report
    1. General settings
    2. Configuring a chart with a choice of metrics
    3. Selecting dimensions and metrics
  3. Adding a comment
  4. Disabling events
  5. Data export
  6. Troubleshooting
    1. For iOS devices, events fall into background sessions.

The report will help you:

  • Determine the reach of app features and how popular they are.

  • Compare the behavior of different user groups.

  • Evaluate the frequency of using features within sessions.

Working with the report

General settings

  1. Choose the time period and audience segment. By default, the report shows events for the week grouped by days.

    The event time is the moment when the event is generated on the user's device in the time zone specified in the app settings.

    Note.

    To set the report period, use the drop-down element . The selected time interval can be grouped by hours, days, weeks, or months.

  2. In the report, you can select specific users by using segmentation.
  3. You can set up groupings and metrics in the report.

Configuring a chart with a choice of metrics

The report contains a visual chart with a choice of metrics. You can select no more than three metrics at a time. The selected metrics must have the same units. If a metric is not available in the list (its name is written in gray), it means that it has a different unit.

Selecting dimensions and metrics

The report contains metrics grouped into groupings.

To set up groupings and metrics:

  1. Click the button.
  2. In the window that opens, add the groupings and metrics to base the report on.
  3. Configure the order of metrics and groupings.

    The order of metrics determines the order of columns, the order of groupings determines the nesting of rows in the table.

Groupings

Restriction.

Groupings by parameter are only available for nesting level 1. For more information about nesting levels, see an example of events.

Audience
  • Operating system.
  • OS version.
  • Gender. Determined heuristically using Crypta technology. If the prediction accuracy is insufficient , it takes the Undefined value.
  • Age. Determined heuristically using Crypta technology. Possible values: <18 | 18-24 | 25-34 | 35-44 | 45-54 | ≥55 . If the prediction accuracy is insufficient, it is Undefined.
Geography
  • Continent.
  • Country.
  • District.
  • Region.
  • City.
  • City size.
Event
  • Event. Event name.
  • All parameters, nesting levels 1-5 Outputs all passed event parameters corresponding to the nesting levels.
  • Parameter. Lets you select a specific parameter. You can select a dimension several times with different parameters.

    Restriction.

    Only nesting level 1 parameters are available.

Event date
  • Month.
  • Week.
  • Day.
Application
  • Version.
  • Build number.

Metrics

Restriction.

Metrics by parameter are only available for nesting level 1. For more information about nesting levels, see an example of events.

Events metrics
  • Number of events.
  • Unique parameter values. The number of unique values of the selected event parameter.
  • Sum of parameter values. The sum of values of the selected event parameter. A missing value or parameter in the event during the calculation is interpreted as 0.
  • Average parameter value. The sum of values of the selected event parameter divided by the number of events. A missing value or parameter is interpreted as 0.
  • Median parameter value. The median value of the selected event parameter. A missing value or parameter in the event during the calculation is interpreted as 0.
User metrics
  • Users. The number of users with the event.
  • Events per user. The ratio of the number of events to the total number of app users.
  • % of all users. The percentage of users with the event out of the total number of app users.
  • Unique values per user. The ratio of the number of unique values of the selected event parameter to the number of users with the event. A missing value or parameter in the event during the calculation is interpreted as 0.
  • Sum of values per user. The ratio of the sum of values of the selected event parameter to the number of users with the event. A missing value or parameter in the event during the calculation is interpreted as 0.
Session metrics
  • Sessions with events. The number of sessions in which an event occurred.
  • Events per session. The ratio of the number of events to the number of sessions.
  • Unique values per session. The ratio of the number of unique values of the selected event parameter to the number of sessions with the event. A missing value or parameter in the event during the calculation is interpreted as 0.
  • Sum of values per session. The ratio of the sum of values of the selected event parameter to the number of sessions with events. A missing value or parameter in the event during the calculation is interpreted as 0.

Analysis of event parameters

Analysis of nested event parameters
You can use the report to analyze nested event parameters. Along with the audience metrics, the following aggregations of parameter values are available: their sum, average and median values, and the number of unique values. These metrics are helpful in scenarios such as:
  • Comparing multiple events by the selected parameter.
  • Counting the amount of resources used by players.
The sum and number of unique parameter values are also available in terms of users and sessions.
Grouping by a specific event parameter
You can set up groupings (dimensions) by a specific event parameter in the report. This is helpful for:
  • Filtering the report data.
  • Scenarios such as: comparing multiple events and calculating statistics for all events with the desired parameter.

Adding a comment

To make it easier to navigate reports, you can add comments to events. To do this, follow these steps:
  1. Find the desired event in the Settings → Events section.
    Note. You can go to event settings from the report interface. To do this, click the icon next to the name of the event.
  2. Leave a comment.
  3. Go back to the Events report and refresh the page.

Disabling events

To disable event collecting and remove it from the report, follow these steps:
  1. Find the desired event in the Settings → Events section.
    Note. You can go to event settings from the report interface. To do this, click the icon next to the name of the event.
  2. In the Events collection block, select the Collecting disabled mode.

Data export

You can export data by choosing an item from the Export dropdown list above the chart. The data is exported based on the selected report settings: segmentation, grouping, and time period.

The dropdown list contains the following elements:

  • Export as CSV — Exports the data from the table in the CSV format.
  • Chart as PNG — Exports the chart image in the PNG format.
  • Chart as CSV — Exports the data from the chart in the CSV format.
  • Copy table API request — Displays the query text for exporting data from the table using the Reporting API. You can use this query to build your own dashboard or create automated data export scripts.
    Note. If you are getting the text of the query for the first time, make sure that the browser doesn't block the pop-up authorization window. In the authorization window, allow AppMetrica to access the data.
  • Copy chart API request — Displays the query text for exporting data from the chart using the Reporting API. You can use this query to build your own dashboard or create automated data export scripts.
    Note. If you are getting the text of the query for the first time, make sure that the browser doesn't block the pop-up authorization window. In the authorization window, allow AppMetrica to access the data.

Troubleshooting

  1. For iOS devices, events fall into background sessions.

For iOS devices, events fall into background sessions.

Events that are sent immediately after initializing the library are counted in background sessions. To make sure that events belong to user sessions, initialize the library with the handleActivationAsSessionStart option enabled (Objective-C | Swift).

If you didn't find the answer you were looking for, you can use the feedback form to submit your question. Please describe the problem in as much detail as possible. Attach a screenshot if possible.