Creating and configuring a project

A project represents one tracked website or app inside a workspace. Each project gets its own API key, retention policy, and tracking mode, and all analytics (sessions, heatmaps, funnels) are scoped to it — the switcher in the top bar is how you move between projects.

What you set when creating a project

• Website URL and project type — used to verify installation and origin-match incoming sessions.
• Framework, so the setup wizard shows you the right snippet. Pick the closest match; you can always use the plain HTML snippet.
• Tracking mode — defaults to consent-required, meaning the SDK waits for a consent signal before recording replay.
• Replay retention — how many days raw session recordings are kept before automatic deletion. Your plan sets the ceiling.

One project or several?

Use separate projects when the sites have different audiences or different domains — marketing site vs. logged-in app, for example. Use one project when it's the same product and you want funnels to follow a visitor across the whole journey, since funnels, journeys, and visitor profiles never cross a project boundary.