Inline [a|b|c]
Drop alternatives right into the copy with square brackets and pipes. At send, each recipient gets one of the options — no setup, no definition.
Content
Spintax rotates phrasing per recipient — write inline choices like [Hi|Hello|Hey] or reuse a saved tag, and each contact gets one consistent resolution. It softens the repetitive content fingerprint that pushes high-volume sends toward the bulk folder.
Template
Resolves to
Two ways to spin
Quick one-offs go inline; anything you want to reuse or tweak in one place becomes a saved tag. Both resolve the same way at send.
Drop alternatives right into the copy with square brackets and pipes. At send, each recipient gets one of the options — no setup, no definition.
Define a reusable spin under Content → Spintax and reference the tag wherever you need that rotation — change the value list in one place and it updates everywhere it's used.
The behaviour that matters
This is where naive content-spinning falls down. If {{greeting}} appears in the subject and again in the body, a careless tool might pick "Hi" once and "Hey" the next — and the recipient gets a message that reads inconsistently.
Mumara resolves per recipient, not per occurrence: whichever variant a contact draws, every instance of that tag in their message uses it. The randomisation is between people, never within one person's email — so you can spin tone freely without it ever reading broken.
Subject
Hey Ben — your cart's still warm
Body opener
Hey Ben, just a quick nudge…
Where it applies
Variation that only touches the subject still ships an identical body to everyone. Spintax spreads across the whole message, so the spin isn't cosmetic.
Where inbox-placement diversity matters most — rotate the line every recipient sees first.
Vary the sender label subtly across the send without spinning the address itself.
The preview snippet beside the subject — another visible surface to diversify.
Greetings, sign-offs, calls to action — the bulk of the content, spun line by line.
The text alternative spins too, so both versions of the email vary in step.
The same saved tags work in broadcasts, drips, and recurring sends — define once, reuse everywhere.
One saved tag can drive variation across every one of these surfaces at once.
Why it helps deliverability
When ten thousand recipients get a byte-for-byte identical message, that uniformity is itself a signal filters weigh. Rotating phrasing across the send softens that fingerprint.
Spintax resolves deterministically: the same tag produces the same option for a given recipient, every time it appears in their message. So a person never sees "Hi" in the subject and "Hey" in the body — their copy is internally consistent, just different from the next person's.
It works everywhere wording matters — subject line, from-name, pre-header, HTML body, and the plain-text part — so the variation spreads across the whole message, not just one field.
It's a deliverability tactic, not a personalization gimmick: the goal is to reduce the repetitive content fingerprint of a large send, which pairs naturally with proper authentication and clean lists to keep high-volume mail landing in the inbox.
What teams do with it
“We send big promotional batches, and adding spintax to the subject and the opener was a small change with a real effect on placement. The part I didn't expect to care about — same-tag-same-value — turned out to matter: our emails never read like a glitchy mail-merge, because each person's copy is consistent end to end.”
Verified review
Mumara ONE customer
Common questions
Two forms. Inline: square brackets with pipe-separated options, like [Hi|Hello|Hey]. Saved: a reusable tag in double curly braces, managed under Content → Spintax and referenced wherever you want that rotation. (It's bracket-pipe for inline, not single curly braces.)
No. Spintax is deterministic per recipient — the same tag resolves to the same option throughout that contact's message, so their copy is internally consistent even though it differs from the next person's.
Anywhere wording lives: the subject line, from-name, pre-header, HTML body, and the plain-text part. The variation spreads across the whole message, and the same saved tags work across broadcasts, drips, and recurring sends.
They layer. The platform resolves conditional blocks first, then spintax, then your %%field%% merge tags — so a spun line can still contain a merge tag that fills in per contact. Spintax rotates the phrasing; merge tags fill in the data.
Primarily deliverability. The point is to reduce the repetitive content fingerprint of high-volume identical sends. It complements personalization rather than replacing it.
A small handful is plenty — a few well-chosen alternatives per tag give meaningful variation without becoming hard to maintain. The aim is natural-sounding variety, not maximum entropy.
Related
Spintax is one mechanism in the personalization stack that layers in any send.
Read moreWhere spintax rotates wording, DCTs swap whole blocks on a condition.
Read moreApply spintax to a broadcast to vary phrasing across the whole audience.
Read moreWatch how varied content lands — delivery and bounce signals in real time.
Read moreMumara ONE · Spintax
Inline choices and saved tags rotate phrasing per recipient, deterministically, across every field — softening the repetitive fingerprint of high-volume mail.