New format
Heatmaps and maps in Yandex Metrica
In Yandex Metrica the maps section shows where people click, how they scroll, and where they abandon forms. It is an aggregate picture across many visits, not a recording of one session.
Below: what heatmaps, link maps, and form analytics are for. Mode UIs and tab names change — use current Metrica Help. Visitor session recording lives in a separate Session Replay article.
What Metrica maps give you
Numbers say “few leads.” A map shows where people actually tap: the logo instead of the button, a non-clickable image, past a thin mobile link.
Useful on ad landings, product cards, cart, and long pages. For media — on pages with odd bounce or depth.
Basic set:
- click map (heat / density)
- link map
- scroll map
- form analytics
- alongside — Session Replay on problem segments
Click map
A heatmap highlights frequent click zones. Cold areas mean little interaction. Display modes (monochrome, “fog,” link emphasis) depend on the account UI — the point is density and fake clicks.
Don’t chase a pretty picture — chase mismatch with intent: main CTA with no clicks, decorative block with many.
What to watch:
- menu and logo vs action button
- banners people click as links but aren’t
- mobile layout separate from desktop
- pages after a redesign — before/after periods
Link map
Shows transitions via links and buttons: click count and share vs others. Handy to see if people go to cart, catalog, or “nowhere” — footer and socials.
If an important URL barely gets clicks, check visibility, anchor text, and competition from neighbors.
Form analytics
Forms are where conversion breaks: extra fields, phone masks, captcha, validation errors without clear copy. Form analytics shows how far people get and where they drop.
Simplify step by step and measure the “submit” goal. Placeholders help but do not replace proper labels and error messages.
Conditions and limits
Maps build from counter data. You need correct code, enough period, and an understanding of how Metrica normalizes URLs (campaign tags, www, # fragment).
Old guides about Internet Explorer 8 and hard page-pixel limits are history. If the map draws wrong, check Yandex Help and code freshness first — don’t copy 2017 settings.
Before panicking check:
- counter on all needed templates
- maps/forms enabled in settings
- no “native + GTM” conflict
- correct URL and period selected
- CSP/blocker not cutting the script
Session Replay beside, not instead
The map said “few button clicks” — Session Replay shows how people scroll past or miss with a finger. For ad bounce and abandoned forms, a session recording beats one heat picture.
Storage and volume limits changed; don’t rely on “120k per day” from old announcements. Current quotas are in the account and Help.
What to remember
Metrica maps are about action density on the page. Session Replay is about a specific session. With goals they close the loop number → hypothesis → fix → measure.
Don’t expect a heatmap to lift conversion by itself: it is an observation tool.
FAQ
Are the click map and Session Replay the same?
No. A map aggregates clicks and scroll. Session Replay records a specific session. Use both by task.
Do maps need a separate code snippet?
Usually the counter with maps/forms options enabled in settings is enough. If you turned them on later — update the code or the GTM container.
Why is the map empty?
Too little data for the period, a different URL (tags, www, hash), counter missing on the template, blocker/CSP, or the page layout changed a lot vs the collection period.
Will a map raise conversion by itself?
No. It suggests hypotheses: move the CTA, simplify the form, remove fake clicks. Proof is measuring goals.
Can I view maps without Metrica?
Other heatmap services exist. In the RU stack Metrica is often already installed — start there if the counter is correct.
Metrica maps not giving hypotheses?
We’ll unpack clicks, forms, and the Session Replay link — without outdated cabinet screenshots.
Discuss the task
