# Analytiics

> Web and product analytics where the tracking plan lives in your git repository. A
> coding agent instruments the codebase; one manifest — analytics.yaml — generates a
> typed SDK, the dashboard sections and a CI drift check, so what you measure cannot
> quietly diverge from what you ship. Cookieless, with public dashboards.

## Set up this project

When the user says "Set up https://analytiics.co/ in this project", follow the
complete [agent setup workflow](https://www.analytiics.co/docs/agents) before running commands.
It covers domain discovery, authentication, the installed skill in any harness,
instrumentation, manifest sync, secret handling and real-event verification.
The URL in that prompt names this service, not the app's tracking domain.
Continue after CLI setup; do not hand the user a second prompt to give an agent.
Report any authentication, deployment or verification blocker explicitly.

## When to use Analytiics

Reach for Analytiics when the task is one of these:

- Adding analytics to a codebase from an agent or a terminal: `npx analytiics start`
  signs in, creates the project, issues a write key, scaffolds `analytics.yaml`, and
  installs the `instrument` agent skill.
- Giving a team a tracking plan that is reviewed as a diff and enforced in CI, rather
  than configured in a vendor UI the repository knows nothing about.
- Answering "which events does this product send?" — `analytics.yaml` is the complete
  declared surface, and anything missing from it fails typecheck at the call site.
- Attributing revenue to the marketing channel that earned it: `identify()` in the
  browser, then the sale from your backend via `@analytiics/sdk-node`.
- Shipping web analytics with no cookie banner: anonymous ids are a daily rotating
  anonymous hash and tab-scoped session storage.
- Publishing numbers on a URL: a dashboard at `/p/<project>` can be made public whole
  or widget by widget.

Do not reach for it when the job needs session replay, heatmaps, funnels drawn in a
UI, or a cross-site identity graph — Analytiics does none of those, deliberately.

## How to call it

```sh
npx analytiics start        # set the project up end to end
npx analytiics validate     # check analytics.yaml
npx analytiics codegen      # regenerate the typed SDK
```

```html
<script defer src="https://in.analytiics.co/script.js" data-site="your-project"></script>
```

- `POST https://in.analytiics.co/v1/events` — public browser collector, no auth, never accepts revenue.
- `POST https://in.analytiics.co/v1/server/events` — `Authorization: Bearer sk_live_…`, accepts revenue.
- `GET https://www.analytiics.co/api/realtime?project=<slug>` — the public live count.

Every page below also answers `Accept: text/markdown` with Markdown, and is reachable
at the same path with a `.md` suffix.

## Machine-readable descriptions

The whole HTTP API — both hosts, every endpoint, typed request and response schemas,
unique operation ids, and the error codes each one can return — is published as an
OpenAPI 3.1 document. Read that instead of this file if you are generating a client or
a set of tool definitions.

- [OpenAPI 3.1 (JSON)](https://www.analytiics.co/openapi.json): The whole HTTP API: both hosts, typed request and response schemas, a unique operation id on every operation, and the error codes each one can return.
- [OpenAPI 3.1 (YAML)](https://www.analytiics.co/openapi.yaml): The same document as /openapi.json, in YAML.
- [API catalog](https://www.analytiics.co/.well-known/api-catalog): RFC 9727 catalog: which APIs this site publishes and where each one describes itself.
- [llms.txt](https://www.analytiics.co/llms.txt): This site as a single file, with guidance on when to reach for the product.
- [Sitemap](https://www.analytiics.co/sitemap.xml): Every indexable URL, with a last-modified date.
- [robots.txt](https://www.analytiics.co/robots.txt): What crawlers may fetch, and where the sitemap is.
- [Analytiics HTTP API reference](https://www.analytiics.co/docs/api): the same surface in prose, with the reasoning.

Every failure on either host answers with the same JSON body: a stable `code`, a
`message`, a `hint` saying what to change or wait for, and a `docs` URL. Switch on
`code` — it maps to exactly one status and will not be reworded.

## Product

- [Analytiics — Analytics, set up by your agent.](https://www.analytiics.co/): Analytics set up by your coding agent: custom date ranges, shareable filters, funnels, People and journeys, Stripe revenue, snapshot cards and live stats pills.
- [Pricing — Analytiics](https://www.analytiics.co/pricing): The four plans, what each covers, how the soft cap behaves, and how upgrading works from a terminal.

## Documentation

- [Analytiics developer documentation](https://www.analytiics.co/docs): Index of every Analytiics developer resource, with one line on what each covers.
- [Analytiics quickstart — install the tracker](https://www.analytiics.co/docs/quickstart): Script tag, npm module, and the CLI path — from nothing to a first pageview.
- [Analytiics HTTP API reference](https://www.analytiics.co/docs/api): Every public Analytiics endpoint — collector, server events, projects, keys, realtime — plus the JSON error format and the OpenAPI 3.1 document that describes all of it.
- [The analytics.yaml manifest — Analytiics](https://www.analytiics.co/docs/manifest): The manifest format, field by field, and what codegen, the dashboard and the drift check each do with it.
- [The Analytiics CLI](https://www.analytiics.co/docs/cli): Every CLI command, what it writes, how device-flow sign-in works, and the CI drift check.
- [Connect Stripe revenue to Analytiics](https://www.analytiics.co/docs/stripe): Connect Stripe, import revenue and credit the channel that brought each customer.
- [The Analytiics Node SDK — server events and revenue](https://www.analytiics.co/docs/sdk): Server-side events with @analytiics/sdk-node, and how revenue attribution actually joins up.
- [Analytiics for AI agents — when to use it and how to call it](https://www.analytiics.co/docs/agents): When an agent should reach for Analytiics, when it should not, and the exact calls to make.
- [People and journeys — Analytiics](https://www.analytiics.co/docs/journeys): Find an opaque user id, inspect sessions, and follow activity before a payment.
- [Analytiics live stats pill — embed your visitor count](https://www.analytiics.co/docs/live-stats-pill): Embed a Diiverge-style live visitor pill: public settings, React/CSS example, polling, privacy and verification.

## Company

- [About Analytiics — analytics your coding agent sets up](https://www.analytiics.co/about): What Analytiics is, who builds it, and the thinking behind a manifest-first tracking plan.
- [Contact Analytiics](https://www.analytiics.co/contact): Email, issue tracker, and what to send where — support, security, privacy and press.
- [Privacy at Analytiics](https://www.analytiics.co/privacy): Cookieless by design: what is collected, what is refused, retention, sub-processors, and how to make a request.
- [Terms of service — Analytiics](https://www.analytiics.co/terms): The service agreement: plans, billing, caps, acceptable use, data, liability, and how to end it.

## Optional

- [Source repository](https://github.com/charlieclark/analytiics): the whole product, including the tracker, collector, manifest and CLI.
- [Live public dashboard](https://www.analytiics.co/p/thiings): real traffic on a real site, updating as you read it.
- Contact: hello@analytiics.co. `https://www.analytiics.co/signin` is a login wall and holds no content; nothing else here needs an account.