Project settings

Project settings has four tabs. This page is the map — each tab links out to the page that covers it in depth.

One thing applies across all of them: your tracking configuration is read-time. Conversion, first value, tracked events and aliases are stored as settings and applied when queries run, never written into the event store. The page says so directly: Changes apply to all past and future events — no re-install needed.

Tracking tab

Where you define what success means.

• Conversion — an event name or a page path. Page conversions are a prefix match.
• First value — the activation event. Requires a conversion first.
• Extra tracked events — up to 12 additional events, comma- or newline-separated.
• Detected events — names your site is sending that aren’t mapped yet, with one-click assignment.
• Active aliases — incoming name → configured name, up to 24 per project.

Every event input is backed by a dropdown of names your site actually sent in the last 30 days, with counts.

Full detail: conversions and activation and event aliases.

Install tab

Everything you need to get the tracker onto your site, plus key management.

The snippet generator

A platform dropdown with 12 platforms generates the right snippet for your stack, with a copy button and a hint about where to place it. See installation for the per-platform walkthroughs.

The AI agent prompt

A collapsible section: Prefer an AI agent? Copy a ready-made prompt. It produces a ready-to-paste prompt for Claude, Cursor or whatever you use, already containing your public key, your framework, and your configured events. Paste it into your coding agent and let it do the install.

Public key

Shown in plain text with a copy button.

The public key is meant to be public. It ships in your page source — anyone who views source can read it, and that’s fine. It identifies your project; it doesn’t grant access to your data.

Regenerate it only if someone is abusing it to send fake events into your project. Use the ↻ Regenerate button.

Regenerating:

• revokes the current keys immediately,
• mints a new public + secret pair,
• closes any open live streams.

The old key stops working immediately, so update your snippet right after — until you do, your site is sending events with a dead key.

Secret key

The secret key panel appears only once: right after project creation, or right after a rotation.

A new secret key was generated. Copy it now — it is shown only once.

Only a hash is stored, so it can never be shown again. If you lose it, your only option is to regenerate — which invalidates the public key too. Put it in your password manager or your server’s environment the moment you see it. See security.

Data tab

Three lists that shape how events are interpreted.

• Domains — an origin allowlist. Events from an origin not on this list are still accepted, but marked unattributed with their referrer, UTM and attribution fields stripped. Limit: 64.
• Ignored referrers — hosts that shouldn’t count as a traffic source, like payment and auth providers. Limit: 64.
• Event labels — friendly display names, e.g. account_created → Signup.

The domains list is the one that bites people. If you serve your app from more than one host, add them all. Full detail: domains and referrers.

General tab

Language

English or Español.

This is a per-user setting, not a per-project one — even though it lives on the project settings page. Changing it changes the interface language for you, everywhere, across all your projects. It doesn’t affect your teammates, and it doesn’t change anything about the project’s data.

Worth knowing, because the placement suggests otherwise.

Danger zone — delete project

Deleting a project is a soft delete:

• the project disappears from the app,
• its live streams close,
• your analytics data is retained,
• the project’s internal ordinal is never reused.

The confirmation reads: Delete this project? Analytics data is retained but the project is removed.

So this removes the project from your workspace rather than destroying your history. If you need data actually erased rather than detached, see security.

Project limits

Three projects covers a product, its marketing site, and a side thing. If you need more, see account and billing.

A sensible order to do this in

If you’re setting up a new project, work left to right:

1. Install — get the snippet on your site and confirm events arrive.
2. Data — add every domain you serve from, before you accumulate unattributed traffic you can’t recover.
3. Tracking — define your conversion, then first value once you know which events exist.
4. General — set your language; ignore the danger zone.

Step 2 before step 3 is deliberate. Attribution stripped at collection time is gone for good, while tracking config can be changed retroactively any time. Fix the thing that can’t be fixed later, first.

Where to go next

• Installation — platform-by-platform setup
• Conversions and activation — the Tracking tab in depth
• Domains and referrers — the Data tab in depth
• Going live — the checklist before you trust the numbers
• Security — keys, data retention and access