What is spintax, and why it stopped working
Spintax generates thousands of unique-looking emails from one expression. Here is the syntax, what it was for, and why varying the words changed nothing.
Spintax is a small syntax for generating lots of versions of one sentence. You put alternatives inside curly braces, separated by pipes, and the sending tool picks one each time it sends. It was built so bulk email wouldn't look identical, and it solves a problem that mostly isn't the problem any more.
Spintax puts alternatives inside braces separated by pipes, so {Hi|Hey|Hello} gives one of three greetings per email. A few small spins multiply into thousands of unique versions. But every version makes the same argument to the same kind of person, and the argument is what the reader responds to.
How does spintax syntax work?
The basic form is one set of braces with options separated by pipes:
"{Hi|Hey|Hello} Dana, hope you're well."
Most tools also support nesting, so an option can contain its own spin:
"{Hi|Hey} {there|{friend|colleague}}"
The versions multiply quickly. Three greetings, three verbs and three adjectives give you twenty-seven versions of one line, and a full email with eight small spins runs into the thousands.
Thousands of unique strings, one argument. The recipient only ever sees one of them, and has no idea the others exist. That's the part that tends to get forgotten.
What spintax was actually for
It had two jobs, and they're worth separating.
The first was beating exact-match filtering. Older spam filters fingerprinted message bodies, so a thousand identical emails was a usable signal, and varying the text got around that particular check.
The second was looking hand-written. That was always more of a hope than a result, because what makes an email look automated is what it says, not which synonyms it uses.
The first reason was real and is now largely out of date. The requirements the big mailbox providers publish today are about authentication, sending history and how recipients react. Gmail, for example, asks every sender to authenticate with SPF or DKIM and to keep reported spam below 0.3%. Nothing in those rules is about vocabulary. A carefully spun campaign to a cold list that marks it as spam will still end up in spam.
Why doesn't spintax fix cold email?
The trouble with spintax isn't that it's deceptive. It's that it works on the wrong layer.
| What varies | Does the reader notice? | Does it change replies? |
|---|---|---|
| The greeting | No | No |
| Verb synonyms | No | No |
| Sentence order | Rarely | Barely |
| The observation about their company | Immediately | Yes |
Only the last row matters, and no syntax can produce it. It comes from actually opening their careers page. It's the same reason a template that only swaps in the first name gets ignored: the greeting was never the part that needed to change.
There's a quieter cost too. Heavy spinning makes your sends hard to debug. When replies drop, you want to know which message failed, and "one of 4,374 variants" isn't an answer. Teams that spin a lot often can't tell you what they actually sent.
Where it ranks among the things that affect deliverability
If deliverability is why you're looking at spintax, it helps to see the whole ranking at once.
Wording, including spintax, is the bottom bar. Authentication is a gate you pass or fail, complaint rate says something about your list, and engagement says whether anyone wanted the email. All three outweigh vocabulary by a wide margin, and all three can be fixed in an afternoon or by sending to fewer people.
It's worth noticing why so many deliverability features live on the bottom bar: it's the one a product can control on your behalf. Nobody can sell you a better list.
Where spintax came from
Spintax grew up in the 2000s SEO world, as "article spinning": generate many near-duplicate pages from one article and hope search engines don't notice. They got better at noticing, and the technique died there.
It then moved into cold email, bringing the same assumption with it, that systems detect duplication by comparing strings. That assumption was already fading when it arrived. It hangs on because it's a satisfying idea, it's easy to build into a product, and when it fails, you can't see it fail. Nobody can tell you which of your four thousand variants went to spam, so the feature never gets the blame.
When it's still reasonable
Small spins on the greeting and sign-off are a cheap hedge. They cost you nothing and might help against a very basic filter. That's the fair case for spintax, and it's a footnote rather than a strategy.
If you do use it, keep it away from the parts of the email that carry meaning. Spin the value claim and you no longer know what you promised, and two people at the same company who compare notes will find they got different promises on the same day.
What to do instead
Vary the observation instead. One dated, checkable fact per account makes each email different in the only way the reader can actually see. Here are some examples of that, graded.
That takes ten to twenty minutes per account rather than a bit of syntax, which is exactly why spintax stays popular: it looks like personalisation at no extra cost, and looking like personalisation is the bit that doesn't work.
If deliverability is the real worry, the fixes are authentication, a warmed-up domain you can afford to lose, volume that ramps up slowly, and a list clean enough that nobody reports you. None of those are wording problems, and none of them get better by sending more.
For what it's worth, Revtive's prospecting agent doesn't do spintax. What it varies is the observation, because that's the only thing the reader notices.