Site Analytics Available
How many? Traffic, sources, devices and geography for every site you run, plus the business events your site already pushes to a dataLayer.
Site Analytics in detail →Site Behavior Available
What did they actually do?
Analytics counts the visit. Behavior shows it: where people clicked, how far they read, where they gave up, and what the page looked like while it happened. Plus a live view of who is on the site right now.
What you get
Three views of the same thing.
A heatmap tells you where. A recording tells you why. Live view tells you that it is happening now.
Heatmaps
Where people click, how far down the page they get, and which parts they actually spend time looking at. Desktop, tablet and mobile are kept as separate maps, because they are separate layouts.
Session recordings
Replay a real visit: the page, the scrolling, the clicks, the moments of hesitation. Sessions are listed with what happened in them, so you can go to the ones worth watching.
Live view
Who is on the site right now, what page they are on, and how long they have been there. You can also watch a session as it happens rather than waiting for it to end.
How it works
A recording is not a video.
Skomi captures the structure of the page and the things that changed it, then rebuilds the page to replay it. That is why a recording is small enough to be practical, and why the text in it stays text.
Heatmaps work the same way round. Heat is aggregated against the elements on your page rather than against pixel coordinates, so a map still means something after a responsive reflow. The background you see it on is a real captured page, never a screenshot taken by a robot that never logged in.
- Clicks
- Recorded against the element, plus where in it, so the map survives a layout change.
- Rage clicks
- Three or more clicks in the same small area within a second. The whole burst is flagged, not just the last one.
- Dead clicks
- A click that changed nothing on the page and went nowhere.
- Scroll depth
- How far down each page view got, aggregated into the fold line.
- Attention
- Time each tenth of the page spent on screen.
What is captured
Recording is the most invasive thing you can put on a site.
One of these is not a setting: what a visitor types is never captured, in any mode. What the page shows them is captured by default, and how much of it stays legible is a decision you make per site. A page of order details and a page of marketing copy are not the same risk.
What people type is never captured
Inputs, textareas and selects are excluded in every mode. This is not a setting, and there is no way to switch it on.
How much page text is captured is your call
Out of the box, in the mode called Relaxed, the words on your pages are captured, so a replay is legible and you can see what somebody hesitated over. Balanced masks anything that looks like personal data: numbers, and anything resembling an email address. Strict masks every word. A site whose pages show accounts, orders or anything medical wants one of those two, and nobody here can make that call for you.
Masked content never leaves the browser
Masking happens at capture, not at playback. What is hidden was never uploaded, so it cannot be revealed by a setting later.
You can exclude anything by hand
Mark an element to mask it, unmask it, or drop it and everything inside it from the recording entirely.
Recording starts when you switch the product on
There is no separate opt-in step, so it works from the moment you enable it. If your site asks visitors for consent first, tell Skomi about their answer and recording will follow it, in both directions, during the visit.
skomi.consent('recording', true);
Worth knowing
What it does not do.
It will not show you what someone typed
Which rules it out as a way to debug a form by reading the values. Watch what the visitor did with the field instead. That is usually the more useful answer anyway.
A heatmap needs a recording to sit on
The background is a real captured page, matched to the device you are mapping. A page with clicks but no recording on that device cannot be drawn yet, and the app says so rather than guessing.
Live view is for watching, not for intervening
There is no chat, no co-browsing and no way to take control. You see the session; you do not touch it.
- Installation
- None. It runs from the script you already have.
- Masking
- Inputs never captured, in any mode. Page text captured by default; masking is per site.
- Retention
- Set per site, and short by default.
- Replay
- Recordings play back on a separate origin, isolated from the rest of your account.
The rest of the platform
Same script, same account.
Every product reads the site you have already registered. Switching one on is a toggle, not another installation.
Site Feedback Available
What did they say? Let visitors rate a page and say what is wrong, pinned to the exact element they were looking at and triaged in one inbox.
Site Feedback in detail →App Analytics Available
How is the app doing? Sessions, screens and retention for an app people install, with crash-free rates and errors alongside them, so a bad release is visible in the same place as a quiet one.
App Analytics in detail →Watch the visit you have only been counting.
Switch Behavior on for a site and the next visitor is a recording.