Skomi
English
EnglishDeutschFrançaisEspañolPortuguêsItalianoРусский
Get started
Site Analytics Available

How many came, and where from?

Traffic, sources, devices and geography for every site you run, and the business events your site already emits. Built on a column store, so the dashboard stays fast as your history grows.

Create an account All products
What you get

The dashboard, and what is on it.

The numbers that matter first

Page views, unique visitors, bounce rate and event count across the period, with traffic over time and your top sources beside them.

Every site under one account

Register as many domains as you run. Each keeps its own data and its own snippet, and you switch between them from the same dashboard.

Sources, devices and geography

Where the traffic came from, what it browsed on, and which country, region and city it arrived from.

Business events, not just page views

A purchase, a signup, a form submission, recorded with whatever properties you attach and with a value you can sum.

Fast on a long history

Readings go to a column store built for this shape of query, so a year of data answers about as quickly as a week.

Light on your pages

A few kilobytes of plain JavaScript. No framework, no third-party request, no ad-tech.

Events

If you run Tag Manager, you are already sending events.

Anything your site pushes to window.dataLayer with an event key is recorded, including everything Google Tag Manager already sends, and anything passed through gtag(). Google's own gtm.* housekeeping events are skipped.

Pushes that happened before our script loaded are replayed rather than lost, and nested objects are flattened so an ecommerce payload arrives intact.

Already running GTM: nothing to write
window.dataLayer.push({
    event: 'purchase',
    value: 49.90
});
Or call it directly
skomi.track('signup', { plan: 'pro' });
What happens to the data

Measured, not profiled.

The point of this product is to tell you about your site. It is not to build a picture of the person reading it.

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. A visitor is recognised by a one-way hash computed on our server under a key that is never written down and is destroyed nightly.

No cross-site profiles

Visitor identifiers are scoped to your site alone. Nothing is shared between customers, sold on, or passed to an ad network.

Only your domain can report

Each site is registered with its domain, and readings are accepted only from it. Nobody can inject traffic into your numbers.

Worth knowing

What it does not do.

It does not follow people between sites

Which also means it cannot tell you that the visitor who bought today is the one who read a post last month on a different domain. That trade is deliberate and not configurable.

The same person tomorrow is a new visitor

Identity is worked out on our server under a secret replaced every day, so nothing links Tuesday's visit to Wednesday's. Daily figures are unaffected, but unique visitors over a longer window is the sum of daily uniques and reads high, and the retention report cannot work at all. A per-site setting puts a stable id on the device instead, which brings the consent banner back with it and is off unless you switch it on.

It is not an ad platform

There is no audience export, no remarketing pixel and no integration that sends your visitors anywhere else.

Installation
One script tag before </body>, on every page you want counted.
Events
window.dataLayer, gtag() or skomi.track().
Storage
A column store, in the EU.
Ingestion
Accepted only from the domain the site is registered with.
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.

See your first numbers today.

Create an account, register a site, paste one script tag.

Create an account Sign in