New format
YAN revenue metrics in Yandex Metrica
If your site is in the Yandex Advertising Network (YAN) as a publisher, Metrica can show more than visits: ad revenue, block performance, and cuts by source and device.
Below: what the reports mean for a publisher and the connection logic. Menu names and metric sets change — check current Yandex Help. This piece is about publisher revenue analytics, not buying ads in Yandex Direct.
Why link YAN + Metrica
The YAN partner account shows money. Metrica shows behavior. Together you see which traffic feeds revenue and which pages are empty on ads despite a good audience.
That makes it easier to decide where to strengthen units, where not to overload with ads, and which sources bring valuable vs empty views.
Typical cuts:
- revenue and ad views
- pages and sections
- devices and geo
- traffic sources / channels
- ad density vs interest in content
Which metrics make sense
Actual impressions and revenue are the base. Without them you can’t talk about monetization.
CPM / renders / ad requests help judge the technical yield of units.
ARPU and similar per-user metrics help compare sections and seasonality.
Check the exact field glossary in Help: Yandex renamed and expanded reports since 2018.
How connection works (step logic)
A working Metrica counter on the site.
A site in the YAN partner interface with consent to send data to Metrica.
Align counter/site IDs per the instructions.
Set access rights to financial reports (don’t show revenue to every editor).
Confirm data appears in reports after stats accumulate — not in a minute.
How to read for decisions
Pages with high traffic and low revenue — hypothesis: few/poor units or strong adblock on the segment.
High revenue with falling depth — maybe ad overload; balance UX and money.
Check season and layout changes: a new template often breaks unit rendering.
What to remember
YAN revenue in Metrica is publisher reports, not a Direct advertiser account.
You need a YAN partnership, matched counters, and current Help for connection.
Read revenue next to audience so monetization doesn’t kill UX.
FAQ
Who needs YAN revenue metrics?
Site/app owners who show YAN ads and want income next to audience data in Metrica.
Is this the same as advertiser spend in Direct?
No. Here it’s publisher income, not an advertiser account with CPC/CPA campaigns.
Do I need to be a YAN partner?
Yes: without network participation and consent to share data, revenue reports won’t appear.
What should I look at first?
Revenue and ad views/renders by pages and sources: where audience exists but monetization is weak — and the reverse.
Why CPM and ARPU?
CPM is yield per impressions; ARPU is per user. They help compare sections and periods, not only absolute money.
Do ad blockers matter?
Yes: some impressions never happen. Reports may include fields about ad unavailability — see current Help fields.
Is connecting paid?
Metrica reports for partners are usually free. YAN partnership terms are separate.
Do the counters have to match?
Yes: the ID in the partner interface and on the site/in Metrica must match Yandex’s instructions, or data won’t join.
YAN ads live, but revenue doesn’t line up with Metrica visits?
We’ll match counters and publisher reports — income next to audience, without killing UX.
Discuss the task
