Creating Your First Project

A project represents one website or app you want to test. Each project gets its own snippet key and its own experiments. Metrics can belong to one project, or be shared across every project in your organization. Most teams have one project per website.

For "Acme Corp", you might have Main Website for acmecorp.com, Marketing Blog for blog.acmecorp.com, and App for app.acmecorp.com. Each is its own project because they have separate code, audiences, and goals.

Create it

The project screen appears right after you finish setting up your organization. You can also add more projects later from the Projects page in the left sidebar. While you work inside a project, its name shows next to your organization's name at the top of the page, so you always know which one you are in. There's no limit on how many projects you can create, on any plan, including Free. See Billing for what each plan does include.

The Create a New Project dialog: Web Experimentation selected as the project type, followed by Project Name, Description, and Website URL fields, a question asking whether this is an online store with Yes/No options, and a Create Project button. — The New Project dialog: choose a type, name it, add your site URL, and say whether you sell online.

Choose Web Experimentation to build A/B tests on your site.
Paste your site's full URL, including https://.
Answer whether you sell products online. You can change this later.
Click Create Project to finish.

Name the project

Something you'll recognise at a glance: "Main Website", "US Storefront", "Marketing Landing Pages".

Enter the website URL

Paste the full URL including https://, e.g. https://www.acmecorp.com. A vs B uses this to check snippet installation and generate the right snippet tag.

Say whether it is an online store

Answer Yes, we sell products online and this project gets a Commerce menu in the sidebar for product catalogs, recommendations, and revenue tracking. Answer No, not right now and the menu stays out of your way. A marketing site or a blog does not need it. You can change your answer at any time from Project Settings › General › Online store.

Create the project

Click Create Project ›. A vs B generates a unique snippet key and takes you straight to the install screen, the last step of setup. The environment defaults to Production (changeable later in Project Settings).

Install, or skip it for now

The install screen shows your two-tag snippet (or, for a feature-flag project, your SDK key) with a live status that confirms itself the moment your site's first visit, or your app's first check-in, arrives, no refresh needed. A fold-out panel there offers one ready-made prompt for Claude Code, Cursor, or any AI coding assistant, filled in with your project's real details, so the assistant can install it for you instead. Nothing here is required: click Skip for now and finish it later from Settings › Snippet.

Land on the dashboard

Your new dashboard carries a short Getting started checklist: five steps, each linking straight to the page that does it, each ticking itself off from your own data rather than from a box you check. It disappears when you finish, and you can hide it whenever you like.

A new web project starts with one experiment already in the list, named Demo experiment: Homepage headline. A vs B creates it so your first dashboard has something you can open and poke at. It is a draft pointed at example.com: it is not running, it is not on your site, and it collects nothing. Delete it whenever you like, exactly like any other experiment, and it will not come back for you. On a project you share, a teammate opening it for the first time may still get their own copy, which they can delete just as easily.

Every project has its own snippet key, which tells the snippet which project it belongs to. Never reuse a key across different websites; create a separate project for each one.

If the page seems to hang and you try again, you will not end up with two projects. We recognise the repeat and take you to the same project you already made. If publishing your project to our network is briefly delayed, we say so on the install screen and keep retrying in the background, so the install check may take a few extra minutes.

If you leave it unanswered, nothing breaks. The project simply starts without a Commerce menu. If your plan includes Commerce, turn on Online store in Project Settings › General whenever you want it, and the menu appears straight away.

What happens next

Time to put A vs B on your site. Continue to Installing the snippet.