Site analytics

1. In Trakys, open Projects → Sites → + Connect, pick the project and enter the site's domain. Trakys registers the site with its analytics backend and hands you a script tag.
2. Paste that tag into your site's <head>. It looks like this (your ids differ):

   <script defer src="https://analytics.example/script.js"
           data-website-id="00000000-0000-0000-0000-000000000000"></script>

3. That's all. Visits start counting immediately; the numbers appear on the site's card and in its Analytics tab.

Everyone who can see the project sees its analytics; attaching or detaching the site needs editor-level access.

The script counts what happens in the browser. For things only your server knows — a user registered, an order was paid, an export ran — your backend sends an event with one HTTP call. No SDK; any language that can make a POST works.

1. In the site's Connection tab, press Create ingest key. The key (tik_…) is shown once — store it as a server secret. It is write-only: it can record events for this one site and can do nothing else (no reads, no account access), which is what makes it safe to keep on a production box.
2. Send events from your backend when the thing actually happens:

   POST https://api.trakys.com/v1/ingest/event
   Authorization: Bearer tik_your_key_here
   Content-Type: application/json
   
   {"name": "signup", "url": "/register"}   // url is optional

   curl -X POST https://api.trakys.com/v1/ingest/event \
     -H "Authorization: Bearer tik_your_key_here" \
     -H "Content-Type: application/json" \
     -d '{"name": "signup"}'

3. One name is special: signup becomes the New users tile on the Analytics tab (send it once per completed registration). Every other name — 1–50 chars of letters, digits, spaces, _ - . — shows up in the Events breakdown with its count. The key identifies the site, the name identifies the event: one key covers all your events, and a new event needs no setup anywhere — send a new name and it appears.

Rotate or revoke the key any time on the Connection tab (rotation invalidates the old key immediately). Trakys stores only a hash of the key, so it can never be shown again — losing it just means minting a new one. Events can also be sent from the page itself with the script's own umami.track("signup") — but the backend is the honest source for registrations: it fires exactly once, after the registration really completed, and bots can't inflate it.

The script is a ~2 KB cookieless counter (self-hosted Umami). It stores nothing on the visitor's device — no cookies, no localStorage, no fingerprint identifiers — so under EU ePrivacy rules it does not require a consent banner. The cost of that honesty: a returning visitor counts as a new one, and there are no cross-site profiles. You get aggregate traffic, not people.

One website per project (sub-projects share it). There is no public API for pulling the metrics out of Trakys yet — the numbers live in the Analytics tab. If you need raw exports today, say so: [email protected].