# About Analytiics

Analytiics is web and product analytics for teams that would rather review a
tracking plan than administer one. The plan lives in your repository as a file
called `analytics.yaml`; everything else — the typed SDK your code calls, the
dashboard sections, the CI check that catches drift — is derived from it.

## Why the repo

Every analytics setup is correct on the day it ships. The interesting question
is what happens over the following six months, as features land and nobody
remembers to add the events. The usual answer is that the dashboard slowly
stops describing the product, and nobody notices until somebody asks a question
it can no longer answer.

Putting the plan in the repository changes who is responsible for that. A new
event is a diff with a comment thread. A renamed event breaks the build instead
of silently emptying a chart. A feature that ships with no instrumentation shows
up in a drift check rather than in a quarterly audit. None of that is possible
when the plan lives in someone else's admin panel, because the plan and the code
are then two things that have to be kept in agreement by hand.

## What we build

- **A browser tracker** — under 2 KB gzipped, cookieless, served first-party.
  Pageviews, SPA navigation, outbound clicks, custom events, identity.
- **An event collector** at `in.analytiics.co`, which validates, enriches with
  geography and device from request headers, drops bot traffic, and writes to a
  columnar store.
- **A manifest and a code generator** that turn `analytics.yaml` into a typed
  SDK, so event names, property names and enum values are all checked at build
  time.
- **A CLI and an agent skill**, so setting analytics up is a command and a
  prompt rather than an afternoon.
- **Dashboards** at `/p/<project>`, publishable in whole or in part on a
  single URL.

## How we handle data

Anonymous visitors get a daily rotating hash. The tracker sets no cookies and
uses tab-scoped sessionStorage for sessions and, when requested, a site's user id. Revenue is
only ever accepted over an authenticated server-side path, so nobody can post
fake sales into your dashboard from a browser console. The full detail is on the
[privacy page](/privacy).

## Where it is

The product is in public beta and running in production today — the dashboard
at [/p/thiings](/p/thiings) is real traffic on a real site, fed by the same
ingestion path a customer's events would take. The source is public at
[github.com/charlieclark/analytiics](https://github.com/charlieclark/analytiics).

## Talk to us

Write to [hello@analytiics.co](mailto:hello@analytiics.co), or open an issue on the
repository. More ways to reach us are on the [contact page](/contact).