Skomi is one platform for the things you need to know about the sites and apps you already run. Rather than a separate vendor, login and bill for each question, every capability is a product you switch on for the site or app that needs it.
Four products, two kinds of thing measured
Three of them measure a site, and answer questions that get progressively more specific:
- Site Analytics: how many people came, and where from.
- Site Behavior: what they actually did once they arrived.
- Site Feedback: what they wanted to tell you.
The fourth measures software people install:
- App Analytics: which screens they reached, whether they came back, and whether the release crashed.
One script for a site, one SDK for an app
The three site products read the same site through the same snippet. Switching one on changes what that script does; there is nothing new to paste and no second vendor to introduce.
An app has no page to put a snippet on, so it is measured with an SDK instead. There is one for each of eight platforms, and the format they send is frozen, so a build published today keeps reporting for as long as people run it.
One allowance, not four subscriptions
Everything on the account draws on a single balance. A page view is the unit the rest is priced against, so sampling recordings or adding an app is a decision about one number rather than a second bill to approve.
The pricing page has the figures, including a free plan that carries every product rather than a cut-down version of one.
Where it runs
Customer data is stored in the EU.
Where to start
If you are setting a site up for the first time, start with installing the snippet. For an app, see measuring an app.
If you are still deciding, what people use Skomi for is organised by the job rather than by the product, and each of those pages says where Skomi stops being the right tool as well as where it is.