Getting Started with Buzzmark: From Zero to Your First Send
New to Buzzmark? Here's the whole path in one place — from verifying a domain to sending your first message and watching it land — with links to the concepts behind each step.
The Buzzmark Team
If you're just starting with Buzzmark, this is the map. Five steps take you from an empty account to a delivered email you can watch land — and each one connects to a concept worth understanding rather than just clicking through.
1. Add and verify your sending domain
Everything starts with a domain you control. Add it, then publish the DNS records Buzzmark gives you so that SPF, DKIM, DMARC, and Return-Path all verify. The dashboard shows a live status for each, and you want all four green before sending a single message — this is the foundation the rest of your deliverability is built on. If the acronyms are a blur, our post on SPF, DKIM, and DMARC explained walks through what each one proves.
A tip: use a subdomain dedicated to sending, like notify.yourapp.com, rather than your bare domain.
2. Create a hive
A hive is an independent mail stream with its own configuration, reputation, tracking settings, inbound address, and webhook. Create one for your transactional mail — receipts, password resets, notifications — and leave open and link tracking off for it, since transactional mail doesn't need a tracking pixel. If you'll also send marketing mail, make that a separate hive so the two reputations never contaminate each other. Here's why that separation matters.
3. Connect your app
You have two doors: classic SMTP or the HTTP API. If you already have code or an app that sends over SMTP, point it at Buzzmark and you're moving in minutes. If you're building fresh and want structured responses, use the API. Both feed the same hive and are handled identically once the mail is in — it's purely about which integration fits your stack.
4. Send your first message
Send a test to your own inboxes at Gmail, Outlook, and Yahoo, and confirm it lands in the inbox rather than spam. Peek at the message headers to see authentication passing at the receiving end. This is your proof that steps 1–3 are wired up correctly, before any real user is involved.
5. Watch it land, and wire up the feedback loop
Open the hive's message log and delivery events to see exactly what happened to your message — accepted, delivered, opened if tracking is on. Then close the loop: point the hive's webhook at your app so bounces and complaints flow back automatically, and let hard bounces feed the suppression list. That's what keeps your reputation healthy without ongoing manual effort.
Where to go next
Once you're sending, a few things pay off quickly: warming your domain if it's new, running through the pre-flight checklist before your first real send, and keeping an eye on the handful of metrics that matter. But the core path is just these five steps: verify a domain, create a hive, connect your app, send a test, and watch it land. Everything else builds from there.
Welcome to Buzzmark. Now go send something.