Notification Emails

Split Test Pro sends transactional email only: each message is triggered by something that happened in your workspace, and there’s no marketing list behind it. There is no notification-preferences page and no unsubscribe link — the way to stop a category of email is to stop the thing that triggers it, which each section below names.

Who receives them. The login code and the invite go to the address concerned. Everything else goes to the workspace’s contact address: on Shopify, the store’s email; on HTML, the workspace owner (the earliest owner, if there are several). Members don’t receive workspace emails.

Login code

• Subject: “Your Split Test Pro login code”
• Trigger: you click Send login code on the login page, or submit the sign-up form.
• Contents: the 6-digit code, and “This code expires in 10 minutes. If you didn’t request this, you can safely ignore this email.”

Enter the code on the Login code screen. A code that has expired or was already used is refused — request a new one.

Workspace invite

• Subject: “You’ve been invited to <site> on Split Test Pro”
• Trigger: an owner sends an invite from Settings → Team.
• Contents: the workspace and the role you were invited as, and an Accept Invite button.

The button opens the sign-up page with your email filled in. Verify the login code it sends and you’re in. The email says it for existing users: “If you already have an account, simply log in and you’ll be connected to the workspace.” The invite expires after 30 days; see Team and Invites.

Proposed plan update

• Subject: “Proposed plan update for <workspace>”
• Trigger: a Test Plan re-plans itself — when a test completes, an anomaly fires, new traffic data arrives, or the north-star goal changes. Refresh-driven re-plans email at most once a day.
• Contents: what triggered it, a summary, the proposed changes with reasons, and the buttons Review in Split Test Pro and — for revisions that only reorder or update existing items — Approve update.

Nothing changes until you approve; the email says so, and that approving uses 2 AI generations. Review opens the Testing Overview’s diff card. Approve update opens a confirmation page rather than approving on the click; the link lasts 7 days, and revisions that add new tests always need in-app approval. More on re-plans in Testing Overview.

Weekly program digest

• Subject: “Your testing program this week — <workspace>”
• Trigger: once per calendar week for a workspace with a Test Plan, and only when there’s news. A week with no running tests, no winners, no pending decision and nothing queued sends nothing.
• Contents: Running tests, Winners with the winning variant and lift, a line if “A proposed plan update is waiting for your decision.”, Next up, and an Open Testing Overview button.

Email only — there’s no in-app digest.

Autopilot digest

• Subject: “Autopilot acted on your testing program — <workspace>”
• Trigger: each Autopilot run that took an action or held something for your review; a run that did nothing sends nothing.
• Contents: every action this run, a Held for your review list when there is one, a Review in Split Test Pro button, and the reminder “Every autopilot action is logged in the Autopilot drawer. Autopilot acts only within the caps you set.”

Every Autopilot email ends with “Too much automation? Pause autopilot with one click — nothing else changes.” The link pauses Autopilot without touching your tests; re-enable it from the Autopilot drawer. See Autopilot.

Autopilot notices

Three single-purpose messages, each with an Open the Autopilot drawer button and the same one-click pause link:

• “Autopilot paused <action>” — one of the actions Autopilot had earned the trust to take was paused after a problem. “Autopilot re-earns this action by the same criteria that unlocked it. Review the log in the Autopilot drawer.”
• “Autopilot suspended itself” — after a run of consecutive failures. “No further automatic actions will run until you re-enable autopilot in the drawer.”
• “Autopilot stopped before spending more” — it hit the AI budget you set. “Autopilot never buys add-ons or overages. Raise the budget in the Autopilot drawer, or wait for the next monthly reset.”

Each notice is sent once per occurrence, not repeated on every run.

Rollout reminder

• Subject: “Make <experiment>’s winner permanent”
• Trigger: a winner rollout has been serving for 4 weeks. One email per rollout.
• Contents: “Hard-code the change in your theme and stop serving — your site stays fast and independent of Split Test Pro.”, the result line, and a Review the rollout button. It also reminds you that “Serving is free while you decide — rollout traffic never counts toward your plan’s sessions.”

See Winner Rollout.

Rollout regression check

• Subject: “Check <experiment>’s rollout”
• Trigger: a workspace with a north-star metric source configured, where the metric’s daily mean over the first 14 days after a rollout is more than 10% below the 28 days before it. At least 7 post-rollout days are needed, and the check sends once per rollout.
• Contents: “Your site metric moved after this rollout”, “This is an observational signal, not proof the rollout caused it.”, the size of the drop, and a Review the rollout button.

Split Test Pro never reverts a rollout on its own. “If you’d rather be safe, stop serving from the experiment page — visitors see your original theme again immediately.”

Scheduled launch failed

• Subject: “<experiment> didn’t launch as scheduled”
• Trigger: a scheduled test failed a launch check at its launch time and was moved back to Draft.
• Contents: “A pre-launch check failed at the scheduled start time, so the experiment was moved back to your drafts. Nothing is running.”, the reason, and a Review the experiment button.

The reason is one of the launch checks: the workspace has no active subscription, the monthly session limit was reached, too many experiments were already running, no primary goal was selected, or the primary calculated metric is not available. “Fix the issue above and schedule it again — or launch it manually whenever you’re ready.” See Scheduling Experiments.

Session-limit notices

Three emails track the This month meter, each sent once per month as the threshold is crossed, with an Upgrade your plan button and your usage so far:

• At 90% — “You’re close to your Split Test Pro monthly session limit.” Enrollment continues.
• At 100% — “You’ve reached your Split Test Pro monthly session limit.” Enrollment continues inside a grace buffer: “enrollment will pause once you pass 110% of your limit.”
• At 110% — “Your Split Test Pro experiments paused new-visitor enrollment.” New visitors are no longer entered into experiments; visitors already in a test keep their variant until you upgrade or the meter resets next month.

The thresholds and what the freeze does are in Billing and Plans.