A sheet is the audience
Upload a CSV where each row is a recipient and each column a value. No list to create, no fields to predefine — the spreadsheet is the send list for this one job.
Sending · Business tier
A spreadsheet in. A personalized email per row out.
Upload a CSV where each row is a recipient, write one template that references the columns as merge tags, and Mumara ONE produces a personalized send for every row. No list setup — the send surface for individualized announcements and one-off outreach that doesn't fit the standard list model.
recipients.csv
emailnameplanrenews
Hi %%name%%, your %%plan%% plan renews %%renews%%.
3 rows → 3 personalized emailsvia transactional-bridge
Three steps
Sheet, template, send.
One template, every row filled
Write a single email referencing the columns as merge tags. Each recipient gets a version assembled from their own row, with fallbacks for blanks.
Sent through your Bridge
Mail merge still leaves through a Bridge with full authentication and tracking — a different front door to the same dedicated-IP infrastructure.
When to reach for it
For the sends a list doesn't fit.
Most marketing runs off lists and segments. But some sends are inherently row-based — an individualized announcement to a hand-built set of contacts, a one-time outreach with per-recipient details, a 1:few campaign you'd never model as a standing list. Mail merge is the clean path for those.
- 1
Prepare the CSV
An email column plus any per-recipient fields you want to merge.
- 2
Write the template
Compose one email referencing the columns as merge tags.
- 3
Map and preview
Match columns to tags and preview a few rows to confirm the personalization.
- 4
Send
Mumara produces a personalized email per row and sends through your chosen Bridge.
What it solves
The sends that don't belong in a list.
-
Forcing a one-off into a permanent list
Creating a standing list for a single individualized send clutters your audience model. Mail merge runs straight off the spreadsheet — no leftover list to manage.
-
Mail-merging from a desktop client
Word-plus-Outlook mail merge has no authentication, tracking, or deliverability behind it. Mail merge in ONE sends through your dedicated IPs with the full spine.
-
Per-recipient detail in a broadcast
Some sends need values that only exist per row, not as standing contact fields. The CSV carries them for this send without polluting the contact record.
-
No tracking on individualized sends
Hand-sent personalized emails are invisible afterward. Mail merge sends are tracked like any other — opens, clicks, bounces included.
What teams use it for
The sends that start life as a spreadsheet.
-
Event invitations
- The send
- A hand-built list of attendees with per-person details.
- What mail merge does
- One template merges each guest's name, session, and seat from their row — sent and tracked, no standing list created.
-
Renewal notices
- The send
- A one-off batch with per-recipient dates and amounts.
- What mail merge does
- Columns for plan, renewal date, and amount fill the template per row — through your transactional Bridge.
-
Personalized statements
- The send
- Per-recipient figures that aren't standing contact fields.
- What mail merge does
- The CSV carries the one-time values for this send, so the contact record stays clean and uncluttered.
-
Partner & 1:few outreach
- The send
- A small, individualized set you'd never model as a list.
- What mail merge does
- Write once, merge each partner's detail, and send with full authentication — not a desktop mail-merge with none.
“We send renewal notices in irregular batches, each with different amounts and dates per customer. Building a list for every batch was silly — now we just upload the spreadsheet, the template fills from the columns, and it goes out through our transactional Bridge with tracking. The contact records stay clean because the one-off numbers live in the CSV, not on the contact.”
Verified review
Mumara ONE customer
G2
Common questions
What buyers usually ask.
Do I need to create a list first?
No — that's the point. Mail merge runs directly off the uploaded CSV. Each row is a recipient for this one send, with no standing list to create or maintain afterward.
How does personalization work?
Reference the spreadsheet's column names as merge tags in your template (for example %%name%% or %%plan%%). Each recipient receives a version filled from their own row, with fallbacks where a cell is empty.
Does it still send through my dedicated IPs?
Yes. A mail-merge send leaves through a Bridge with full authentication and tracking, exactly like a broadcast — it's just a row-driven front door to the same infrastructure.
Which plan includes Mail Merge?
Mail Merge is a Business-tier capability of Mumara ONE.
Related
Pages that pair with this one.
-
Personalization Options
The same merge-tag mechanism mail merge uses, across all your sends.
Read more -
Custom Fields
For recurring sends, store per-recipient data as fields instead of a CSV per job.
Read more -
Broadcasts
The list- and segment-driven counterpart for your standing audiences.
Read more -
Bridges
A mail-merge send routes through a Bridge to its Pool and dedicated IPs, like every send.
Read more
Mumara ONE · Mail Merge
When the send is a spreadsheet, not a list.
Upload the CSV, write one template, and Mumara sends a personalized email per row — authenticated, tracked, and routed through your Bridge. Business tier.