Skip to content

Projects

Use projects to keep separate products apart, and manage each project's settings, token and access.

A project holds the data and setup for one product: its events, people, recordings, dashboards, insights, feature flags and settings. Nothing is shared between projects, so a dashboard in one project never shows another project's data.

Every project belongs to an organization, and the organization's members and roles apply to all its projects.

One project or several?

Use one project for everything that shares the same customers. If your marketing website and your app serve the same people, track both in the same project so you can follow a visitor from first visit to sign-up and beyond.

Create a separate project for a product that shares nothing with the others, or to keep test data out of your real reports.

Create a project

  1. Open the project switcher (the project's name in the navigation).
  2. Choose New project.
  3. Enter a name and select Create project.

Project names must be unique within the organization. The new project opens straight away, ready for its own snippet.

Organization admins and owners can always create projects. Members can create them only if an admin has turned on Members can create new projects under Settings → Organization → Members.

An organization can have one project unless its plan includes Projects; plans that include it allow more, up to the number set on the plan.

Project settings

Open Settings at the bottom of the left-hand navigation. The page opens on the settings of the project you are in.

  • General → Project token & ID: the token your snippet and libraries use to send events, and the project's ID for the API. The token is meant to sit in your website's code, so it isn't a secret.
  • General → SDK setup: the snippet to install on your site.
  • Customization → Project details: rename the project.
  • Customization → Date & time: the time zone used for dates in reports.
  • Customization → Filter out internal and test users: the filters to leave your own team's activity out of reports.
  • Privacy: whether visitors' IP addresses are stored with their events.
  • Project secret API keys: keys that let your own systems call a select set of API endpoints for this project.
  • Access control: who can see and edit this project. See Access control.

Further sections hold the settings for each product, such as Session replay, Autocapture and Feature flags.

Switch between projects

Use the project switcher in the navigation to move to another project. Everything you see, including settings, then belongs to the project you chose.

Move a project to another organization

You can move a project to a different organization you belong to, keeping all its data. You need to be an admin or owner of both organizations.

  1. In the project, open Settings → Project → Danger zone.
  2. Under Move project, select the organization to move it to.
  3. Select the Move button (it shows the project's name) and confirm.

Delete a project

Organization admins and owners can delete a project under Settings → Project → Danger zone.

Deleting a project permanently removes it and all its data, including events, and can't be undone. To confirm, type the project's name. For a project with a lot of data, the clean-up can take several hours; you'll get an email when it is finished.

Can't find what you need? Contact support