A subject line that gets opened but leaves readers disappointed isn't a win.
Marketers can spend days testing whether “Your update is here” beats “See what's new” and still miss the most important question: did the email help the right people take a useful next step?
Visisto makes Email campaigns the place to start. Build a real message, choose an eligible audience, test a clearer subject line and use Results to understand what actually happened. Add Automations when you've discovered a useful follow-up worth repeating.
Don't chase a universal “best subject line”. Learn what works for the people who chose to hear from you.
Create an email campaign with Visisto.
What does an email subject-line A/B test do?
An A/B test compares two subject lines under controlled conditions. Ideally, comparable recipients are randomly allocated to each version while the email body, offer and send timing remain consistent.
For example:
Version A: Your October product update
Version B: Two improvements you'll notice this month
The difference is the promise: one describes the category, while the other describes a specific reason to open. Which is better depends on the real email content and the recipients.
An experiment requires a consistent metric, comparable allocation and enough observations to support a conclusion. Sending version A on Monday to long-time customers and version B on Saturday to new subscribers is not a fair subject-line experiment.
Use any experiment functionality only where it is actually available in your Visisto plan and deployment. An example test design does not promise that every account includes automatic random assignment, built-in significance calculations or automatic winner selection.
Before testing: send an email worth receiving
A/B testing can't compensate for a weak message.
Check the campaign's purpose:
- Audience: Who is eligible and why would they care?
- Offer: Is the promised benefit real?
- Content: Does the email actually deliver what its subject says?
- Action: Is there one useful next step?
- Sender: Is the domain verified and recognisable?
- Permissions: Have unsubscribes and suppression states been honoured?
For a software release, write the actual release message before debating punctuation. For a store promotion, confirm the price, availability and terms before creating urgency.
Strong email campaigns are built on relevance. Testing helps improve them; it does not replace them.
Four meaningful subject-line experiments
1. Specific benefit versus generic announcement
A: Our monthly newsletter
B: Three customer questions answered this month
Hypothesis: people may respond more to a clear description of the information than a generic newsletter label. Only use B if the message really answers three questions.
2. Short versus descriptive
A: New reporting tools
B: See your weekly report in one clearer view
Hypothesis: a more descriptive statement might increase interest, particularly for an audience unfamiliar with the feature.
3. Practical question versus direct statement
A: Is your email signup form doing its job?
B: How to check whether your signup form is working
Hypothesis: one framing may communicate the value better. Keep the content identical and make sure it answers both claims.
4. Relevant deadline versus evergreen message
A: Registration closes on Friday
B: See what's included in next week's workshop
Only test A if the deadline is genuine and time is actually running out. Fake scarcity may gain attention at the expense of trust.
None of these examples is a guaranteed winner. They're realistic hypotheses a business can test.
Why open rate is not a complete success metric
Email open tracking commonly relies on image loading or similar signals. Mail privacy features, caching, automated image fetching and blocked tracking can change the numbers without an equivalent change in human readership.
An email counted as opened isn't necessarily one that a person read. An email with no tracked open may still have been seen.
If open rate is displayed, treat it as a directional signal rather than proof of human interest.
Where supported, compare meaningful link clicks, replies, signups or other appropriately attributed actions. These aren't perfect either—automated security scanners can affect clicks—but they may be closer to the campaign's goal when validated.
A useful primary metric could be:
Unique eligible recipients taking the intended action ÷ delivered eligible emails × 100.
Define how the numerator and denominator are counted in your analytics setup before interpreting the result. Use the actual metric availability in Visisto rather than inventing a report.
Example: the difference between absolute and relative lift
Imagine a hypothetical test with 2,000 delivered emails for each version.
| Metric | Subject A | Subject B |
|---|---|---|
| Delivered | 2,000 | 2,000 |
| Tracked opens | 700 | 800 |
| Tracked open rate | 35% | 40% |
| Verified relevant clicks | 100 | 104 |
| Clicks per delivered email | 5% | 5.2% |
B shows a 5-percentage-point higher tracked open rate, or approximately 14.3% relative growth in tracked opens.
But the relevant click rates are only 0.2 percentage points apart. That difference may be too small to reliably establish which subject produces more useful behaviour.
All the figures are illustrative, not Visisto customer results or universal benchmarks.
If you simply declare “14% better email marketing,” you're conflating an open-tracking signal with the actual customer goal.
Report the event you measured—not the business outcome you hope it represents.
Small samples can make any subject look brilliant
Suppose A receives two clicks from 50 delivered emails and B receives four from 50. That's 4% versus 8%, an apparently dramatic relative difference based on only two extra clicks.
Those observations provide limited evidence about what will happen next month.
Avoid checking after every handful of sends and stopping as soon as your favourite version leads. Define your planned sample and decision method ahead of time. If you need to establish a small lift, larger samples and suitable statistical methods may be necessary.
For many small newsletters, a single experiment will be inconclusive. That's fine. You can still improve a vague headline by making it clearer and learn from feedback over multiple sends.
Segment the audience without biasing the test
A subject that works for existing customers may not work for new prospects. But don't compare different audiences and then describe the difference as caused by subject wording.
If you test within a given audience, allocate comparable contacts to each variant. Document meaningful factors such as:
- New versus returning subscribers.
- Product interest or declared preferences.
- Geography and send-time context.
- Mobile versus desktop reading behaviour when reliable data exists.
- Recent campaign history.
- Whether the recipient received an overlapping Automation message.
If sample sizes are too small for every segment, keep the experiment focused rather than slicing the results until something looks significant.
Set up a subject-line test workflow around Visisto
Step 1: choose a real Email campaign
Start with a planned newsletter or update. Confirm the audience, sender and links.
Step 2: identify one wording question
Example: does a benefit-focused subject result in more relevant clicks than a generic release announcement?
Step 3: prepare exactly two versions
Keep the email content as similar as possible. Don't change price, visual layout and sender simultaneously.
Step 4: check the available experiment tools
Verify whether your Visisto account supports the required assignment and reporting. If it doesn't, don't claim the product automatically conducts a randomised A/B test. You may need a supported external testing process.
Step 5: test sending and unsubscribe behaviour
Make sure both versions render correctly and eligible audiences are protected from duplicates or unwanted sends.
Step 6: review reliable results
Record delivered counts, available engagement measures, complaints, opt-outs and appropriately attributable actions.
Step 7: document the decision
A result can be “inconclusive.” Repeat or refine the test rather than announcing a false victory.
The job is to improve one real campaign, not produce a dashboard screenshot.
A reporting template you can reuse
| Question | What to write down |
|---|---|
| Audience | Eligible recipients and selection method |
| Goal | The action you want after reading |
| Hypothesis | The one wording difference being tested |
| Versions | Exact A and B subject lines |
| Dates | Sending window and relevant context |
| Assignment | How comparable recipients were allocated |
| Primary metric | Clear numerator and denominator |
| Results | Raw counts as well as percentages |
| Limitations | Small sample, privacy tracking or uneven allocation |
| Next step | Keep, retest or try a clearer hypothesis |
This short record prevents somebody from presenting a different metric next week as proof of the original experiment.
Subject-line examples for different Visisto journeys
Newsletter: “Three useful ideas for your next campaign.”
Product update: “Your weekly report has a clearer layout.”
Booking information: “Your appointment is confirmed for Tuesday”—but only with real booking details.
Event promotion: “Registration is open for the product workshop.”
Booking confirmations and ticket notifications belong in their relevant product workflows. They are not necessarily suitable promotional A/B testing subjects, and their service purpose should not be blurred with marketing.
Visisto's strength is offering Email campaigns, Bookings, and Events & tickets as distinct customer journeys with shared capabilities where appropriate.
When to introduce Automations
Automations help with repeatable, supported events. They don't need to appear before you've ever sent a campaign.
Start with a useful email. Then ask whether new eligible contacts should receive a consistent welcome sequence or whether a relevant supported action merits follow-up.
A possible flow:
Eligible signup → Welcome message → Helpful resource → End.
Check the actual trigger, timing, eligibility and stop rules. Don't assume a subject-line experiment can automatically optimise every automation or that an open-tracking event is always reliable enough to trigger consequential actions.
Visisto pricing for email-first businesses
| Visisto plan | Monthly | Included emails | Included Visi credits |
|---|---|---|---|
| Free | £0 | 20,000 | 50 |
| Grow | £19 | 60,000 | 150 |
| Scale | £49 | 200,000 | 500 |
All plans include unlimited stored contacts and supported core marketing tools, subject to usage, security, consent and fair-use controls. The previous £9 Choice module is not a current new subscription.
See Visisto pricing for the current subscription and feature entitlements.
Frequently asked questions
Does a higher open rate always mean a better subject line?
No. Privacy tools and automatic image loading can affect opens; useful customer actions and appropriate context matter.
Can I test subject lines with a small list?
You can try alternatives, but small samples may not support a confident winner. Consider clear wording, qualitative feedback and repeated observations.
Does Visisto guarantee an A/B testing feature on Free?
Don't infer feature entitlements from sending allowances. Verify whether the actual account supports an experiment or a suitable external test process.
Should I test clickbait?
Misleading curiosity can violate trust. Test accurate, relevant promises rather than false claims.
Is an Automation the same as an Email campaign?
No. A campaign is generally a planned message to selected eligible recipients, while an Automation follows supported events and conditions.
Make your next subject line earn the next click
A useful subject makes a truthful promise. A useful email keeps it.
Build the campaign in Visisto, test a meaningful difference, and measure something closer to the real customer outcome.
Create your next Email campaign with Visisto.
Sources and verification
Reviewed 10 October 2026.
- Apple Mail Privacy Protection — effects on email tracking.
- Google Analytics metrics — distinctions between reporting events and users.
- Visisto pricing — plan limits.
Examples are illustrative, and statistically meaningful differences depend on data quality, sample size and study design.


