Sending
A broadcast is the marketing campaign at the heart of Mumara ONE. Build it in either editor, target a list or a live segment, and send it through a Bridge — which routes to its Pool and dedicated IPs automatically. No sending nodes to wire up.
Subject
Audience
Bridge
Three decisions, one send
A broadcast comes down to three choices. Everything else — authentication, suppression, tracking, throttling — the platform handles underneath.
Write in the HTML editor for full control, or build visually in the drag-and-drop builder. The Mumara AI chat agent lives inside both — ask it to draft the email, rewrite a block, or spin up subject-line options. Layer in merge tags, conditional blocks, and spintax for per-recipient personalization.
Send to one list, several lists, or a dynamic segment that recalculates at send time. The recipient count updates live as suppression and per-list opt-outs are applied — so the number you see is the number that actually receives.
Pick the Bridge. That's it — the Bridge already routes to its Pool and dedicated IPs, so a promotional broadcast leaves on your promo IPs and a transactional-style send on the transactional ones. No sending-node configuration, because in ONE there are none to configure.
Build it your way
Hand-coders and visual builders both get a first-class editor — and neither has to start from a blank page, because the AI agent is one prompt away inside each.
Paste or write raw HTML with full control over markup, inline styles, and structure. For teams that maintain their own templates or need pixel-exact control, this is home.
Assemble blocks and modules on a canvas, with responsive preview built in. No code required — and the result still respects your personalization tags and conditional content.
The ONE difference
In a self-hosted setup you'd choose a sending node, wire it to IPs, and manage throughput per node. Mumara ONE collapses that: a Bridge already routes to a Pool of dedicated IPs. Choosing the Bridge chooses the reputation lane the broadcast travels on.
Keep a promotional Bridge for campaigns and a separate transactional Bridge for receipts and confirmations, and your marketing volume never touches the IPs your critical transactional mail depends on. The broadcast just picks the lane.
This broadcast's path
Broadcast
Spring picks · 48,210 recipients
Bridge
marketing-bridge
Pool
acme-promotional · 3 dedicated IPs
Dedicated IPs
203.0.113.10 · .11 · .12
In every broadcast
The things that decide whether a campaign lands — authentication, suppression, a pre-send sanity check, real-time results — ship with every broadcast rather than living in separate tools.
From draft to inbox
Anyone can write an email. The reason a campaign lands in the inbox instead of the promotions tab — or the spam folder — is everything that happens around the content.
When you pick the Bridge, you're picking which dedicated IPs carry the send and therefore which sender reputation the receiving servers weigh. Keeping marketing and transactional traffic on separate Bridges means a heavy promotional send can't drag down the reputation your password-reset emails rely on.
Before the send, the spam analyzer scans the composed message for the content and structure problems that trip filters, and the live recipient count reflects suppression and opt-outs already applied — so you never send to an address you shouldn't. Authentication (DKIM, SPF, DMARC) is already in place on your sending domain.
After the send, results stream in real time. You watch delivery, opens, clicks, bounces, and complaints move as the broadcast goes out — and the A/B tab breaks the result down by list, SMTP, top-clicked link, and browser so you see what actually drove it. Want the platform to pick a winning variant before the bulk send? That's Split Tests.
What it removes
Self-hosted senders configure nodes and map them to IPs for every send. In ONE there are no nodes — a Bridge already routes to its Pool, so 'where does this go out from' is a single dropdown, not a setup task.
On shared sending, a big promotional blast can bruise the reputation your receipts depend on. Separate promotional and transactional Bridges keep the two on different IPs so they can't contaminate each other.
A subject line or content pattern that trips filters is a disaster discovered post-send. The pre-send spam score surfaces it while you can still fix it.
Suppression and opt-outs applied at send time, reflected in a live recipient count, mean a hard-bounced or complained address never receives the next campaign — automatically.
Common questions
No — Mumara ONE has no sending nodes to configure. You pick a Bridge, and the Bridge already routes to its Pool and dedicated IPs. Choosing the Bridge is the entire routing decision for a broadcast.
Yes. A broadcast can send to one or more lists, or to a dynamic segment that recalculates at send time. The live recipient count updates as suppression and per-list opt-outs are applied, so you always see the true delivered audience before you send.
Two: a full HTML editor for pixel-exact control, and a drag-and-drop builder for visual assembly with responsive preview. The Mumara AI chat composer is built into both, so you can draft or refine copy without leaving the editor.
Run the spam analyzer on the composed broadcast and it scans subject-line patterns, content structure, spam-trigger word density, and compliance markers, returning a score with specific recommendations. Fix the flagged issues and re-run before you schedule.
Yes to both. Schedule a broadcast to send now, at a set time, or on a recurring cadence (see Evergreen Campaigns). To compete variants on a sample and auto-send the winner to the rest, use Split Tests; to break a sent campaign's results down by list, SMTP, link, and browser, use the A/B tab in its statistics.
Use separate Bridges — a promotional Bridge on your promotional Pool and a transactional Bridge on your transactional Pool. A marketing broadcast picks the promotional Bridge, so its volume never touches the IPs your transactional mail depends on.
Related
The endpoint a broadcast sends through. Pick the Bridge and the broadcast inherits its Pool and dedicated IPs.
Read moreTarget a broadcast at a dynamic segment that recalculates at send time, not just a static list.
Read moreWhen one send isn't enough, a drip turns a broadcast into a multi-step sequence with per-step routing.
Read moreCompete subject lines and content on a sample, then auto-send the winner to the rest of the audience.
Read moreThe pre-send score built into the broadcast editor — catch content and structure issues before sending.
Read moreReal-time delivery and engagement for every broadcast, down to per-IP and per-Pool detail.
Read moreMumara ONE · Broadcasts
Compose in either editor with AI on tap, target a list or a live segment, pick the Bridge that carries the right reputation — and send. Authentication, suppression, and tracking are already handled underneath.
