Workspace Settings

Settings is one page. A left-hand navigation lists its sections, one card each, in the order below; click a section to jump to it, and the navigation follows as you scroll. The cards you see depend on the platform — Script & API and Danger zone exist only for HTML workspaces — and on your role: most cards are owner-only, and a member sees them as an Owners only placeholder with a line explaining why (“Conversion goals are managed by the workspace owner.”, and so on).

Every card saves on its own. A card’s Save button stays unavailable until something has changed, and a toast confirms each save.

Billing

Settings → Billing · both platforms · visible to every member; subscription changes are owner-only.

The card’s header carries a status pill — Active, Past due, Cancelled or Inactive — and the body shows your plan, the This month tested-sessions meter, Change plan beside Manage subscription (HTML, opens the Stripe portal) or Stop subscription (Shopify), the provider note, and the AI features inset with the AI generations this month meter. Without a subscription the three plan cards — Core, Pro, Agency — show inline so you can subscribe.

Plans, limits and the subscription flows on each platform are covered in Billing and Plans.

Script & API

Settings → Script & API · HTML only · owners only (“Only workspace owners can view the install snippet and API key.”).

Two blocks:

• The install snippet. “Paste this snippet into your <head> before any other script.” A code block holds the script tag with a copy button. The Active pill beside it is static — it labels the snippet as your live one and doesn’t check whether your site has it installed. The Dashboard’s site check does that.
• API key. The key is masked, with show and copy buttons, and the hint “This key identifies your site to the tracking script and is safe to expose. Server-side calls use the API keys card.”

The key shown here is the same key that appears in the snippet’s data-api-key attribute, so anyone who views your site’s page source can read it. Treat it as a workspace identifier rather than a secret: it lets a page load your experiments, nothing more. The install steps are in Install on an HTML Site.

Workspace

Settings → Workspace · both platforms · owners edit the fields; the Appearance toggle is for everyone.

The card opens with the Appearance row — the Dark/Light toggle, which “Follows your system until you choose.” It’s a per-browser preference, so members see it too, above their owners-only placeholder (“Workspace settings are managed by the workspace owner.”).

On HTML, owners then get:

• Workspace name — the name in the workspace switcher and the login picker.
• Site domain — “Experiments only run on this domain.”
• Timezone — grouped by region; “Experiment schedules display and launch in this timezone.”

On Shopify the name and domain come from the store, so the card holds only Timezone: “Auto-filled from your Shopify store’s timezone — override it if your team schedules in a different zone.”

More on names, domains and switching in Workspaces.

Integrations

Settings → Integrations · both platforms · owners only (“Integration settings are managed by the workspace owner.”).

“Connect Split Test Pro to your analytics tools.” Today that means one row: Google Analytics 4, with a pill that reads Not connected, Needs property, Connected or Reconnect, and a Connect or Disconnect button.

Connect sends you through Google sign-in; back in Settings a toast says “Google Analytics connected. Select your GA4 property below.”, and you pick the GA4 property and Save. The measurement ID of the stored property shows under the select. Reconnect appears when an older connection needs re-authorising so Split Test Pro can read your traffic data. Disconnect asks first: “Disconnect Google Analytics? Existing audience IDs remain in GA4 but won’t be updated.”

What the connection does with your data is in Google Analytics 4.

Site-wide tracking

Settings → Site-wide tracking · both platforms · owners only (“Only workspace owners can change site-wide tracking.”) · Pro and Agency.

One checkbox — “Record anonymous page views and goal events across your whole site — not just pages with experiments.” — and a Sampling select (100%, 25% or 10%) that stays disabled while tracking is off. The card’s guidance: “Under 50k sessions/mo: use 100% · 50–250k: 25% · over 250k: 10%.” Site-wide events never count toward your billable sessions, and they record the page path only.

On Core the card reads “Site-wide tracking powers Global Goals and Test Plans — included in Pro and Agency.” What the data feeds, and the privacy disclosure, are in Site-wide Tracking.

Conversion goals

Settings → Conversion goals · both platforms · owners only (“Conversion goals are managed by the workspace owner.”).

The card starts with the Default goal select, marked Required. Its first option is “Recommended default · <the platform’s default>”, which is what new experiments measure unless you pick another goal.

• On Shopify, “All standard goals are tracked automatically.” — the Standard goals grid lists them.
• On HTML, the card explains how to fire a goal from your site with window.SplitTestPro.track('event_key'), and that passing a value also tracks revenue.

Under Custom goals, each row has a Display name, an Event key (lowercase letters, numbers and underscores, like contact_submit), and a kind: JavaScript event, or Page view with a URL pattern and match type. Save goals writes the whole list; funnels and calculated metrics can use a custom goal once it’s saved. Details in Conversion Goals.

Funnels

Settings → Funnels · both platforms · owners only (“Funnels are managed by the workspace owner.”).

A funnel is an ordered list of steps drawn from the platform’s built-in events plus your saved custom goals. New funnel adds a block with a Funnel name, a Default pill (exactly one funnel is the default), numbered steps you can move up or down or remove, and an Add step… select. Up to 10 funnels of up to 12 steps each.

Until you save your own, the card shows the built-in funnel with a Platform default note; removing every funnel and saving returns the workspace to that default. The funnel view on results is described in Shopify Funnel Tracking.

Surfaces

Settings → Surfaces · both platforms · owners only (“Surfaces are managed by the workspace owner.”).

“Name the areas of your site — Homepage, Product pages, Cart — and the URL patterns that identify them (use * as a wildcard). Experiments can be tagged with a surface, and the experiments list can filter by it.”

Each row is a Name plus comma-separated URL patterns; every pattern starts with / or is *, like /products/*. + Add surface adds a row; up to 20 surfaces with up to 10 patterns each. The workspace is seeded with sensible defaults the first time the card loads, so the list is never empty. Test Plans use the same surfaces when they estimate traffic per area.

Calculated metrics

Settings → Calculated metrics · both platforms · owners only (“Calculated metrics are managed by the workspace owner.”).

“Define your own ratio metrics — a numerator divided by a denominator, like goal value per session. Each renders on the results tab with the full Bayesian lift treatment.”

New metric adds a block with a Metric name, a Numerator, a Denominator and a Format (Number, Currency or Percentage). Numerators are a goal’s value or count — on Shopify, checkout revenue too; denominators are sessions or a goal’s count — on Shopify, orders too. Saved custom goals appear in both lists. How the metric is read on results is in Calculated Metrics.

Brand profile

Settings → Brand profile · both platforms · owners only (“The brand profile is managed by the workspace owner.”).

“Tell the AI assistant what your brand is about. It uses this profile to ground experiment ideas and drafts in your positioning, audience, and visual identity.”

The fields: Brand name, What you sell / category, Target audience, Voice & tone and Key differentiators; then Visual identity — Primary color, Secondary color and Accent color as hex values with swatches, Heading font, Body font, and an Imagery style textarea. On Shopify an empty profile is pre-filled with the store name as a suggestion. Splitty and Create with AI read this profile when they write copy and variants.

Team

Settings → Team · both platforms · owners manage; members see the placeholder (“Only workspace owners can view and manage the team.”).

“Workspace members can view and edit experiments. Owners can manage billing and team.” The card is the roster — Member, Role, Last active — with Invite in its header, and Manage and Remove on each other member’s row. Pending invites sit in the same table with a Revoke button. The full flow is in Team and Invites.

Danger zone

Settings → Danger zone · HTML only · owners only (“Workspace deletion is restricted to owners.”).

One action: Delete workspace — “Permanently delete all experiments, variants, results, and team members. This cannot be undone.” The Delete workspace? dialog lists what goes and asks you to confirm. Shopify workspaces are deleted by uninstalling the app instead. What deletion covers is in Workspaces.

Usage and AI meters

Both meters live in the Billing card:

• This month — tested sessions used against your plan’s monthly limit. It turns amber as you approach the limit and, once new-visitor enrollment is frozen, reads “New visitors are no longer being entered into experiments — upgrade to resume.”
• AI generations this month — generations used against your allowance, with the date the meter resets. At the cap it reads “Free allowance used up — add the AI add-on to keep generating.” or, on a paid allowance, “Monthly fair-use cap reached — contact us if you need more.”

What counts, the thresholds and the emails each one sends are in Billing and Plans and Notification Emails.