Spintax is inline syntax that picks one of several phrasings at send time, so a 10,000-email campaign is not 10,000 copies of the same message. Buyers use it to avoid content fingerprinting by spam filters, which cluster near-identical messages from many senders. Volume senders treat it as a deliverability feature, not a copywriting one.
How it works
The sequencer parses a token such as {Hi|Hello|Hey} per recipient, picks an option at random and renders the result. Nesting and variables multiply the combinations: three choices in five places gives 243 versions. Good implementations render per recipient, show previews, and let follow-up steps use their own spintax.
| Tool | Syntax | Notes |
|---|---|---|
| Instantly | {{RANDOM | a | b}} | Variables nest inside; fallbacks; Liquid {% if %}; "AI Spintax Writer" (help) |
| Smartlead | {a|b|c} | Multi-level nesting; per-step; preview cycling (vendor blog) |
| Reply.io | {{Random | 'Hi' | 'Hello'}} | Spaces around pipes required; variables cannot nest inside (help) |
| Woodpecker | Supported | Help article; included in pricing |
| EmailBison | Spintax + Liquid | Per a third-party directory (GTM Directory) |
| Saleshandy | Supported | All plans (pricing) |
| PlusVibe | "SPINTAX generation" | Plan feature (pricing) |
No spintax documentation was found for lemlist, Salesforge, Apollo, Outreach or HubSpot sequences in this pass. lemlist and Salesforge lean on AI-generated personalisation instead. Treat their spintax support as unknown.
Who does it well
Instantly has the most complete stack: nested variables, fallbacks, Liquid conditionals and an AI writer that produces the spintax for you. Smartlead's own blog says multi-level nesting works without breaking. Reply.io's is the most fragile: a missing space breaks it, and merge fields cannot sit inside a spin block. That limits how much variation you can write.
Where implementations differ
- Syntax incompatibility. Three syntaxes across three leaders (
{a|b},{{RANDOM | a}},{{Random | 'a'}}). Copy written for one tool breaks in another, which is a small migration cost that keeps customers where they are. - Variables inside spins. Instantly allows them; Reply.io does not.
- AI generation. Instantly and PlusVibe generate spintax with AI. Smartlead points users to its SmartAgents for "content that goes beyond basic spintax" (vendor blog). The direction of travel is clear: hand-written spintax is being replaced by an LLM writing a different email per lead. See AI personalisation.
- Measurement. No vendor documents a "uniqueness score" or shows how similar the rendered messages are to each other. Users find out by previewing a handful.
Risks and abuse
Spintax exists mainly to defeat content clustering, which is how filters spot one sender (or one campaign spread over 100 lookalike domains) blasting the same text (How filtering works, Content and tracking). It is the textbook example of a feature that is good hygiene at low volume and evasion at high volume. Two practical risks:
- Bad spins read as spam. Synonym salad ("I hope this {finds|reaches|discovers} you") lowers reply rates and invites complaints, and complaint rate is what Google enforces on (Google and Yahoo sender rules).
- It breaks A/B tests. Random variation inside a variant adds noise to any comparison between variants (A/B testing).
Spintax is a crude proxy for what filters actually measure, which is similarity across a sender's traffic. A product that measured that similarity directly and generated variation until the campaign cleared a threshold would replace the syntax with a guarantee.
What this means for an entrant
- Support
{a|b}and import Instantly's and Smartlead's syntax. A migration tool that converts both is a cheap switching-cost killer (The wedge). - Allow variables and fallbacks inside spins, nested at least two levels, with a preview that cycles renders.
- Ship an AI variant generator with guardrails: keep the meaning, cap the reading level, flag spammy synonyms.
- Show a campaign-level similarity metric (for example, average pairwise similarity across rendered emails). No one does this today and it makes the feature legible.
- Position it as deliverability hygiene, not filter evasion. Policy teams at Google and Microsoft read vendor marketing too (Provider rules: Google, Microsoft and the ESPs).