Skip to content
Peekbird

Recordings, Live, Analytics and Heatmaps

Recordings, Analytics and heatmaps are built from the same visits, and recordings and Analytics share their filters. Here's how each number is counted, and what the tools around them do.

Visits

A visit (a session, in the dashboard) is one browser's time on your site. It ends 30 minutes after the last page load: clicks, scrolling and moving between screens of a single-page app don't extend it. A visitor who reads one page for 40 minutes and then opens another starts a new visit.

  • Page views are full page loads. For single-page apps, see Speed, CSP and single-page apps.
  • Each visit is one tracked visit for your plan, whatever it does (see Plans and usage).
  • QA visits are marked QA in the recordings list, and left out of Analytics, heatmaps and your plan's tracked visits.
  • Crawlers, known by their browser's user agent, are kept apart: only their page views are kept, they're never recorded, and Analytics shows them only with Bot traffic switched on.

Analytics

Analytics → Overview shows the last 30 days unless you pick another time frame, compared with the same length of time before it. Up to 2 days are drawn hour by hour, longer ones day by day, in your browser's time zone.

NumberWhat it counts
VisitorsBrowsers that visited. Someone on a phone and a laptop counts twice.
SessionsVisits with at least one page view that started in the time frame.
Page viewsFull page loads.
Pages per visitPage views divided by sessions.
Bounce rateThe share of visits with one page view. In A/B tests, the Bounce rate goal counts the same way, for the visit each visitor entered the test in.
Time on siteThe average visit, from its first page load to the last report the visitor's browser sent, when they left or hid the page.
ConversionThe share of visits with an order: an event sent with revenue. Experiment goals don't count here; they're in each experiment's results.
RevenueOrder values added up as sent, and shown in the currency your orders use most. Orders in other currencies are added in unconverted.
Time on pageIn the Pages list: the average active time of a view (below).
ScrolledIn the Pages list: how far down views got, on average.
  • Time on page, scrolling, speed, heatmap clicks and every signal below come from Collect analytics in your site's Site settings. With it off, recordings still play, without them.
  • Time, scrolling, clicks and speed are sent when the visitor leaves the page or switches tabs, so a visit in progress shows them later.
  • Pages are told apart by host and path: letter case, "www.", a trailing slash and the query string don't count. The 50 most viewed pages are listed, and the top 20 of each other list.
  • A visit's traffic source comes from its first page, in this order. Paid: a UTM medium such as cpc, paid or display, or an ad's click ID (gclid, fbclid, msclkid…). Email: a UTM medium of email or newsletter, or a link opened in webmail (Gmail, Outlook, Yahoo Mail) or the Gmail app. Social: a UTM medium of social, or a link from a social network. Search: a search engine's results (not its company's other sites, like signing in with Google). Other sites: any other site, or UTM tags with no site before. Direct: neither a site before nor tags.

What the signals mean

Each of these is a filter for recordings and Analytics. Rage clicks, dead clicks, frequent zooms and errors are also marked on a recording's timeline.

SignalCounted when
Active timeThe time between the visitor's mouse moves, scrolls, clicks, taps and key presses, up to 5 seconds each, while the tab is in view. Reading counts; walking away doesn't.
Scroll depthHow far down the bottom of the window got, as a share of the page's height. A visit's is its deepest page's.
Rage clicks3 clicks within 0.7 seconds, within 30 pixels of each other. Not on controls made for repeated clicks: sliders and seek bars, number steppers, video and audio players, and anything your site marks with data-peekbird-repeat (carousel arrows, say).
Dead clicksA click on something that isn't a link, button, form field or other control, after which, for 1 second, nothing on the page changes, the address stays the same and no text is selected.
Frequent zoomsZooming in past 115% three times within a minute, zooming back out between.
Excessive scrollingChanging scroll direction 4 times on one page, each time after scrolling at least a quarter of the window.
Quick backGoing to a page, then back to the one before within 10 seconds.
JavaScript errorsUncaught JavaScript errors and unhandled promise rejections. Pictures or scripts that fail to load don't count.
Entered textTyping into a form field.
Refreshed a pageReloading a page.
Clicked textThe text of links and buttons clicked: up to 100 characters, and 20 different ones per page view. Never from masked parts of a page, or with Mask all text on.

Page speed

Peekbird measures three Web Vitals on every page view, rated with Google's thresholds. In between, a page needs improvement.

MetricWhat it measuresGoodPoor
Loading · LCPWhen the largest text or picture showed, counting only what showed before the visitor first clicked, tapped or pressed a key.up to 2.5 sover 4 s
Responsiveness · INPThe slowest response to a click, tap or key press, measured as Google’s web-vitals library measures it. A page nobody interacted with has none.up to 200 msover 500 ms
Stability · CLSHow much the layout moved in its worst burst of shifts (less than 1 second apart, within 5 seconds). Shifts right after the visitor's own input don't count.up to 0.1over 0.25
  • Each page view keeps its worst values. Page speed in Analytics shows the 75th percentile (three in four page views did at least that well) and the share in each rating.
  • A recording's Performance (worst page), and the LCP, INP and CLS filters, rate the visit's worst page.
  • Browsers report what they can measure: in practice Chrome, Edge and other Chromium browsers report all three, and Firefox reports LCP. Page views with nothing measured are left out.

Finding recordings

Recordings → Sessions lists recorded visits, newest first. Search by email, name, user ID, order ID, or visitor or session ID; pick a time frame up to how long recordings are kept; and add filters:

CategoryFilters
PagesVisited page, Entry page, Exit page, Visited pages in order, Pages viewed
BehaviorSession length, Active time, Clicks, Scroll depth, Rage clicks, Dead clicks, Frequent zooms, JavaScript errors, Quick back, Excessive scrolling, Entered text, Refreshed a page, Clicked text, Clicked element
Goals and ordersCompleted goal, Placed an order, Revenue, Order ID, Tracked event, Funnel
ExperimentsSaw variation, Feature flag
VisitorIdentified, Email, User ID, Name, Custom attribute, New or returning, Visitor ID
Traffic sourceChannel, Referring site, UTM source, UTM medium, UTM campaign, UTM term, UTM content
TechnologyDevice, Device brand, Device model, Browser, Browser version, Operating system, OS version, Screen width
LocationCountry, Region, City
PerformanceLargest contentful paint (LCP), Interaction to next paint (INP), Cumulative layout shift (CLS)
TimeDay of week, Hour of day
  • Filters combine with AND. AND / OR splits them into groups, each matching all or any of its filters: up to 10 groups of 20.
  • Page rules starting with / match the path on any of your domains; the query string counts when you include a "?". Regular expressions ignore letter case, and can't use lookarounds or backreferences.
  • The Segments menu saves the filters under a name, for everyone in the workspace. Saving and deleting one takes an editor or owner.
  • The same filters and segments work on Analytics → Overview, and the page's address keeps them, to bookmark or send.

Watching a recording

Which visits are recorded is on Privacy controls, and how close replays come to what visitors saw on Replays that match your site. The player plays at 1× to 8×, with Skip idle on, and takes these keys, here and on shared links:

  • Space plays or pauses.
  • ← → go 5 seconds back or forward, and Shift + ← → to the previous or next page of the visit.
  • Home and End go to the start or the end, once the timeline is selected.

The Timeline tab lists pages, orders, goals, events and signals; choosing one plays from 2 seconds before it, or from the start of a page. Goals show only for experiments the visitor was in, from when they entered. Details has who the visitor is, where they came from, their device and All sessions of this visitor.

Sharing and downloading

Share or download on a recording shares all of it or a part: drag across the bar, or click a page. A link is for Members, who sign in to watch, or Anyone with it, which only editors and owners can make. It works for 1, 7, 14 or 30 days, and never longer than the recording is kept.

  • Whoever opens a link sees the site's name, the date, the device and browser, and the part shared with its pages, rage and dead clicks, zooms and errors. Never who the visitor is, or their orders and events.
  • Recording settings lists the links that still work, with their views, to Turn off. Deleting a visitor's data turns off links to their recordings.
  • Download HTML file saves the player and the recording, or the part, in one file that plays in any browser, without an account or a connection. Pictures and fonts load from your site when it can be reached, so offline they're missing.

On Growth and Scale, recordings and shared links show Peekbird's copies of your pages' files; on Free, they load them from your site (see Replays that match your site). Live, heatmaps and downloaded files always load them from your site.

Live

Recordings → Live lists everyone active on your site in the last 2 minutes (up to 100), and updates by itself. Recorded visits have Watch live: playback runs 10–15 seconds behind the visitor, since their browser sends what they do every few seconds. Go back with 10 s or the bar, and return with LIVE. Once the visitor leaves, open the visit as a recording for its timeline and sharing.

Heatmaps

Analytics → Heatmaps lists your most viewed pages in the time frame, the last 30 days unless you pick another. Open one to see Clicks (all, rage or dead) or Scrolling, on Desktop, Tablet or Phone.

  • Each click is placed on the element clicked, so it lands on it even where the layout differs a little. Clicks made with the keyboard aren't placed, and a page view places up to 500.
  • Scrolling shows the share of views that got at least each tenth of the way down.
  • A page is its address without the query string: /shoes?color=red and /shoes?color=blue share one heatmap.
  • Heatmaps are drawn on a recording of the page as it loaded, before the visitor's first click, tap or typing: the latest one kept from that kind of device, or else from another. So a page needs at least one recording kept. Your own QA recordings, such as visits with ?peekbird_record=1, are used only when no visitor's recording from that kind of device is.

Heatmaps take the same filters as Recordings and Analytics, so a heatmap can show only some visits. The Visits menu beside the page has the usual ones:

  • Visits that bought, or didn't buy: where buyers click, against everyone else.
  • Visits that completed a goal, one of yours.
  • Saw a variation of an experiment: each variation's own heatmap, to see how people use the new version.
  • Feature flag, on or off: where visits with a new feature click, against the rest.

A filtered heatmap counts the visits that started in the time frame and match the filters.

Area counts the clicks in a part of the page: drag a box over it, such as a menu or a banner, to see how many of the page's clicks land there. Scroll the page while the tool is on, and drag again to move the box.

See what your visitors see.

Start free in a few minutes: one snippet, every feature. Move to a bigger plan when you need more tracked visits.