Events

To send a multi-level event, pass a key:value pair. In the interface, key and value are considered nesting levels.

In the AppMetrica interface, the values {"count": 3} and {"count": "3"} are interpreted the same way. However, when exporting data using the Reporting API or Logs API, parameters are exported in the same form as they were sent to the server.

If the same event is passed multiple times with different numeric parameter values, the parameter values are not aggregated in the web interface. Each of them is recorded and calculated separately.

If the server receives events with duplicate parameters but different nesting levels, their values are added together based on duplicate parameters.

For example, the first event has two nesting levels:

{ 
    "param1": "param2"
}

The second one has three nesting levels:

{
    "param1": {
        "param2": "value"
    }
}

In the web interface, these events are displayed as a tree view:

Events are counted using the following algorithm:

1. The event is recorded, along with two of its sublevels. 1 is added to each parameter.
2. 1 is added to the event name and three of its sublevels.

To analyze the chain of events and to compare conversion rates, use the Funnels report. Configure 1 to 10 steps by including one or more events from the app in each step. For multi-level events, use key and value filtering.

Use funnels to compare target event conversions on different versions of the app, assess trends in behavioral scenario conversions, or find out how much of the audience needed a particular app function (number of users and percentage).

This way you will find growth points and implement the best ideas for your users. For more information, see Working with reports.