Spintax for cold email and how to pair it with Liquid

Picture a team sending the same 300 words to 2,000 leads, then wondering why replies stay flat. Every email looks identical to a spam filter and reads identical to the prospect. So someone suggests spintax cold email tricks: swap “Hi” for “Hello,” rotate the sign-off, call it personalization. It helps. It is not the whole fix.

In this piece, I’ll show you what spintax actually changes, what it leaves untouched, and why pairing it with Liquid conditions moves the needle further than either technique alone. I’ll pull from lemlist internal data showing exactly how much each layer adds to reply rates, down to the percentage point.

If you’ve ever wondered whether spintax is worth the setup time, or whether it’s just theater on top of a generic email, this answers that. You’ll leave with a clear map of where to spin, where to keep copy fixed, and how to stack spintax with Liquid so your emails stop looking like they came from a template.

What spintax is

Spintax is a syntax that lets you write several versions of a word or phrase inside curly braces, separated by pipes, so each email picks one variant at random. The result: no two emails leave your outbox with identical copy.

Here is what it looks like in practice:

{Hi|Hello|Hey} {{firstName}}, {I noticed|I saw|I came across} your team is {growing|scaling|expanding}.

That single line can render six different combinations. The recipient sees a normal sentence. Your sending infrastructure sees a unique string every time.

Spintax is easy to confuse with two other personalization layers, so let’s separate them. A variable like {{firstName}} swaps in one data field per lead. It changes what the email says, but every email still follows the same sentence structure. A Liquid condition changes which sentence appears based on a property of the lead (industry, role, company size). Spintax sits between the two: it randomizes wording without requiring any lead data at all.

Each layer solves a different problem. If you want to personalize at scale, you need all three working together.

What spintax does and does not fix

Variation helps. When every email in a batch shares the same body, filters can flag the pattern. Spintax breaks that fingerprint by making each message structurally unique.

But filters also weigh list quality, sending volume, domain reputation, and engagement history. And buyers judge relevance before they judge wording. Spintax on a generic pitch still reads generic.

We see this clearly in lemlist internal data. In France, emails using only first-name and company variables reply at 3.57%. Add Liquid conditions and the reply rate climbs to 5.89%. Stack Liquid with spin syntax and it reaches 7.94%.

The pattern holds in the US too: 2.24% with variables only, 4.86% with Liquid, 5.82% with Liquid plus spin syntax.

Spintax contributes, but it is one layer inside a larger email deliverability strategy. Treat it that way.

Where to place spintax in an email

Some parts of a cold email benefit from variation. Others break when you spin them.

The greeting, transition phrases, the call to action, and the sign-off are safe. These are functional lines where synonyms carry the same weight. Small wording changes in the subject line work too, as long as the meaning stays stable.

Your core claim and your proof point should stay fixed. These are the lines that carry your argument. If you spin them, you risk testing multiple messages at once with no way to know which one worked.

Think of it this way: spin the scaffolding, protect the payload.

How to write good variations

Bad spintax reads like a thesaurus exploded inside your email. Good spintax is invisible. Here are the rules that keep it clean.

• •

  Every variant must sound equally natural when read aloud. If one option feels stiff next to the others, cut it.

• •

  All variants should carry the same meaning. “Want to chat?” and “Ready to buy?” are two different messages, not two spins of one.

• •

  Keep variants in the same length range. A two-word greeting next to a nine-word greeting creates inconsistent tone.

• •

  Match the tone across every option. Mixing “Hey” with “Dear Mr. Johnson” signals that the email was assembled by a machine.

The workflow matters too. Write the full email first as a single, fixed draft. Read it. Edit it. Only then go back and add spin syntax to the safe zones. Never start with spintax. You will lose track of what the email actually says.

Never spin facts, numbers, or names. And before you launch, render at least three random versions and read each one start to finish. If any version sounds off, fix it before it hits an inbox.

Stack spintax with Liquid conditions

This is where most teams leave performance on the table.

Liquid is a templating language that inserts or removes content based on a condition tied to the lead. Instead of randomizing wording, it changes the message itself depending on who receives it.

Here is a short example:

Two leads, two different opening lines, each grounded in something real about their business. Combine this with spintax on the greeting and CTA, and the email feels handwritten.

The data backs this up. lemlist internal data shows reply rates climb with each personalization technique you stack: 2.5% with zero techniques, 2.9% with one, 3.7% with two, 5.7% with three, and 7.2% with four. In France, four stacked techniques push the reply rate to 8.72%.

Yet 75% of emails sent through lemlist still use only simple first-name and company variables. Liquid appears in just 3% of emails. Liquid combined with spin syntax shows up in 2%.

That gap is the opportunity. Most teams are competing on the same baseline personalization. Adding one Liquid block and a few spintax zones puts you in the top 2% of senders by sophistication. You can also layer in AI variables to generate a researched line per lead, which stacks on top of both. For a deeper look at how AI fits into the full personalization workflow, see our guide to AI email personalization.

Common spintax mistakes

• •

  Spinning entire paragraphs so that variant A and variant B are functionally different emails. You lose the ability to know what message is working.

• •

  Broken curly braces or missing pipes that render raw syntax in the inbox. Nothing kills trust faster than {Hi|Hello sitting in the greeting.

• •

  Variants with mismatched tone. One casual, one formal, one somewhere in between. The email feels stitched together.

• •

  Spinning the subject line into clickbait. “You won’t believe this” as one variant and “Quick question” as another means you are testing two completely different hooks with no control.

• •

  Using spintax to mask a weak email. If the core message has no relevance, variation in the greeting will not save it.

• •

  Forgetting to preview. Every platform that supports spintax lets you render a sample. Skipping this step is how broken emails go live.

Test spintax against a fixed version

The only way to know if spintax improves your results is to test it against a fixed version on the same audience.

Split your list into two equal segments. Send segment A the fixed email. Send segment B the spun version. Run both for the same duration, same send times, same follow-up cadence.

Judge the test on replies. Open rates fluctuate with subject lines and pixel-blocking. Reply rate tells you whether the body copy moved someone to respond.

Once you have a winner, run a second test: the winning version versus the same copy with one Liquid condition block added. This isolates the lift from conditional content on top of variation.

You can read more about structuring these experiments in our guide to cold email A/B testing. The key is changing one layer at a time so you know exactly what drove the result.

How to use spintax and Liquid in lemlist

You can write spin syntax and Liquid conditions directly inside any lemlist email step. No separate editor, no code export. Type {option one|option two|option three} in the body or subject line and lemlist picks one per recipient at send time.

Liquid conditions work the same way. Add {% if %} blocks inline, referencing any lead field or custom variable in your campaign. You can combine both with standard variables and AI variables in the same email.

Before you launch, use the preview feature to render the email for individual leads in your list. You will see exactly which spintax variant was selected and which Liquid branch fired for that lead. This is your last check before anything goes live.

For testing, you can A/B test a single step or an entire sequence. lemlist uses reply rate as the deciding metric, so the winning version is the one that generates real conversations.

Final takeaway

Spintax makes each email unique at the surface level. Liquid conditions make each email relevant at the message level. Stack them together, and you move from the 75% of senders using basic variables into the 2% generating the highest reply rates.

Build your first signal-based sequence in lemlist.