Projects & Domains
Create a project, set the domains it accepts events from, and give it a readable slug.
A project is one tracked property: a website, a product, or an environment. Each project has its own keys, its own settings, and its own data.
Create a Project
Open the project switcher and choose Add New Project. You provide a Project Name and at least one entry under Tracking Domains.
The domains are not optional. A project with no domains would accept events from any origin, so the dialog blocks submission with Add at least one domain to continue until you add one.
The dialog shows a running count of root domains used against your plan's limit. Subdomains of a domain
you already listed do not count again, so app.example.com and www.example.com together consume one
root domain, not two. If adding a domain would exceed the limit, the dialog says so and links to
Settings → Billing.
Tracking Domains
Manage them later at Project Settings → Domains. The list is the allowlist of origins that may send events with this project's public key. Requests from anywhere else are rejected, which is what stops someone from copying your snippet onto another site and polluting your data.
Add every origin you actually serve from, including staging and preview environments if you want data from them.
Projects created before domains became mandatory can still have an empty list. Those accept events from any origin, and Project Settings → General shows a warning saying so, with a link to fix it. If you see that warning, add your domains.
Name and Slug
Project Settings → General holds the Project Details.
Project Name is the display name, and you can change it whenever you like.
Slug is the readable identifier used in URLs, in place of a long project id. It accepts lowercase letters, numbers, and hyphens. Slugs are unique within your organization, so if the one you want is taken you will get an error on the field and can pick another.
Keys
Each project has its own public and secret key, under Project Settings → Integrations. Keys are never shared between projects, so an environment separated into its own project is genuinely isolated. See API Authentication.