Workspaces | Split Test Pro

A workspace in Split Test Pro is the container for everything related to a single site or store: experiments, team members, conversion goals, billing, and integrations. Most accounts have one workspace per site they’re testing.

What Belongs to a Workspace

Each workspace has its own:

Experiments and results — visible only inside that workspace.
Team members — separate per workspace; an invite to one workspace doesn’t grant access to another.
Subscription / billing — each workspace has its own plan, and its own tested-sessions and AI-generations meters.
Install — for HTML, a unique script tag with its own API key. For Shopify, the workspace is tied to a single Shopify shop domain.
Integrations — the Google Analytics 4 connection is stored per workspace.
Settings — conversion goals, funnels, surfaces, calculated metrics, the brand profile, the workspace timezone and site-wide tracking are all configured per workspace. Each one is a card on the Settings page: see Workspace Settings.

This isolation means you can run experiments on multiple sites under one Split Test Pro login without data crossing over.

Creating a Workspace

When you sign up on an HTML site, the first thing you see is Set up your workspace: a Workspace name (“A friendly name to identify this workspace.”) and a Site domain (“The domain where you’ll install the experiment script.”). You can change both later in Settings.

To create another workspace later (for example, if you manage multiple stores or sites):

Open the workspace switcher in the sidebar footer — the button showing the current workspace’s name.
Click Create workspace.
In the Create workspace dialog, enter a Workspace name and a Site domain, then click Create workspace.

The dialog’s note says what you get: “Workspaces keep experiments, team, and billing separate — one per site. You’ll be the owner of the new workspace.” The app switches into the new workspace straight away. It starts empty: no experiments, no team members other than you, no integrations.

On Shopify, there’s nothing to create. Installing the app on a shop creates that shop’s workspace, with the shop’s timezone adopted as the workspace timezone and the shop’s email as its contact address.

Switching Workspaces

If you have access to more than one workspace, switch between them via the workspace switcher:

HTML — open the switcher in the sidebar footer. Workspaces you belong to are listed with a tick on the current one; click another to switch. The same menu has shortcuts to Workspace settings, Team members and Billing & plan.
Shopify — workspaces map 1:1 to shop domains; switching is implicit when you open a different shop’s admin and launch Split Test Pro from that shop’s Apps menu.

When you sign in with an email that belongs to several workspaces, the login page asks you to Pick a workspace first, showing each workspace’s name, domain and your role in it.

Switching changes everything you see in the app — Dashboard, Experiments, Settings — to that workspace’s data.

Editing Workspace Settings

In Settings → Workspace, owners can edit:

Workspace name — how teammates find the workspace in the switcher and the login picker.
Site domain (HTML) — “Experiments only run on this domain.” Editing it doesn’t move the snippet; if your site moves, install the script tag on the new domain too.
Timezone — “Experiment schedules display and launch in this timezone.” On Shopify this is auto-filled from your store’s timezone; override it if your team schedules in a different zone.

The same card also holds Appearance, the Dark/Light toggle. It follows your system until you choose, and it’s a per-browser preference rather than a workspace setting, so every member sees it, including members who otherwise see the card as owners-only.

Changes save with the card’s Save button and apply immediately. They don’t require re-installing the snippet (HTML) or reinstalling the app (Shopify).

Deleting a Workspace

Workspace deletion is permanent and cascading.

To delete an HTML workspace (owners only):

Open Settings → Danger zone.
Click Delete workspace.
In the Delete workspace? dialog, read the list of what goes, then click Delete workspace.

You’re signed out as soon as the workspace is gone. A live Stripe subscription on the workspace is cancelled as part of the deletion. If the workspace is also linked to a Shopify store with an active subscription, the deletion is refused: uninstall the Shopify app first, then delete the workspace.

For a Shopify workspace, uninstall the app from your Shopify admin. Re-installing creates a new workspace; the old one is gone.

After deletion:

The workspace disappears from the workspace switcher for all team members.
For HTML, the install snippet stops accepting events. Old snippets in your site code can be cleaned up at your convenience — they’re harmless without a valid workspace.

Workspace vs Account

A few mental-model notes:

Account — your personal login. You sign in with your email and a 6-digit login code sent to it; there’s nothing else to remember. One account per person, and it can be a member of many workspaces.
Workspace — a site or store’s container. One workspace per site, with any number of member accounts.
Membership — the link between an account and a workspace, with a role (owner or member).

Inviting someone to your workspace creates a membership for their account; it doesn’t merge their account with yours. They keep all their other workspace memberships intact.

Multi-Workspace Patterns

A few common ways teams organize multiple workspaces:

One workspace per brand. Brand A and Brand B run separate Shopify stores; each gets its own workspace. Team members on both brands have memberships in both.
One workspace per environment. Production workspace + staging workspace, each with its own snippet. Test experiments on staging before promoting to production. (Note: results don’t transfer — staging is for QA, not for collecting decisional data.)
One workspace per agency client. An agency uses Split Test Pro to run experiments on multiple client sites; each client has a workspace, and the agency team is invited to all of them.

The platform doesn’t enforce a particular pattern. Whatever shape fits your business, the workspace abstraction supports it.

Limitations and Caveats

No workspace-to-workspace data transfer. Experiments, goals, and team setups can’t be cloned between workspaces. Set each one up fresh.
No global-account view. There’s no aggregate dashboard showing all your workspaces at once. The workspace switcher is the only cross-workspace navigation.
Billing is per-workspace, not per-account. Each workspace has its own subscription. Three workspaces = three subscriptions.

Common Mistakes

Treating two related sites as one workspace. If shop.example.com and blog.example.com are different audiences with different conversion goals, they’re better as separate workspaces — your data stays clean and per-workspace billing reflects per-site spend.
Deleting a workspace to “clean up” old experiments. Use experiment archiving instead. Workspace deletion deletes everything; archiving just hides individual experiments.
Inviting people to the wrong workspace. Memberships are per-workspace. Double-check the workspace switcher shows the right one before sending invites.

Next Steps

See every Settings card in one place: Workspace Settings.
Add team members to a workspace: Team and Invites.
Set up the workspace’s billing: Billing and Plans.
Wire up integrations specific to the workspace: Google Analytics 4.