Three questions about the same visit, and the same ones for your app.
Every Skomi product reads the site you have already registered, through the script that is already on it. The page underneath is the same for all three; what changes is what Skomi draws on top of it. Analytics also reads a mobile or desktop app, through an SDK rather than a script. That is its own product, on its own page.
How many came, and where from?
Which pages pull their weight, where visitors came from, and what they did next. Built on a column store, so the dashboard stays fast as your history grows.
Traffic, sources, devices and geography
Page views, unique visitors, bounce rate and time on site, per site and per page.
Your dataLayer, already understood
Anything pushed to window.dataLayer with an event key is recorded, including everything Google Tag Manager already sends.
Nothing is stored on the visitor's device
No cookie and no identifier are written in a visitor's browser, so most sites need no consent banner.
What did they actually do?
Analytics counts the visit. Behavior shows you the visit: where people clicked, how far they read, where they gave up, and what the page looked like while it happened.
Click, scroll and attention maps
Painted over a real snapshot of the page, with desktop, tablet and mobile kept apart.
Session recordings you can replay
A reconstruction of the page and what the visitor did to it, not a video file.
Live view
See who is on the site right now, and watch a session as it happens.
What did they want to tell you?
Numbers and recordings show you that something is wrong. Feedback is how a visitor tells you what, attached to the exact thing on the page they were looking at.
A rating, a comment, or both
One question, asked in the corner of the page. Either half on its own is enough to submit.
Pinned to an element, not just a URL
The visitor points at what they mean. You get back the element, not a page address to guess from.
An inbox, not a spreadsheet
Every submission arrives as new, and moves to triaged, resolved or spam.
How is the app doing, release by release?
An app is not a site with rounded corners: there is no URL to read, no referrer, and a version people may never update. So the questions change: which release is this, is it crashing, do people come back. The answers come from an SDK rather than a script tag.
Screens, sessions and people
The three totals every other question hangs off, broken down by release, platform, device and country.
Crash-free rate, next to the numbers
Sessions and visitors that saw no fatal error, per release, so a bad build shows up beside the usage it ruined rather than in a separate tool.
Eight SDKs, one wire format
Android, iOS, Kotlin Multiplatform, Flutter, React Native, Unity, .NET and Electron. All speak the same frozen contract.
One question leads to the next.
- A page loses people
- Analytics shows the drop. The Behavior heatmap shows how far down anyone got before leaving, and a recording shows what they tried first.
- A button gets rage-clicked
- Behavior flags the burst. Feedback tells you the visitor thought it was broken, pinned to that button.
- A campaign underperforms
- Analytics attributes the traffic. Behavior shows whether the landing page was read or skimmed.
Start with one. Add the others when they earn it.
Every product is a per-site switch. Nothing new to install.