Projects & write keys

A project is where events land: one stream of data with its own write key, dashboards, reports, and context. One project per product or site is typical; staging and production are usually separate projects so test noise never pollutes real numbers.

Everything you see in the console is scoped to the projects you can access: queries, dashboards, reports, and the assistant’s answers are all bounded to them server-side.

Write keys are public identifiers

A write key (nrw_…) identifies your project when events are sent. It ships in your page source, so it is not a secret, and it doesn’t need to be:

• It can only write events into your project. It can never read data, list events, or touch any other project.
• Ingestion is rate-limited and metered per account.

This is the same model every browser analytics tool uses. You can view and copy the key any time from the project’s page.

Rotation and revocation

From the project page:

• Rotate issues a new key while the old one keeps working for a 24-hour grace window, so you can deploy the new key at your own pace; nothing drops mid-rotation.
• Revoke is for compromise: the current key (and any grace key) stops being accepted within a minute, and a replacement is issued immediately. Update your clients with the new key to resume sending.

Key changes propagate to event intake within about 60 seconds.

Archiving

Archiving a project is a soft delete: its write key stops accepting events within a minute and the project disappears from the console. Use it for retired products or abandoned experiments.

Personal vs team projects

Projects start personal, owned by you alone. Creating a team from a project moves it (with its data, dashboards, and reports) into a shared workspace; see Teams & roles. That move is one-way.