EonMailer The agency pain
Teams lose tracking when webhooks or signing keys are wrong, and still hop Mailgun logins per client.
Integrations · Live
Mailgun for agencies — multi-client ops on their domains
Mailgun is developer-friendly sending. EonMailer adds the agency layer: workspaces, readiness, approvals, and client-facing packs.
What EonMailer adds
Validate keys and region (US/EU), require domains, configure webhooks + open/click tracking via API when roles allow, and report from real events.
Outcome
Reliable Mailgun sending with agency-grade process and reporting.
Capabilities
Mailgun with EonMailer
- US and EU Mailgun regions
- Private API key + HTTP webhook signing key
- Domain-required identity model
- Auto-configure webhooks and open/click tracking when permitted
- Send quota / custom limit visibility when Mailgun exposes it
Setup path
From zero to first safe send
- Create or access the client’s Mailgun account
- Copy Private API key and HTTP webhook signing key from API Security
- Connect Mailgun in EonMailer (correct US/EU region)
- Add DNS for the sending domain + tracking CNAME as Mailgun requires
- Confirm tracking, then send from the workspace
Help Center
Step-by-step Mailgun guides
Deep setup docs live on Help — linked from the product wizard too.
FAQ
Mailgun questions agencies ask
Why does Mailgun need two keys?
The Private API key sends and configures domains/webhooks. The HTTP webhook signing key verifies delivery and engagement events so reports stay accurate.
Is a domain required?
Yes for Mailgun in EonMailer — Mailgun is domain-oriented. Single-address shortcuts that work on SES/SendGrid are not the Mailgun model.
Do opens and clicks need DNS?
EonMailer can enable tracking via API, but Mailgun’s tracking CNAME in DNS is still required for reliable open/click events.
Connect Mailgun for your next client
Free plan includes 1 workspace — enough to validate BYO Mailgun end to end.