AppMetrica Blog

AppMetrica Logs API - get the max from your data

15 April 2016, 13:29

We are happy to announce public release of Logs API – an API which allows you to pull out raw, non-agregated data of your applications from AppMetrica. Logs API opens new ways for AppMetrica integration with your in-house analytics or BI and smart data re-usage (e.g. retargeting).

Currently Logs API supports export for:

Tracking URL clicks;
Installations;
Application events.

Such information is invaluable when creating customised reports and precisely defining a target audience for an ad campaign. Let’s look at both cases in more detail.

Creating customised reports

As an example of a customised report, let's say you want to get a summary report for all versions of a service. If the service exists in web and mobile versions, Logs API can be used to calculate the overall retention rate across the service as a whole, using your own analytics system.

In our example, the retention indicator will be calculated from registered users' actions with all versions of the service: a person's login is used to connect his or her use of mobile and web versions.

How to do it:

  1. Integrate AppMetrica into the application; in the SDK, set the login and registration events so that users will be linked with their advertising identifier (GAID, IDFA) upon logging in or registering.
  2. Use Logs API to upload data about login and registration events.
  3. Upload analogous information from the web version of the service.
  4. Merge web and mobile versions' charts of data by login.
  5. Calculate overall retention for the product as a whole using in-house analytics.

Defining a target audience for an ad campaign

Non-aggregated data about installations can be used to define an audience for an ad campaign, setting targeting on the advertising identifiers of specific users. This is particularly useful for retargeting and cross-promotion.

For example, here’s what’s required to organise an ad campaign for application A among users who have already installed application B:

  1. Create an advertising campaign for application A (for example, in myTarget) aimed at users of application B.
  2. Upload data about all installations of application B over a relevant timeframe (for example, a year).
  3. Add the identifiers that you receive into the settings of application A’s ad campaign.

Data can be uploaded not only by manually sending a request to the API, but also via user-friendly graphical interface. To do this, go to the Applications section, select what you need from the list on the left, and click Data export at the bottom of the left column.

0 comments
Subcribe to notifications about comments