What is spintax?

How the syntax works

Braces group the variants, pipes separate them, and the sequencer resolves each group at send time: {Quick|Brief} question about {{company}} renders as "Quick question about Acme" for one recipient and "Brief question about Acme" for the next. Most tools support nesting - {Hope {your week|the week} is going well|Hope all is well} - which multiplies the variant space quickly: three groups of three options give twenty-seven distinct renderings of a single line.

Spintax resolves at the template layer, alongside merge fields. The difference is direction: merge fields pull recipient data in; spintax shuffles the sender's own words. One personalizes, the other randomizes - a distinction worth keeping, because only one of them makes the message more relevant to the person reading it.

Why it exists

When receiving systems began fingerprinting message bodies, identical copy at volume became an easy catch: the same paragraph arriving at thousands of mailboxes is a bulk signature no matter who sends it. Spinning was the countermeasure - make every copy unique and the fingerprint dissolves. For a period that arms race favoured the spinners. The reason it no longer decides outcomes is that the models moved on: modern filtering weighs who is sending (domain and mailbox reputation, authentication, volume patterns) and how recipients react (complaints, deletions, replies) far more heavily than string-level uniqueness. Identical copy is still worth avoiding - but a sender with a healthy infrastructure, conservative per-mailbox volume and real engagement does not live or die by it.

The failure modes, in descending order of embarrassment

• Shipped artifacts. A malformed group - {Hi|Hello with a missing brace - sails through many tools and lands in a prospect's inbox as raw markup. One artifact identifies the entire operation as automated. Our cold email grader flags template artifacts for exactly this reason.
• Word salad. Aggressive spinning of syllables and synonyms produces prose no human would write - "trust this correspondence locates you flourishing". It defeats the purpose twice over: unnatural phrasing is itself a signal, and a recipient who senses a machine wrote the message has already declined it.
• Fake variation. Twenty greetings spun in front of an identical 90-word pitch is one template wearing twenty hats. The part fingerprinting would catch is the part left unspun.
• Untested variants. Every spun path is a version of your message that a prospect will receive and your QA probably never read. The variant space grows multiplicatively; reading discipline does not.

What variation is actually for

The legitimate goal behind spintax - not being trivially identical across a large send - is better served one level up, at structure rather than syllables:

• Segment-level rewrites. Different industries and roles get differently argued messages, not reshuffled greetings. This is variation that also improves relevance, which spinning never does.
• Real personalization. A first line grounded in something true about the recipient makes every message naturally unique. Merge fields used with discipline do the mechanical share of that work.
• Copy that earns replies. Engagement is the strongest anti-spam signal there is: replies tell providers your mail is wanted. The rules we score copy against exist to produce that outcome, and no amount of spinning substitutes for it.
• Light spinning where it is harmless. Rotating a few genuinely natural greetings or sign-offs across a large fleet is defensible - it just should not be mistaken for a deliverability strategy.

Spintax and spam filters: the honest summary

Does spintax help you land in the inbox? Marginally at best, and only against the narrowest failure mode. The things that decide placement are sender reputation, authentication and engagement, the things that trigger filters are listed in the 1,130-phrase trigger list, and the things that get replies are relevance and brevity. A message that needs spinning to survive review usually has a copy problem spinning cannot fix - run it through the grader and the specific problem will have a name.

Common questions

Does spintax still work in 2026?

As a deliverability lever, barely: reputation and engagement dominate string uniqueness in modern filtering. As a way to avoid sending byte-identical copy across a large fleet, light structural variation still has a place. As a substitute for good copy, it never worked.

Do spam filters detect spintax?

Filters do not need to detect the syntax - it resolves before sending. What they catch is its by-products: unnatural phrasing, template artifacts, and the unspun identical core of a lazily spun message.

What is the difference between spintax and merge fields?

Merge fields insert recipient data - name, company - making the message more specific to the reader. Spintax shuffles the sender's own wording, making copies differ from each other without becoming more relevant to anyone. Details on merge fields.

Should follow-ups use spintax?

A follow-up in our cadence is a single short sentence with a changed angle - there is almost nothing to spin, and any artifact risk lands on the touch most likely to get the reply. Vary follow-ups by writing them per segment, not by spinning.