Content
Every way to make one email feel personal.
Mumara ONE stacks several personalization mechanisms — merge fields, spintax rotation, conditional blocks, and the AI composer. They layer cleanly in any broadcast or drip and resolve in a predictable order, so each recipient receives a message assembled for them.
- Layer freely — use what each send needs
- Predictable order — deterministic output
- One editor — no tool sprawl
- Beyond the first name — depth, not tokens
- Custom Fields %%field%%
- Spintax [a|b] / {{tag}}
- Dynamic Content Tags [[tag]] / [if:…]
- Mumara AI chat composer
The mechanisms
Each does a different job.
Substitution, rotation, conditional swaps, and generation — different powers you reach for as the send demands. New mechanisms join the stack over time.
-
Custom Fields
%%field%%Swap a value — name, plan, renewal date — per recipient, with fallbacks for blanks.
Deep-dive -
Spintax
[a|b] / {{tag}}Rotate phrasing per recipient to soften the repetitive fingerprint of bulk sends.
Deep-dive -
Dynamic Content Tags
[[tag]] / [if:…]Swap whole blocks on a condition — fields, lists, or behaviour.
Deep-dive -
Mumara AI
chat composerDraft and refine the copy the other mechanisms then tailor.
Deep-dive
All at once
Watch one line assemble itself.
The mechanisms aren't alternatives — they compose. A single greeting can carry a conditional block, a spun verb, and a merged name, and each layer resolves on top of the last to produce one clean line for the reader.
The author writes the template once; every recipient gets the version assembled for them. Same input, same output, every time.
DCTplan=Pro → keep the block
Spintaxdrew "Welcome back"
Fieldfirst_name → "Ada"
Processing order
The sequence the engine follows.
Order matters because the layers feed each other — and because it's fixed, a complex email behaves predictably.
- 1
Dynamic Content Tags
Conditional blocks resolve first — only the chosen content continues.
- 2
Spintax
Wording rotates within the surviving content, deterministically per recipient.
- 3
Custom Fields
Merge values substitute in, with fallbacks for blanks.
- 4
System tags
Unsubscribe links, preference-centre URLs, and the like resolve last.
The AI composer sits in the same editor — draft with it first, then layer fields, spintax, and conditional blocks over the draft.
What teams do with it
Depth, not just a name in the greeting.
-
Address the person
- The goal
- You want the basics — name, plan, renewal date — filled in per recipient.
- What the stack does
- Custom field merges substitute the right value for each contact, with fallbacks so blanks never show.
-
Reshape the message
- The goal
- Different segments need genuinely different content, not just a different name.
- What the stack does
- Conditional blocks swap whole sections, so one email carries the right hero and offer for each audience inside it.
-
Soften a bulk send
- The goal
- A large identical send risks looking mechanical to filters.
- What the stack does
- Spintax rotates phrasing per recipient, deterministically, to reduce the repetitive content fingerprint.
-
Skip the blank page
- The goal
- You want a strong draft to personalize, fast.
- What the stack does
- Mumara AI composes the base copy; the other mechanisms then tailor it per recipient — a strong start and real relevance together.
“The thing I appreciate is that it's one editor, not four bolted-on tools. I draft with the AI, drop in merge fields, wrap a section in a conditional block, and add a spun greeting — and because the resolution order is fixed, I always know exactly what each recipient will get. No surprises on send day.”
Verified review
Mumara ONE customer
Common questions
What buyers usually ask.
What are the mechanisms?
Custom Fields (%%field%% value merges), Spintax (per-recipient wording rotation), Dynamic Content Tags (conditional content blocks), and the Mumara AI composer (drafting and rewriting) — with more added over time. Each has its own deep-dive.
Can I use them together?
Yes — that's the point. They layer in any broadcast or drip and resolve in a fixed order (Dynamic Content Tags, then Spintax, then Fields, then system tags), so a complex email produces a predictable per-recipient result.
Why does processing order matter?
Because the layers feed each other. Conditional blocks resolve first, so spintax and field merges only run on the content that actually made it into the message — keeping the output deterministic.
Do I need to use all of them?
No. Use what the send needs — a simple email might use only field merges, while a flagship campaign might stack several. They're available together but never required together.
Will the message ever render inconsistently?
No. Each mechanism is deterministic per recipient — the same contact always resolves to the same blocks, the same spun variants, and the same field values throughout their email. The variation is between people, never within one person's message.
Where does this work?
Across broadcasts and drips, in both the HTML editor and the drag-and-drop builder — the same stack, the same processing order, everywhere you compose an email.
Related
Pages that pair with this one.
-
Custom Fields
The %%field%% value merges — the simplest layer.
Read more -
Spintax
Per-recipient wording rotation for deliverability.
Read more -
Dynamic Content Tags
Conditional blocks that swap whole sections.
Read more -
Mumara AI
The composer that drafts the copy the others tailor.
Read more -
AI Content Tags
Automated per-send rewriting — the AI variant of spintax.
Read more
Mumara ONE · Personalization Options
One message, assembled for each reader.
Merge fields, spintax, conditional blocks, and AI — mechanisms that layer in a predictable order so every recipient gets a message built for them.