Workspaces

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.
• Conversion goals (HTML) — defined per workspace.
• Subscription / billing — each workspace has its own plan and payment method.
• 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 — GA4 OAuth credentials, Klaviyo connection, etc., stored per workspace.

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

Creating a Workspace

When you sign up, you’re prompted to create your first workspace. To create additional ones later (for example, if you manage multiple stores or sites):

1. Open the workspace switcher — on HTML, in the sidebar footer; on Shopify, the workspace is auto-created per shop.
2. Click Create workspace (or the equivalent in your platform).
3. Enter:
   • Name — usually your brand or site name.
   • Site domain — the domain where you’ll install the snippet (HTML).

The new workspace starts empty: no experiments, no team members other than you, no integrations. Set it up the same way you set up your first one.

Switching Workspaces

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

• HTML — in the sidebar footer.
• Shopify — workspaces map 1:1 to shop domains; switching is implicit when you open a different shop’s admin and re-launch Split Test Pro from that shop’s Apps menu.

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

Editing Workspace Settings

In Settings → Workspace, you can edit:

• Name — display label only; doesn’t affect anything technical.
• Site domain — for HTML, the domain you’ve installed the snippet on. Editing it doesn’t move the snippet — you still need to update the script tag if your site moves.

These changes propagate 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:

1. Open Settings → Workspace.
2. Scroll to the Danger zone at the bottom.
3. Click Delete workspace.
4. Confirm by typing the workspace name when prompted.

Only workspace owners can delete a workspace.

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.
• For Shopify, the app is uninstalled from the shop. Re-installing creates a new workspace; the old one is gone.

Workspace vs Account

A few mental-model notes:

• Account — your personal login (email + password / OTP). One account per person, can be a member of many workspaces.
• Workspace — a site or store’s container. One workspace per site, can have many 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

• 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.