Projects organize Analytics data and reports inside a workspace.

Open a project

  1. Select Analytics in the sidebar.
  2. Use the project selector in the Analytics sidebar.
  3. Select the project you want to analyze.

The selected project determines which events, users, reports, dashboards, cohorts, metrics, goals, and alerts you see.

Create or manage projects

  1. Go to Settings > Projects.
  2. Review the projects in the current workspace.
  3. Use the available action to create a project or update an existing one.

Choose project names that clearly identify the product, application, or environment being measured.

Before changing projects

Projects are Analytics containers. They do not divide announcements, feedback boards, roadmaps, or other workspace content. If a report appears empty, confirm that you selected the project receiving the expected event data.

Verify development, staging and production routing

A project name such as “Production” is an organizational label. Creating or selecting that project in the admin interface does not prove that an installed SDK sends events there.

Before accepting an environment setup:

  1. Record the website hostname, workspace Account ID and intended Analytics project for each environment.
  2. Review the installation or widget configuration that supplies the Analytics destination. Do not add an undocumented projectId option to browser SDK initialization.
  3. Use a synthetic user and perform one known configured event on the development site.
  4. Open Live Events in the intended project and confirm that event's identity and time.
  5. Repeat for staging and production with distinguishable synthetic test activity. Check the other projects for unexpected cross-environment data.
  6. Record the verified mapping with your installation documentation. Repeat this check after changing an Account ID, widget or routing configuration.

If you need independent feedback, roadmaps, announcements or teammate access as well as separate analytics data, evaluate the workspace boundary too. Analytics projects alone do not provide that separation.

An empty report does not always mean missing data

Check the current workspace, selected project, date range, filters and event name before changing tracking code. See SDK troubleshooting.

Was this helpful?