Skip to content
Mumara

Content

One email. The right version for everyone.

Where a merge tag swaps a value, a Dynamic Content Tag swaps a whole block — a different hero, offer, or call to action depending on who's reading. Branch on fields, list membership, and — in ONE — Pixel and conversion events.

Get started The two syntaxes →
  • Whole blocks, not just values
  • Saved units or inline conditionals
  • Branches on behaviour — Pixel & conversions
  • The RSS mechanism for feeds in email
hero block · [[offer]]
[if:plan=Pro] … [else] … [endif]

Ada · plan = Pro

Your Pro perks for March — 3 things to try this week.

Ben · plan = Free

Upgrade to Pro and unlock dedicated IPs and AI credits.

one send, two blocksresolved per recipient

What it does

Swap blocks, branch deep, embed feeds.

Whole blocks, not just words

A merge tag changes a value; a Dynamic Content Tag changes an entire section — hero image, offer, CTA. One email becomes the right email for every segment inside it.

Branches on ONE data

Conditions read custom fields and list membership — and uniquely in ONE, Pixel events and conversion history. Show a "finish your purchase" block only to people who viewed pricing but didn't buy.

The RSS mechanism

The same [[tag]] wrapper is how RSS feed content embeds into emails, with iteration over items and per-item formatting — the backbone of self-publishing newsletters.

Two syntaxes

Saved units, or inline conditionals.

Reach for a saved unit when the same branching block recurs across sends; reach for an inline conditional for a one-off fork right in the body.

Saved [[tag]]

Build a rule-based content unit — several blocks each with their own conditions — and drop the tag into any email. Reuse it across sends; edit it in one place.

[[march_offer]]

Inline [if:field=value]

Write the conditional right in the body for a one-off branch — show this block when a field matches, fall back otherwise.

[if:country=US] … [else] … [endif]

Two rendering modes

Show the first match — or stack every match.

A saved content unit holds several blocks, each with its own rule. You choose how the tag resolves when more than one rule fits a recipient.

  • 1First qualifies — the email shows only the first block whose rule matches, so blocks act like mutually-exclusive branches in priority order.
  • 2All qualified, combined — every block whose rule matches is concatenated, so a recipient can collect several relevant sections in one email.
[[recommendations]] · Cleo
if interest=hiking ✓Trail gear block
if interest=camping ✓Tents block
if interest=cycling ✗Bikes block
Mode: all qualified → Cleo's email shows trail gear and tents.
per-block rulescombined on match

What conditions can read

Branch on who they are — and what they did.

Most tools condition on stored fields alone. In Mumara ONE a content rule can also read behaviour, so the block a contact sees reflects their actions, not just the data they were imported with.

  • Custom fields

    Any value on the contact record — plan, profession, interests, lifecycle stage.

  • List membership

    Which lists a contact belongs to, so the block matches the audience they sit in.

  • Pixel events

    Pages and actions tracked on your site — show a block only to people who viewed pricing.

  • Conversion history

    Whether a contact has purchased or converted — hide an offer from people who already bought.

  • Geography

    Country, region, or city captured as fields — swap the offer or shipping note by location.

  • Dates & milestones

    Signup date, renewal date, and other date fields — branch on where someone is in their journey.

Combine conditions in one rule to target a precise slice — Pro-plan contacts in the US who haven't converted.

What teams do with it

One template, many audiences inside it.

  • Collapse near-duplicate sends

    The goal
    You're maintaining three near-identical broadcasts per segment.
    What DCTs do
    Replace them with one email whose hero, offer, and CTA swap by condition — a single template to edit and ship.

  • Behaviour-driven offers

    The goal
    You want to nudge people who browsed but didn't buy.
    What DCTs do
    A block conditioned on Pixel and conversion events shows a finish-your-purchase prompt only to the people it fits.

  • Localised content

    The goal
    Different regions need different offers or wording.
    What DCTs do
    Branch on a geography field so each contact sees the block for their market, in one send.

  • Self-publishing newsletters

    The goal
    Your newsletter just relays your latest posts.
    What DCTs do
    An RSS-fed [[tag]] pulls feed items in automatically, with iteration and per-item formatting — no hand-curation.
“We used to run three versions of every campaign — one per plan tier — and inevitably one would go out with a stale offer. Now it's one email with conditional blocks, and the clever bit for us is branching on conversion events: people who already bought simply never see the upsell. Less to maintain, fewer mistakes.”

Verified review

Mumara ONE customer

G2

Common questions

What buyers usually ask.

How is this different from a merge tag?

A merge tag (like a custom field) substitutes a value — a name, a date. A Dynamic Content Tag swaps an entire block of content — a different hero, offer, or CTA. Use merge tags for values, DCTs for sections.

What are the two syntaxes?

Saved content units referenced as [[tag]] for reusable, rule-based blocks; and inline [if:field=value] … [else] … [endif] conditionals written directly in the body for one-off branches.

What's the difference between the rendering modes?

A saved unit can resolve two ways: "first qualifies" shows only the first block whose rule matches (mutually-exclusive branches), while "all qualified, combined" concatenates every matching block (a recipient collects several relevant sections in one email).

What can conditions check?

Custom field values and list membership, plus — uniquely in ONE — Pixel events and conversion history. So you can branch on what a contact did on your site, not just the data they were imported with.

How does it interact with spintax and merge tags?

They layer in a fixed order: conditional blocks resolve first, then spintax rotates wording inside the chosen block, then %%merge tags%% fill in per-contact values. So a DCT block can itself contain spun phrasing and personalized fields.

Is this how RSS gets into emails?

Yes. The same [[tag]] wrapper renders RSS feed items into an email, with iteration over items and per-item formatting (truncate, strip images, strip styles). It's the backbone of self-publishing evergreen newsletters.

Related

Pages that pair with this one.

Mumara ONE · Dynamic Content Tags

Send one email that reads like many.

Conditional blocks that branch on fields, lists, and behaviour — saved as reusable units or written inline. The right hero, offer, and CTA for every recipient, in a single send.

Get started See pricing