Documentation

Restrictions

Technical limitations

Each advertiser can send a maximum of 20 requests in 10 seconds to the Reports service.

The report queue can contain a maximum of 5 offline reports at once per user.

Generated offline reports are stored for 5 hours, then deleted automatically.

Data availability

Statistics are available for the three years prior to the current month. For example: on 15 August 2016, you can get data starting from 1 August 2013.

The table shows the availability of data in specific fields.

FieldData available
AvgImpressionPosition
[no-highlight[

Average display position of the ad. Calculated using only displays on the first page of Yandex search results. The top position is assigned the number 1.

]no-highlight]
Starting from 01.11.2014
AvgClickPosition
[no-highlight[Average position where the ad was clicked. Calculated using only clicks on the first page of Yandex search results. The top position is assigned the number 1.]no-highlight]
Device
[no-highlight[

The type of device the ad was shown on: DESKTOP, MOBILE or TABLET.

]no-highlight]
Starting from 01.11.2014
Age
[no-highlight[

The user‘s age group: one of the values AGE_0_17, AGE_18_24, AGE_25_34, AGE_35_44, AGE_45 or UNKNOWN.

]no-highlight]
Starting from 22.07.2015
Gender
[no-highlight[

The user‘s gender: GENDER_MALE, GENDER_FEMALE or UNKNOWN.

]no-highlight]
RlAdjustmentId
[no-highlight[

ID of a retargeting list used for applying bid adjustments for website users.

]no-highlight]
Starting from 22.07.2015
MobilePlatform
[no-highlight[

OS type: ANDROID, IOS, OTHER or UNKNOWN.

]no-highlight]
Starting from 15.09.2015
CarrierType
[no-highlight[

The type of connection:

  • CELLULAR — Mobile connection.
  • STATIONARY — Wi-Fi or wired internet access.
  • UNKNOWN — The type couldn‘t be detected.
]no-highlight]
Starting from 16.10.2015
Bounces
[no-highlight[

The number of bounces (according to Yandex.Metrica data).

]no-highlight]
Starting from 10.11.2015
BounceRate
[no-highlight[

The percentage of bounces in the total number of sessions (according to Yandex.Metrica data).

]no-highlight]
Query
[no-highlight[

The search query that triggered the ad.

]no-highlight]
For the past 180 days

Availability of Yandex.Metrica data:

  • AvgPageviews
    [no-highlight[

    The average session depth on the site, meaning the number of pages viewed (according to Yandex.Metrica data).

    ]no-highlight]
    , Bounces
    [no-highlight[

    The number of bounces (according to Yandex.Metrica data).

    ]no-highlight]
    , and BounceRate
    [no-highlight[

    The percentage of bounces in the total number of sessions (according to Yandex.Metrica data).

    ]no-highlight]
    are available if the advertiser's site has a Yandex.Metrica counter installed and the counter number is specified in the CounterIds campaign parameter.
  • Conversions
    [no-highlight[

    The number of conversions (according to Yandex.Metrica data).

    ]no-highlight]
    , ConversionRate
    [no-highlight[

    Conversions as a percent of the total number of sessions (according to Yandex.Metrica data).

    ]no-highlight]
    , andCostPerConversion
    [no-highlight[

    The average cost of reaching a goal (according to Yandex.Metrica data): the ratio of the cost of clicks to the number of conversions.

    ]no-highlight]
    are available if counter goals are also set up (see Goals in the Help for Yandex.Metrica).
  • Revenue
    [no-highlight[

    Revenue (according to Yandex.Metrica data).

    ]no-highlight]
    and GoalsRoi
    [no-highlight[

    The return on investment in advertising, up to two decimal places (according to Yandex.Metrica data):

    ]no-highlight]
    are available if the counter code also transmits the order price.

It can take up to several hours for Yandex.Metrica data to appear in reports because the data transmitted from the counters must be correlated with the ad campaigns.