Metrickle

Watch what happened, without recording what people typed

Click heatmaps and scroll depth show where attention goes on the pages that sell. Session replay shows the sessions behind a drop-off or a low score, with every input masked, all text masked by default, and nothing recorded until the visitor consents. Both come with Growth and up, each plan with its own monthly allowance of recordings.

Heatmap: /quillmere.example · mobile · last 30 days
Clicks18,904
Visitors9,210
Reached half54%
Most-clicked elements on the page, with their share of all clicks
ElementShare of clicks
button "Start free trial"31%
img.hero (not a link)14%
a "Pricing"8%

14% of clicks land on the hero image, which isn’t a link. Fewer than half of mobile visitors scroll far enough to see the pricing table.

Clicks and scrolling, per page and device width

Heatmaps group page views into three width buckets: desktop, tablet and mobile. A layout that works at 1280 pixels can hide the key button on a phone, so each bucket gets its own map.

Clicks are drawn over a masked snapshot of the page, with the most-clicked elements listed alongside. Scroll depth shows the share of page views that reached each point.

  • Text summaries and data tables come with every heatmap, so the findings don’t depend on seeing colour.
  • Sampled if you want: record clicks for every visitor or a share of them.
  • Works in cookieless mode, because heatmaps don’t need to recognise anyone. Replay does, so it stays off in cookieless mode.
Scroll depth by devicequillmere.example · / · last 30 days
Share of page views that scrolled to at least each depth, for each device width
ReachedDesktopTabletMobile
25% of page92%88%81%
50% of page71%63%54%
75% of page44%37%29%
Footer26%22%21%

Mobile loses almost half its visitors before the halfway mark. The pricing table sits at 60% of the page on a phone.

Replay that starts private and stays that way

Session replay is off until you switch it on for an app. When you do, the defaults are the careful ones, and loosening them is a deliberate choice.

  • Opt-in per app under Settings, off by default.
  • Sampled: 10% of sessions by default, adjustable per app.
  • Waits for consent by default: nothing is recorded until your site calls metrickle.consent({ replay: true }).
  • Every input masked, always. All text masked by default, with data-mk-unmask to show regions you know are safe.
  • data-mk-block replaces an element with a placeholder. Canvas elements are not recorded.
  • Erased with the visitor: a GDPR erasure request removes their replays along with their events.
<!-- Replay waits for this by default -->
<script>
  // e.g. from your consent manager
  metrickle.consent({ replay: true });
</script>

<!-- Text shows as dots unless unmasked -->
<nav data-mk-unmask>…</nav>

<!-- Replaced with a placeholder in the recording -->
<div data-mk-block>…</div>

Start from the problem, not from a pile of recordings

Nobody has time to watch every session. Each replay is lined up with the friction signals and survey answers from the same session, so you can start from a rage click, a dead click or a low effort score and open only the sessions that show it.

Filter replays like any other report: by page, device, campaign, accessibility setting or survey answer.

Replays: /checkoutquillmere.example · consented · 10% sample
Recordings of sessions that visited checkout, with pages, friction signals, accessibility setting and survey answer
SessionPagesFrictionSettingSurvey
Desktop · 4m 12s75Keyboard navigationEffort 2 of 7
Mobile · 2m 40s52Large text–
Desktop · 1m 55s40No accessibility settingsEffort 6 of 7

Show only sessions with friction, then open the worst. The timeline marks each rage click, dead click and survey answer, so you can jump straight to the moment.

Heatmaps and session replay are available on the web. Replay code is a separate file that loads only when an app has replay switched on and the session is picked by the sample, so sessions that aren’t recorded never download it.

Switch it on, no new snippet

  1. Install the script tag

    The same tag that tracks pageviews and friction. Heatmaps and replay code loads only when you switch them on.

  2. Switch on per app

    Under Settings → Research, turn on heatmaps and, if you want it, replay. Set the sample rates.

  3. Connect consent

    Call metrickle.consent({ replay: true }) when the visitor agrees. Until then, replay records nothing.

  4. Mark safe regions

    Add data-mk-unmask to navigation and headings you’re happy to see, and data-mk-block to anything that must never appear.

See which release is costing you conversions, and who it broke for

Free to start. One script tag on the web, one SDK on mobile, and no cookie banner in cookieless mode.

Start free