Who it is for

Skomi for SaaS products

A SaaS company measures two things that are usually bought separately: a marketing site that has to convert, and a product that has to keep people. Skomi covers both from one script and one bill, as far as page-level measurement goes, which is the part worth reading carefully below.

What you get

The marketing site and the signed-in product on the same script. Trial pages, docs, pricing and the app itself report into one account, so the path from a blog post to an activated account is one funnel rather than two tools stitched by hand.

No consent banner on the marketing site. Nothing is stored on the visitor's device, so the page that has to convert is not the page asking permission first. For a product whose own pitch involves trust, that is worth more than the analytics.

Funnels, and cohorts with a caveat. Journeys show where a signup or onboarding flow loses people, step by step, and that works whatever your identity setting. Retention cohorts group by when a visitor was first seen ever rather than first seen in the period. Read the next section before relying on them, because what "the same visitor next week" means depends on a setting most people leave alone.

Heatmaps and recordings inside the product. The onboarding screen where everyone stalls is usually not the screen you would have guessed. Inputs are always masked in recordings, which matters more here than on a marketing page.

A feedback widget you can put on one screen. Ask on the page where the doubt is, rather than emailing a survey a week later.

Reports without handing out logins. A shared dashboard is a link with no account behind it, which is how a founder shows numbers to an investor or a board without adding seats.

What Skomi will not do for you

Skomi does not work out who anybody is. Identity is derived on the server from a rotating daily salt, so somebody who returns next week is counted as a new visitor, not the same one. The exception is one you choose: switch on Identify signed-in users in the site's Analytics settings, and your product can call skomi.identify() with its own id for a signed-in person. That id follows the person across days and devices, stores nothing on their device, and lets the dashboard, the visits list and journeys be filtered to what that one customer did. It is off until you switch it on, it refuses anything that looks like an email address, and telling your users about it is yours to do. It adds a filter, not an account model: there is no company dimension, no list of your users and no traits attached to them. A per-site identity.mode of device is a separate choice. It puts a stable id back on the device and makes retention mean what you expect, at the cost of storing something on the device, which brings the consent question back with it. That is a real trade and it is yours to make.

No feature flags, no experiments, no A/B testing. Product-analytics suites bundle these and Skomi has none of them. If your roadmap depends on shipping variants and reading the difference, you will be running something else alongside.

No CRM, no emails, no user records. Skomi measures and reports. Beyond an id you choose to send, it holds nothing about your customers, so it cannot segment by plan, trigger a lifecycle email, or tell you which accounts went quiet.

No SSO for your own team. People you work with sign in with their own email and password, or with Google, Microsoft or GitHub, and access is granted per site or app rather than by directory group.

Recording a signed-in product should be a decision, not a default. Inputs are masked and you can sample rather than capture everything, but you are still filming screens with customer data on them. Make it deliberately, tell people in your privacy policy, and decide how much page text a replay may show.

Setting it up the way you work

One script on both, marketing site and app. They can be one site in Skomi or two: one if you want the whole funnel in a single view, two if the teams looking at them are different. The snippet guide covers either.

Tag every campaign the same way so the acquisition side is readable. There is a convention worth adopting before the first campaign rather than after the tenth.

Make signup a goal, and the first real action a second goal. The gap between them is activation, and it is the number most SaaS dashboards are missing.

Turn recordings on at a sample rate, not for everyone. A sample is enough to see where onboarding stalls, and nobody needs every session in the product filmed.

Know how long recordings are kept. Retention comes from your plan, not from a per-site setting, and recordings are kept for less time than analytics on every plan. The pricing page shows the window for each.

One script, or one SDK. The same reports either way.

Create an account, register a site, and switch on what you need.