# Bitelio — full content corpus

---

# https://dev.bitelio.com/

# Bitelio — The All-in-One Email Platform

One platform covering transactional email, marketing campaigns, and workflow automation.
Hosted in the EU, with a free plan and no cap on contacts.

[Get started free](https://app.dev.bitelio.com/auth/signup) | [Read the docs](https://docs.bitelio.com)

---

## Key facts

| Metric | Value |
|--------|-------|
| Price | Free plan; Pro from $19/month |
| Contacts | Unlimited, always free |
| Setup time | < 5 minutes |

---

## One platform instead of five

A single tool that stands in for Resend, SendGrid, Mailchimp, Customer.io, and Mailgun.

- [Bitelio vs Resend](/vs/resend)
- [Bitelio vs SendGrid](/vs/sendgrid)
- [Bitelio vs Mailchimp](/vs/mailchimp)
- [Bitelio vs Customer.io](/vs/customerio)
- [Bitelio vs Mailgun](/vs/mailgun)

---

## Why Bitelio

### Setup — < 5 min
Where other platforms need days of configuration, Bitelio goes from signup to first send — domain and DKIM included — in under five minutes.

### Pricing — 0 limits
Most tools raise your bill as your list grows. Bitelio stores unlimited contacts at no cost and sizes its plans by emails sent.

### Ownership
Your data answers to you. Pull contacts, events, and analytics through the API at any point — no lock-in, no export fees.

---

## Features

### Workflow Automation
Assemble multi-step email sequences visually, with triggers, delays, and conditional logic — zero code involved.

### Dynamic Segments
Audiences that recalculate in real time from contact attributes and behavior.

### Campaign Management
Schedule broadcast emails and follow their performance from a single view.

### Analytics
Opens, clicks, bounces, and conversions, measured across every campaign.

### Inbound Email
Accept incoming mail and hand it to your application through webhook notifications.

### Custom Domains
Send under your own domain, authenticated with DKIM, for consistent branding.

---

## Data model

Transactional, campaign, and workflow activity all land on one contact record — a single source of truth for every interaction.

- **Transactional** — Receipts, password resets, event-driven sends
- **Campaigns** — Newsletters, product launches, announcements
- **Workflows** — Onboarding sequences, drip campaigns

---

## Hosting & data control

- **Hosting**: EU infrastructure, GDPR compliant
- **Data control**: Complete API access — pull contacts, events, and analytics whenever you need
- **No lock-in**: Your data remains portable, always

---

## Pricing comparison

**Bitelio Pro: $19 / month with 15,000 emails included**

| Provider | Monthly price at 15,000 emails |
|----------|-------------------------------|
| Bitelio | $19 |
| SendGrid | $30 |
| Mailgun | $45 |
| Mailchimp | $60 |

*Based on plans matching Bitelio Pro at 15,000 emails per month.*

[Full pricing details](/pricing)

---

## What users say

Founders who switch tend to highlight the same three things: setup measured in minutes rather than days, an interface that stays out of the way, and pricing that doesn't climb as their audience grows.

---

## FAQ

**How is Bitelio different from other email automation tools?**
Bitelio is designed with SaaS teams, indie makers, and developers in mind. Build sophisticated automated email flows once, then fire them from anywhere with a single API call.

**Can I use Bitelio for transactional emails?**
Absolutely. Sign-up confirmations, cancellations, plan changes, and other transactional messages run side by side with your marketing email on one platform.

**Can I use Bitelio for newsletters?**
Yes — broadcast newsletters to your entire list, or narrow them down to any segment.

**What programming languages does Bitelio support?**
Anything that can make an HTTP request. There's a REST API plus SDKs for Node.js, Python, and more.

**How much does Bitelio cost?**
The free plan covers 1,000 emails/month. Pro is $19/month and includes 15,000 emails; Scale is $99/month with 100,000 emails plus a dedicated IP. Additional volume on paid plans runs $1.20 per 1,000 emails, and contacts are never limited on any plan.

---

Your first email can go out within 5 minutes. Free plan available, contacts never capped, nothing hidden.

[Create free account](https://app.dev.bitelio.com/auth/signup) | [Read the docs](https://docs.bitelio.com)


---

# https://dev.bitelio.com/pricing

# Bitelio Pricing — Simple, Transparent

1,000 emails/month on the free plan; Pro begins at $19/month. Contacts stay unlimited and nothing is hidden in the fine print.

---

## Plans

### Free forever

**1,000 emails / month** — No credit card required

What you get:
- Transactional emails
- Workflow automation
- Campaign broadcasts
- Custom domains
- Click & open tracking
- Unlimited contacts
- Bitelio branding on emails (paid plans remove it)

[Start for free](https://app.dev.bitelio.com/auth/signup)

---

### Pro

**$19 / month** — 15,000 emails included

Everything from Free, and:
- Bitelio branding removed
- $1.20 per extra 1,000 emails
- Monthly spend cap

[Get started](https://app.dev.bitelio.com/auth/signup)

---

### Scale

**$99 / month** — 100,000 emails included

Everything from Pro, and:
- Dedicated IP
- $1.20 per extra 1,000 emails

[Get started](https://app.dev.bitelio.com/auth/signup)

---

### Enterprise

**Custom pricing** — for high-volume senders

Get in touch and we'll shape a plan around your volume and requirements.

[Contact us](mailto:legal@bitelio.com)

---

## The full feature set, on every plan

No gated tiers, no bolt-on fees, no surprises at renewal.

| Feature | Description |
|---------|-------------|
| Transactional emails | Receipts, password resets, and event-driven mail delivered over API and SMTP. |
| Workflow automation | Sequences that trigger on events, featuring delays, conditions, and branch logic. |
| Campaign broadcasts | Newsletters and announcements, sent to your entire list or a chosen segment. |
| Unlimited contacts | Keep as many contacts as you want — list growth never raises your bill. |
| Full API access | A REST API plus SDKs for Node.js, Python, and more. |
| Custom domains | Your own sending domain, with DKIM, SPF, and DMARC configured automatically. |
| Audience segmentation | Live segments assembled from behavior, attributes, and engagement data. |
| Analytics & tracking | Opens, clicks, bounces, and unsubscribes — real numbers, not guesswork. |
| EU-hosted & GDPR-compliant | Data stored and processed on EU infrastructure under GDPR. |

---

## Hosting & data control

Bitelio runs on EU infrastructure with GDPR-compliant processing.
The data is yours to keep — pull contacts, events, and analytics through the API whenever you like.

[Read the docs](https://docs.bitelio.com)

---

Five minutes from signup to first send. Free plan, no card needed.

[Create free account](https://app.dev.bitelio.com/auth/signup) | [Read the docs](https://docs.bitelio.com)


---

# https://dev.bitelio.com/features/workflows

# Workflow Automation — Bitelio

Visual builder for complex email sequences with triggers, delays, and conditional logic. No code required.

[Get started free](https://app.dev.bitelio.com/auth/signup) | [Documentation](https://docs.bitelio.com)

---

## What are workflows?

Workflows are automated email sequences that trigger based on events in your application. Define who receives emails, when they receive them, and what conditions must be met — all without writing code.

## Key capabilities

- **Event-triggered**: Start workflows from any API event
- **Delays**: Wait minutes, hours, or days between steps
- **Conditional branching**: Branch paths based on contact data or behavior
- **Visual builder**: Drag-and-drop interface, no code required
- **Unlimited steps**: As complex as your use case demands

## Use cases

- **Onboarding sequences**: Welcome new users and guide them to activation
- **Drip campaigns**: Nurture leads over time with educational content
- **Re-engagement**: Win back inactive contacts automatically
- **Lifecycle emails**: Upgrades, renewals, cancellations

[Back to features](/features) | [Pricing](/pricing)


---

# https://dev.bitelio.com/features/segments

# Dynamic Segments — Bitelio

Real-time audience segmentation based on contact data and behavior.

[Get started free](https://app.dev.bitelio.com/auth/signup)

---

## What are segments?

Segments are dynamic groups of contacts that update automatically as contact data changes. Target campaigns and workflows to exactly the right audience without manual list management.

## Capabilities

- **Attribute-based**: Filter by any contact property
- **Behavior-based**: Segment by email opens, clicks, and engagement
- **Real-time**: Segments update instantly as contact data changes
- **Combinable**: AND/OR logic for complex targeting
- **Unlimited contacts**: No per-segment contact limits

[Back to features](/features) | [Pricing](/pricing)


---

# https://dev.bitelio.com/features/inbound-email

# Inbound Email — Bitelio

Receive and process incoming emails with webhook notifications.

[Get started free](https://app.dev.bitelio.com/auth/signup)

---

## What is inbound email?

Inbound email lets your application receive emails sent to your Bitelio domain. When a message arrives, Bitelio parses it and delivers the content to your webhook endpoint in real time.

## Capabilities

- **Webhook delivery**: Parsed email payload posted to your endpoint
- **Attachment handling**: Access attachments programmatically
- **Custom addresses**: Route different addresses to different webhooks
- **Reply detection**: Track email threads automatically

[Back to features](/features) | [Pricing](/pricing)


---

# https://dev.bitelio.com/features/email-editor

# Email Editor — Bitelio

Design beautiful emails with a drag-and-drop builder or write in Markdown.

[Get started free](https://app.dev.bitelio.com/auth/signup)

---

## What is the email editor?

Bitelio's email editor lets you build professional emails without writing HTML. Choose from the visual drag-and-drop builder or write in Markdown — both export to responsive HTML email.

## Capabilities

- **Drag-and-drop builder**: Compose layouts with blocks and columns
- **Markdown mode**: Write in plain text, render as rich email
- **Responsive**: Emails adapt to any screen size automatically
- **Preview**: See how your email looks on desktop and mobile
- **Reusable templates**: Save and reuse your designs

[Back to features](/features) | [Pricing](/pricing)


---

# https://dev.bitelio.com/features/smtp

# SMTP — Bitelio

Send emails through Bitelio using standard SMTP — no API changes required.

[Get started free](https://app.dev.bitelio.com/auth/signup)

---

## SMTP access

Bitelio provides SMTP credentials so you can send emails from any application or framework that supports standard SMTP. Drop in your Bitelio credentials and start sending immediately — no code changes needed beyond configuration.

## Details

- **Host**: SMTP endpoint provided in your dashboard
- **Port**: 587 (TLS) or 465 (SSL)
- **Authentication**: Username and password from your Bitelio project
- **Compatible with**: Any language, framework, or tool that supports SMTP

[Back to features](/features) | [Pricing](/pricing) | [Documentation](https://docs.bitelio.com)


---

# https://dev.bitelio.com/use-cases/saas

# Email for SaaS, from signup to renewal

One platform for the emails your SaaS lives on — verification and receipts that must arrive, onboarding sequences that activate users, and lifecycle campaigns that keep them.

## Common challenges

- Transactional email lives in one tool, marketing in another, and neither team can see the full picture of what a user actually received.
- Password resets and receipts land in spam because your sending domain was never properly authenticated or warmed up.
- Per-contact pricing punishes you for growing — every free-tier signup and churned trial still counts against your bill.
- Building onboarding drips means gluing together cron jobs, a template service, and a CRM that were never meant to talk to each other.

## Why teams choose Bitelio

### Transactional and lifecycle in one account

Fire password resets, receipts, and verification emails through the same API that runs your onboarding and re-engagement campaigns. No more reconciling two vendors and two sets of contacts.

### Onboarding that activates users

Trigger multi-step workflows on signup, first login, or any product event, with delays and conditional branches so each user gets the right nudge at the right moment.

### Segment by product behavior

Group contacts by plan, activity, or any custom trait you push from your app, then target trials, power users, or dormant accounts with precision.

### Deliverability built for critical mail

Guided SPF, DKIM, and DMARC setup plus a warmed sending reputation keep the emails users genuinely need out of the spam folder.

### Pricing that scales with sends, not signups

Start on a generous free tier and move to plans priced by email volume. Your bill tracks what you send, never how many contacts sit in your database.

### Own your data

Customer data lives on EU infrastructure with GDPR-compliant processing, and you can export contacts and events via the API at any time.

## Related features

- [Email API & SMTP](/features/smtp)
- [Workflow automation](/features/workflows)
- [Contact segments](/features/segments)
- [Email editor](/features/email-editor)
- [Deliverability guide](/guides/email-deliverability)

## FAQ

### Can Bitelio send both transactional and marketing email?

Yes. Bitelio was built to handle both from a single account, so your password resets, receipts, product notifications, and marketing campaigns all share the same contacts, sending domains, and deliverability.

### How do I keep password resets and receipts out of spam?

Authenticate your sending domain with SPF, DKIM, and DMARC and let your reputation warm up. Bitelio guides the setup and provides free checker tools so critical mail reaches the inbox. See our email deliverability guide for the full checklist.

### Does pricing scale with my number of users?

No. Plans are priced by emails sent, not contacts stored. Free-tier signups and inactive accounts never inflate your bill, which makes Bitelio predictable as your user base grows.

### Can I trigger emails from events in my product?

Yes. Send events from your app via the API or fire emails directly, then use workflows to turn signups, upgrades, or inactivity into automated onboarding and lifecycle sequences.

### Where is my customer data hosted?

Bitelio is a hosted service running on EU infrastructure with GDPR-compliant processing. Your contacts and event data remain yours — export them via the API at any time.


---

> Source: https://dev.bitelio.com/use-cases/saas

---

# https://dev.bitelio.com/use-cases/developers

# The transactional email API developers actually enjoy

A clean REST API, standard SMTP, and event webhooks — send your first email in minutes, then rely on authentication and delivery logs that just work.

## Common challenges

- Provider SDKs are bloated, poorly typed, or abandoned — you end up reading the raw HTTP docs anyway.
- You can send email, but you can't see what happened to it: no per-message logs, no delivery or bounce events.
- SMTP-only services force you to run a queue and retry logic yourself just to send reliably.
- Deliverability is an afterthought bolted on later, so your first production emails bounce or land in spam.

## Why teams choose Bitelio

### REST API or SMTP, your choice

Call a simple JSON endpoint or point any SMTP client at Bitelio. Same deliverability, same logs, whichever you prefer to integrate.

### Webhooks for every event

Subscribe to delivered, opened, clicked, bounced, and complained events and react in your own backend in real time.

### Send from anywhere

A language-agnostic HTTP API works with Node, Python, Go, Ruby, PHP, or a plain curl command — no SDK required, though examples are provided.

### Deliverability from day one

Guided SPF, DKIM, and DMARC setup plus free checker tools mean your domain is authenticated before you send a single message.

### Inspect every message

Full logs for each send with status, headers, and events, so debugging a missing email takes seconds instead of a support ticket.

### No lock-in

A plain HTTP interface plus full data export via the API mean you never get locked into a provider you cannot leave.

## Related features

- [SMTP relay](/features/smtp)
- [Inbound email parsing](/features/inbound-email)
- [Email API guide](/guides/email-api-guide)
- [DKIM checker](/tools/dkim-checker)
- [SPF checker](/tools/spf-checker)
- [Email header analyzer](/tools/email-headers)

## FAQ

### Does Bitelio have a REST API for sending email?

Yes. Bitelio exposes a simple JSON REST API for sending transactional email. Authenticate with an API key and POST your recipient, subject, and body to send in a single request. See the email API guide for examples.

### Can I use Bitelio over SMTP?

Yes. Point any SMTP client or library at the Bitelio SMTP relay using your credentials. You get the same deliverability and message logs as the REST API without changing your existing mail code.

### Which languages and SDKs are supported?

Because the API is plain HTTP, it works from any language — Node, Python, Go, Ruby, PHP, and more. You can call it directly or use the provided examples; no heavyweight SDK is required.

### How do I receive delivery and bounce events?

Configure a webhook endpoint and Bitelio will POST delivered, opened, clicked, bounced, and complained events to your backend as they happen, so your app always knows the state of every message.

### How do I set up SPF and DKIM?

Bitelio walks you through adding SPF and DKIM records for your domain, and our free SPF checker and DKIM checker let you confirm they resolve correctly before you go live.

### Is there a free tier for development?

Yes. You can sign up and start sending on a generous free tier without a credit card, which is ideal for building and testing before you scale.


---

> Source: https://dev.bitelio.com/use-cases/developers

---

# https://dev.bitelio.com/use-cases/ecommerce

# Email for e-commerce, from order to re-order

The receipts and shipping updates customers expect, plus the promotions and win-back flows that bring them back — all from one store-friendly platform.

## Common challenges

- Order confirmations run through your store platform while promos run through a separate ESP, and the two never share customer data.
- Abandoned carts slip away because setting up a recovery flow means wiring yet another tool into your checkout.
- Marketing suites charge by the subscriber, so a seasonal list spike wrecks your monthly bill.
- Shipping and receipt emails hit spam, generating support tickets from customers who 'never got a confirmation'.

## Why teams choose Bitelio

### Transactional emails that arrive

Order confirmations, shipping notifications, and receipts sent on authenticated, warmed infrastructure so they reach the inbox every time.

### Abandoned-cart and post-purchase flows

Trigger recovery emails, review requests, and replenishment reminders automatically from store events with visual workflows.

### Promotions and newsletters

Design campaigns in a drag-and-drop editor and send them to targeted segments of past buyers in a few clicks.

### Segment by purchase behavior

Split customers by order value, category, or recency to target VIPs, one-time buyers, and lapsed shoppers differently.

### Pay per email, not per subscriber

Plans are priced by emails sent, so a growing customer list never inflates your bill — even during a seasonal spike.

### Personalize with order data

Merge product names, order totals, and tracking links into every message using contact data synced from your store.

## Related features

- [Workflow automation](/features/workflows)
- [Email editor](/features/email-editor)
- [Customer segments](/features/segments)
- [Transactional vs marketing email](/guides/transactional-vs-marketing-email)
- [Deliverability guide](/guides/email-deliverability)

## FAQ

### Can Bitelio send order confirmations and shipping updates?

Yes. Send transactional emails like order confirmations, shipping notifications, and receipts through the API or SMTP with the reliability and authentication those messages demand.

### Can I automate abandoned-cart recovery?

Yes. Send a cart event to Bitelio and a workflow can trigger a timed recovery sequence — a reminder, then an incentive — automatically, without extra checkout tooling.

### Will my transactional and marketing emails share the same contact data?

Yes. Receipts and promotions run from one account and one set of contacts, so a customer segment you build for marketing already knows who has purchased.

### How is pricing calculated for a large customer list?

Pricing is based on emails sent, not subscribers stored. A list that grows or spikes seasonally raises your costs only when you actually send to it.

### Can I personalize emails with order details?

Yes. Store order totals, product names, and tracking links as contact data and merge them into templates so every confirmation and promotion is tailored to the customer.

### How do I keep receipts out of the spam folder?

Authenticate your domain with SPF, DKIM, and DMARC and warm up your sending reputation. Bitelio guides the setup so transactional mail lands reliably. See our deliverability guide for details.


---

> Source: https://dev.bitelio.com/use-cases/ecommerce

---

# https://dev.bitelio.com/use-cases/startups

# Email for startups that scales as fast as you do

Skip the stack of email tools. Send transactional and marketing email, automate lifecycle flows, and start free — then pay only for what you send.

## Common challenges

- Early-stage budgets can't justify a transactional provider plus a separate marketing suite plus an automation tool.
- Free tiers cap you at a few hundred contacts, forcing an upgrade before you've even found product-market fit.
- You need to move fast, but stitching together three email vendors eats engineering time you don't have.
- The cheap option today becomes the expensive one at scale, and migrating email providers mid-growth is painful.

## Why teams choose Bitelio

### One platform, every email

Transactional, marketing, and automation in a single account, so your small team is not juggling three dashboards and three bills.

### A genuinely generous free tier

Start sending without a credit card and stay free until you are ready to scale, so email never blocks your launch.

### Pricing that grows with you

Plans are priced by email volume as you grow. No per-seat fees, no per-contact penalties, and no surprise tier jumps.

### Automate before you hire

Set up onboarding, trial, and re-engagement flows once and let them run without a dedicated growth team.

### Won't outgrow you

The same platform handles your first hundred emails and your millionth, so you never face a painful mid-growth migration.

### No lock-in

Export your contacts and data anytime via the API — your email stack stays portable, so you are never trapped.

## Related features

- [Workflow automation](/features/workflows)
- [Email editor](/features/email-editor)
- [Contact segments](/features/segments)
- [SMTP & API](/features/smtp)
- [Pricing](/pricing)

## FAQ

### Is there really a free plan?

Yes. Bitelio has a genuinely generous free tier so early-stage startups can send transactional and marketing email without paying until they scale.

### Do I need a credit card to start?

No. You can sign up and start sending on the free tier without entering any payment details.

### Will Bitelio still work when we scale to millions of emails?

Yes. The platform is built for high-volume sending, so the same account that sends your first email handles your millionth. You never have to re-platform as you grow.

### Can one platform replace our transactional and marketing tools?

Yes. Bitelio combines transactional email, marketing campaigns, segmentation, and automation in one place, so a lean team can retire several separate subscriptions.

### How much does it cost as we grow?

Paid plans start at $19/month with 15,000 emails included and all features — no per-seat or per-contact charges. Your bill tracks the volume you send, which keeps costs predictable.


---

> Source: https://dev.bitelio.com/use-cases/startups

---

# https://dev.bitelio.com/use-cases/agencies

# Email for agencies managing many clients

Keep each client's sending domain, contacts, and campaigns cleanly separated — and bill for exactly what you send across every account.

## Common challenges

- Every client needs their own sending domain and reputation, but most tools force one workspace per subscription.
- Managing a dozen client logins across a dozen email vendors is a monthly billing and access nightmare.
- Per-contact pricing multiplied across many clients turns email into a margin-killer instead of a service you resell.
- Proving deliverability to clients is hard when you can't authenticate their domains or show delivery logs.

## Why teams choose Bitelio

### A project per client

Isolate each client's contacts, domains, templates, and campaigns in a separate project so nothing bleeds across accounts.

### Per-client sending domains

Authenticate each client's own domain with SPF, DKIM, and DMARC so their sending reputation stays theirs.

### Predictable, resellable pricing

Flat plan pricing based on emails sent makes it easy to mark up and bill clients without doing per-contact math for every account.

### One platform, every service

Deliver transactional email, newsletters, and automations for clients from a single toolset your team already knows.

### Deliverability you can prove

Per-message logs and free authentication checkers let you show clients that their email is actually landing.

### EU data residency for clients

Client data is hosted on EU infrastructure with GDPR-compliant processing, so you can offer data-resident email as part of your service.

## Related features

- [Workflow automation](/features/workflows)
- [Email editor](/features/email-editor)
- [Contact segments](/features/segments)
- [DMARC checker](/tools/dmarc-checker)
- [Spam checker](/tools/spam-checker)
- [Sender reputation guide](/guides/email-sender-reputation)

## FAQ

### Can I manage multiple clients from one account?

Yes. Create a separate project for each client to keep their contacts, sending domains, templates, and campaigns fully isolated while you manage everything from one login.

### Can each client use their own sending domain?

Yes. Authenticate each client's domain independently with SPF, DKIM, and DMARC so every client sends from their own domain and builds their own reputation.

### How does pricing work across many clients?

Pricing is based on plan tiers and emails sent, regardless of how many clients or contacts you manage, which makes it simple to mark up and rebill to each client.

### Can I resell Bitelio to my clients?

Yes. Because pricing is predictable and the platform handles multiple projects, agencies commonly package Bitelio-powered email into their retainers and mark it up.

### How do I prove deliverability to clients?

Per-message logs show the status of every send, and free tools like the DMARC checker and spam checker let you demonstrate that a client's domain is authenticated and landing in the inbox.


---

> Source: https://dev.bitelio.com/use-cases/agencies

---

# https://dev.bitelio.com/use-cases/marketing-teams

# The email marketing platform your team runs on

Design campaigns, segment your audience, and automate lifecycle journeys — with the deliverability and analytics a marketing team needs to hit send with confidence.

## Common challenges

- Campaign tools and automation tools are separate, so your team rebuilds the same audiences in two different places.
- Segments live in a spreadsheet export because your ESP can't slice contacts by real behavior.
- You can send a campaign, but you can't tell whether it actually landed — there's no deliverability visibility.
- Marketing suites price by contact, so growing the list you worked to build keeps raising your bill.

## Why teams choose Bitelio

### Campaigns without the clutter

Compose branded emails in a drag-and-drop editor and send to any segment in a few clicks — no code, no dev handoff.

### Segments that reflect real behavior

Build dynamic audiences from contact traits and activity, then reuse them across campaigns and automations.

### Automation and campaigns together

Nurture, onboard, and win back contacts with visual workflows that share the same audiences as your one-off sends.

### Deliverability you can trust

Authenticated sending, a warmed reputation, and spam-check tooling so the emails your team crafts actually reach the inbox.

### Metrics that matter

Track opens, clicks, and bounces to see what is working and improve every send.

### Priced by sends, not subscribers

Grow your list freely — you pay for the emails you send, never per contact, so success does not punish your budget.

## Related features

- [Email editor](/features/email-editor)
- [Contact segments](/features/segments)
- [Workflow automation](/features/workflows)
- [Spam checker](/tools/spam-checker)
- [Email open rate guide](/guides/email-open-rate)
- [Best practices guide](/guides/email-marketing-best-practices)

## FAQ

### Can my team build and send email campaigns?

Yes. Use the drag-and-drop editor to compose branded campaigns and send them to any segment, so marketers can ship email without engineering help.

### How does segmentation work?

Build dynamic segments from contact traits and activity — such as plan, engagement, or any custom field — and reuse them across both campaigns and automated workflows.

### Can I automate email sequences?

Yes. Visual workflows let your team automate onboarding, nurture, and re-engagement journeys using the same audiences you build for campaigns.

### How do I measure campaign performance?

Bitelio tracks opens, clicks, and bounces so your team can compare sends and iterate. Our guides on open rate and click-through rate explain the benchmarks to aim for.

### Does pricing depend on my list size?

No. Pricing is based on emails sent, not subscribers stored, so a growing contact list only costs more when you actually email it.

### Can Bitelio handle both marketing and transactional email?

Yes. Marketing campaigns and transactional messages run from the same account and contacts, so your team has one source of truth for everything you send.


---

> Source: https://dev.bitelio.com/use-cases/marketing-teams

---

# https://dev.bitelio.com/use-cases/nextjs

# Send transactional email from your Next.js app

Trigger verification emails, receipts, and notifications straight from a route handler or server action with a single HTTP call — no mail server, no SMTP config.

## Common challenges

- Next.js runs on serverless and edge runtimes where long-lived SMTP connections don't work well.
- You want to send from a server action or route handler without bundling a heavy mail library.
- Transactional emails from your app bounce because the sending domain was never authenticated.
- Local email testing means spinning up SMTP mocks instead of just hitting an API.

## Why teams choose Bitelio

### One fetch call from any runtime

Send email with a standard HTTPS request from a route handler, server action, or API route — it works the same on the Node and edge runtimes.

### No SMTP server to manage

Skip nodemailer and connection pooling. The REST API handles queuing, retries, and delivery so your app just makes a request.

### Keep secrets server-side

Call the API from server code with an env-var API key, so credentials never end up in the client bundle.

### React email templates welcome

Render your React or MJML templates to HTML and pass the markup straight to the send endpoint.

### Authenticated delivery

Set up SPF and DKIM once with guided tooling and free checkers so app emails reach the inbox in production.

### Automate lifecycle emails

Push product events to Bitelio and let workflows send onboarding and re-engagement email without extra app code.

## Related features

- [Email API & SMTP](/features/smtp)
- [Workflow automation](/features/workflows)
- [Email API guide](/guides/email-api-guide)
- [Markdown to email](/tools/markdown-to-email)
- [DKIM checker](/tools/dkim-checker)

## FAQ

### How do I send email from a Next.js route handler?

Make a server-side fetch request to the Bitelio REST API from your route handler, passing your API key and the message payload. Because it is plain HTTP, no SMTP connection or mail library is involved.

### Does it work with server actions and the App Router?

Yes. Server actions run on the server, which is exactly where you want to call the email API. Trigger a send from an action the same way you would from a route handler.

### Can I send email from the edge runtime?

Yes. Since sending is a single HTTPS request rather than a persistent SMTP connection, it works on the edge runtime where traditional mail libraries do not.

### Do I need nodemailer or an SMTP server?

No. The REST API replaces the need to run nodemailer or manage an SMTP server. If you prefer SMTP, Bitelio also offers a relay, but most Next.js apps use the HTTP API.

### Can I use React Email templates?

Yes. Render your React Email or MJML templates to an HTML string on the server and pass that HTML to the send endpoint as the email body.

### How do I keep my API key secure?

Store the key in a server-only environment variable and call the API exclusively from server code (route handlers, server actions, or API routes) so it is never exposed to the browser.


---

> Source: https://dev.bitelio.com/use-cases/nextjs

---

# https://dev.bitelio.com/use-cases/nodejs

# Transactional email for your Node.js backend

Send email from Express, Nest, Fastify, or a plain script with one HTTP request or standard SMTP — plus webhooks and delivery logs your backend can act on.

## Common challenges

- Running your own SMTP with nodemailer means managing connection pools, retries, and a queue you never wanted to build.
- You can send mail, but your app has no idea when it bounced or was marked as spam.
- Deliverability tuning — SPF, DKIM, DMARC, and warmup — is left entirely to you.
- Switching providers later means rewriting the whole email layer around a new SDK.

## Why teams choose Bitelio

### REST or SMTP from any Node framework

Use the JSON API from Express, Nest, Fastify, or a cron script, or point nodemailer at the Bitelio SMTP relay — your choice.

### Webhooks your backend can react to

Receive delivered, bounced, opened, and complained events at your endpoint and update your database in real time.

### Queuing and retries handled

Hand off the message and let Bitelio manage delivery, retries, and rate limiting instead of building that logic into your app.

### Deliverability included

Guided SPF and DKIM setup plus free checker tools mean your Node app's email is authenticated before it ships.

### Full message logs

Every send is logged with status and events, so tracing a missing email is a quick lookup rather than a mystery.

### Portable

A standard HTTP interface means no lock-in — export your contacts and data via the API whenever you want.

## Related features

- [SMTP relay](/features/smtp)
- [Inbound email parsing](/features/inbound-email)
- [Email API guide](/guides/email-api-guide)
- [SPF checker](/tools/spf-checker)
- [Email header analyzer](/tools/email-headers)

## FAQ

### How do I send transactional email from Node.js?

Make an HTTP request to the Bitelio REST API from your Node backend with your API key and the message details. It works from Express, Nest, Fastify, or a standalone script with no mail server to run.

### Can I keep using nodemailer?

Yes. Point nodemailer at the Bitelio SMTP relay with your credentials and your existing code keeps working while gaining Bitelio deliverability and logging.

### How do I handle bounces and complaints in my app?

Register a webhook endpoint and Bitelio posts bounced, complained, delivered, and opened events to it, so your Node app can update contact status or suppress addresses automatically.

### Does Bitelio handle retries and queuing?

Yes. Once you hand a message to the API, Bitelio takes care of queuing, retries, and rate limiting, so you do not have to build that infrastructure yourself.

### How do I set up SPF and DKIM for my domain?

Bitelio guides you through the DNS records, and our free SPF checker and DKIM checker confirm they resolve correctly before you send in production.

### Is there a free tier for testing?

Yes. Sign up and start sending on a generous free tier without a credit card, which is ideal for testing your Node integration before scaling.


---

> Source: https://dev.bitelio.com/use-cases/nodejs

---

# https://dev.bitelio.com/integrations/shopify

# Bitelio for Shopify

Connect your Shopify store with a native OAuth app — import customers with their consent, keep marketing consent in sync both ways, and turn orders and abandoned checkouts into automated Bitelio email.

## Capabilities

### Native OAuth Shopify app

Connect from Settings → Integrations in a couple of clicks. Bitelio installs as a proper OAuth app on your store — no private API keys to copy, no code — and the store access token is encrypted at rest.

### Consent-aware customer import

On connect, Bitelio imports your existing Shopify customers as contacts, carrying over tags, order counts, total spent, and last order date. Marketing consent is respected: customers who never opted in can be skipped, and an existing unsubscribe is never overwritten.

### Two-way marketing-consent sync

New and updated Shopify customers stay in sync with your contacts, and when someone unsubscribes in Bitelio you can write that consent change straight back to Shopify so both systems agree.

### Order events for your workflows

Every order fires a Bitelio event — created, paid, first order, fulfilled, cancelled, and refunds — carrying the order number, total, currency, and line items so a workflow can react in real time.

### Abandoned-checkout recovery

When a shopper starts a checkout and does not finish, Bitelio waits a delay you choose (5 to 1440 minutes) and, if no order arrives and the contact is still subscribed, fires an abandoned-checkout event you can recover from.

### Markets, languages & GDPR built in

Map each Shopify market to the language its emails go out in, and rely on the mandatory GDPR data-request and redaction webhooks that Bitelio handles for you.

## How to connect

1. In Bitelio, open Settings → Integrations.
2. Paste your store address (your-store.myshopify.com) and click Connect.
3. You are redirected to Shopify to approve the connection — review the permissions and install the app.
4. Back in Bitelio, the initial customer import starts automatically; watch its progress on the store card.
5. Map your markets to languages, choose whether unsubscribes sync back to Shopify, and start building workflows from your store events.

## What you can build

### Post-purchase & thank-you flows

Trigger a Bitelio workflow the moment an order is paid or fulfilled to send thank-you notes, review requests, or replenishment reminders — personalised with the order details attached to the event.

### Abandoned-cart recovery

Turn the abandoned-checkout event into a timed recovery sequence — a reminder, then an incentive — that stops the moment the shopper completes their order.

### Win-back & VIP segments

Segment contacts by order count, total spent, tags, or last order date to re-engage lapsed buyers and reward your best customers.

### Welcome the first order

A dedicated first-order event lets you greet brand-new customers differently from returning ones, right after their first purchase.

## Related features

- [Workflow automation](/features/workflows)
- [Contact segments](/features/segments)
- [Email editor](/features/email-editor)
- [Transactional vs marketing email](/guides/transactional-vs-marketing-email)
- [GDPR email compliance](/guides/gdpr-email-compliance)

## FAQ

### Is Bitelio a native Shopify app?

Yes. Bitelio connects to your store as an OAuth-based Shopify app that you install from Shopify’s own approval screen. There are no private API keys to copy, and the store access token is encrypted at rest.

### Does it import my existing customers?

Yes. As soon as you connect, Bitelio runs an initial import of your Shopify customers into contacts, bringing over tags, order counts, total spent, and last order date. Customers who have not given marketing consent can be skipped so you only email people who opted in.

### Does marketing consent stay in sync?

Yes, and in both directions. Shopify customer updates keep your contacts current, and an unsubscribe in Bitelio can be written back to Shopify. An explicit Bitelio unsubscribe is never overridden by a later Shopify change.

### Which store events can trigger emails?

Order created, paid, first order, fulfilled, cancelled, refunds, new customer, and abandoned checkout each fire a Bitelio event you can use as a workflow trigger, with the order or checkout details attached.

### How does abandoned-cart recovery work?

When a checkout is started but not completed, Bitelio waits a delay you set (5 to 1440 minutes). If no order arrives and the contact is still subscribed, it fires an abandoned-checkout event your workflow can act on. Completing the order cancels the reminder automatically.

### Is the integration GDPR-compliant?

Yes. Bitelio handles Shopify’s mandatory compliance webhooks — customer data requests, customer redaction, and shop redaction — and honours them even after a store is paused or uninstalled, so deletion requests are always respected.

### How is it priced?

The Shopify integration is included in your plan. Bitelio is priced by emails sent, not by the number of contacts you store, so importing your whole customer list never raises your bill on its own.


---

> Source: https://dev.bitelio.com/integrations/shopify

---

# https://dev.bitelio.com/vs/activecampaign

# Streamlined alternative to ActiveCampaign

ActiveCampaign packs in power you may never use — and bills you for all of it. Bitelio distills email automation down to what actually ships: no CRM baggage, no sales modules, no enterprise price list. Made for developers, not marketing departments.

## Why teams choose Bitelio

### Workflow Automation

Triggers, delays, and conditional branches compose into complete sequences — no CRM prerequisite, just email automation that plugs straight into your product.

### Developer-First API

A clean REST API brings email into your application directly. Skip the labyrinthine marketing console; write code, hit send.

### 50-80% Cost Savings

Automation that costs $149+/month at ActiveCampaign comes standard on every Bitelio plan from $19/mo. Multiply that difference by twelve months.

### Unlimited Contacts

Contact storage is free and boundless; only outgoing email is billed. List growth and invoice growth are fully decoupled.

### EU-Hosted & GDPR-Compliant

Processing happens on EU infrastructure under GDPR, and the API exports your contacts and data at any time. ActiveCampaign runs on US infrastructure.

### Fast Setup

From signup to first send in about five minutes — simple auth, a tidy API, solid docs, and no CRM standing between you and delivery.

## Feature comparison

| Feature | Bitelio | ActiveCampaign |
| --- | --- | --- |
| Pricing Model | Free plan + tiers from $19/mo | Expensive tiers |
| Setup Complexity | 5 minutes | Hours to days |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | Yes |
| Workflow Automation | Yes | Yes |
| CRM Included | No | Yes |
| Sales Automation | No | Yes |
| Machine Learning | No | Yes |

## FAQ

### When should I choose ActiveCampaign over Bitelio?

Teams that need a genuine CRM — sales automation, lead scoring, machine-learning recommendations — are on ActiveCampaign's home turf; it exists for combined marketing-and-sales organizations. Bitelio is for developers who want strong email automation wired into their product without dragging a CRM along for the ride.

### What is the price difference between Bitelio and ActiveCampaign?

ActiveCampaign opens at $29/month for the basics and climbs past $149/month once real automation enters the picture. Bitelio includes automation everywhere: free at 1,000 emails/month, Pro at $19/mo with 15,000 included, Scale at $99/mo with 100,000 — then a flat $1.20 per extra 1,000 emails, with unlimited contacts throughout. Email-focused teams commonly spend 50-80% less on Bitelio for equivalent email automation.

### Can Bitelio match ActiveCampaign's automation capabilities?

On the email front, yes — workflows, event-based triggers, and audience segmentation behave much as they do in ActiveCampaign. What Bitelio deliberately omits is everything around them: the CRM, the sales automation, the ML recommendations. If email automation is the actual job, Bitelio does it with far less machinery to implement and maintain.

### Is migration from ActiveCampaign to Bitelio difficult?

That hinges on how deep you are in. Teams using ActiveCampaign mainly for campaigns and email automation move quickly — export contacts, rebuild workflows, connect Bitelio's API — often within a single day. Heavy CRM, lead-scoring, or sales-automation users will need replacement tools for those pieces before making the jump.

### What ActiveCampaign features does Bitelio not have?

The CRM suite, sales pipeline management, lead scoring, SMS marketing, and machine-learning features stay exclusive to ActiveCampaign — Bitelio doesn't attempt them. Choose accordingly: enterprise breadth over there, focused email automation without the complexity over here.


---

> Source: https://dev.bitelio.com/vs/activecampaign

---

# https://dev.bitelio.com/vs/amazon-ses

# The full platform, not just delivery.

Amazon SES hands you bare infrastructure: no contact store, no campaign tools, no dashboard. Bitelio wraps that same grade of delivery in a complete, fully managed email platform — free to start, paid tiers from $19/mo.

## Why teams choose Bitelio

### Contact Management

A real subscriber database: track events, honor unsubscribes, build living segments. SES doesn't even have a notion of a contact.

### Marketing Campaigns

One-off broadcasts, scheduled campaigns, open and click tracking. SES moves bytes; Bitelio operates your whole email program.

### Workflow Automation

Event-triggered, multi-step sequences — onboarding, drips, win-backs. With raw SES, every bit of this is code you'd write and maintain.

### Transparent Overage

Exceed your allowance and the meter reads a flat $1.20 per extra 1,000 emails. No tier jumps, no invoice surprises — and contacts stay unlimited everywhere.

### EU-Hosted & GDPR-Compliant

EU infrastructure and GDPR-aligned processing out of the box — without wrangling AWS regions, IAM policies, or SNS topics to get there.

### Bounce & Complaint Handling

SES bounce and complaint notifications are processed automatically, protecting your sender reputation with zero code on your side.

## Feature comparison

| Feature | Bitelio | Amazon SES |
| --- | --- | --- |
| Free Tier | 1,000 emails/month | 62,000 emails/month (from EC2) |
| Pricing Model | Free plan + tiers from $19/mo | Usage-based (delivery only) |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | No |
| Workflow Automation | Yes | No |
| Dynamic Segmentation | Yes | No |
| Contact Management | Yes | No |
| Dashboard & Analytics | Yes | No |

## FAQ

### When should I use raw Amazon SES instead of Bitelio?

Raw SES makes sense when you already operate your own email platform and just need the delivery pipe — or when your engineers genuinely want to own every layer of the stack and can commit to building contact storage, unsubscribe flows, bounce processing, and analytics in-house. Bitelio ships that entire layer pre-built on SES-grade delivery, so you're productive from day one with no infrastructure to stand up or maintain.

### Is Bitelio more expensive than Amazon SES?

Per email, SES is cheaper: $0.10 per 1,000, covering delivery and nothing else. Bitelio starts free at 1,000 emails/month, with Pro at $19/mo (15,000 included), Scale at $99/mo (100,000 included), and $1.20 per extra 1,000 after that. What the difference buys you: contact management, campaigns, automation, segmentation, bounce and complaint handling, an admin dashboard, and unsubscribe management — everything you would otherwise pay engineers to build and keep running.

### Does Bitelio use Amazon SES under the hood?

It does. Delivery runs through AWS SES, so deliverability is identical to sending raw — but you also get the managed platform above it: dashboard, templates, campaigns, automation, and deliverability tooling, all maintained for you.

### How hard is it to migrate from SES to Bitelio?

Not very. Swap the SES SDK calls in your sending code for Bitelio's API, and your existing domain verification and DKIM setup can come along for the ride. In return you instantly pick up contact management, bounce handling, unsubscribe lists, campaign tools, and a dashboard — none of it built or maintained by you.


---

> Source: https://dev.bitelio.com/vs/amazon-ses

---

# https://dev.bitelio.com/vs/bento

# API-first alternative to Bento

Bento bundles everything; Bitelio does one thing exceptionally well. Get serious email automation with no CRM, no live chat, and no multi-channel sprawl — a developer-first, API-driven platform with honest pricing.

## Why teams choose Bitelio

### API-First Design

Designed from the endpoint up for developers embedding email in their apps — a tidy REST API, thorough documentation, and webhooks throughout.

### Unlimited Contacts

Contact storage is never metered. Sending is what you pay for, so your audience can balloon without your bill ever noticing.

### Transparent Pricing

Start free at 1,000 emails/month; paid plans begin at $19/mo with a flat $1.20 per extra 1,000 emails. Nothing expires and nothing forces an upgrade.

### Simple Setup

Five minutes from signup to first send. There is no CRM to provision, no channels to connect, no chat widget to install — only email, handled properly.

### EU-Hosted & GDPR-Compliant

Hosted on EU infrastructure with GDPR-compliant processing, and the API will hand back your contacts and data any time you ask. Lock-in is not part of the model.

## Feature comparison

| Feature | Bitelio | Bento |
| --- | --- | --- |
| Pricing Model | Free plan + tiers from $19/mo | Trial then subscription |
| Target Audience | Developers | Small businesses/creators |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | Yes |
| Workflow Automation | Yes | Yes |
| CRM Features | No | Yes |
| Live Chat | No | Yes |
| API-First Design | Yes | Integration-focused |

## FAQ

### When should I choose Bento over Bitelio?

If your business wants email, CRM, live chat, and customer relationship tooling rolled into a single product, Bento's all-in-one design is genuinely useful — it's aimed at small businesses and creators. Bitelio takes the opposite bet: pure, focused email automation for developers embedding email into their product, with none of the surrounding CRM weight.

### What is the pricing difference between Bitelio and Bento?

Bento runs a 30-day unlimited trial before moving you onto subscription pricing. Bitelio never expires: the free plan carries 1,000 emails/month with unlimited contacts, and paid plans begin at $19/month (Pro, with 15,000 emails included) plus a flat $1.20 per extra 1,000. If email is all you need, Bitelio usually wins on cost — though Bento bundles CRM and live chat into its price, so teams that would actually use those may find the bundle worthwhile.

### Can Bitelio handle email automation like Bento?

On the email side, feature for feature, yes — workflow automation, event-based triggers, transactional sending, and marketing campaigns are all present. Bento's extras (CRM, live chat, relationship management) are precisely what Bitelio leaves out, which is why it stays simpler for teams that only want email automation.

### How does the developer experience compare?

They target different builders. Bitelio is API-first — made for developers wiring email into their own applications with full control and flexibility. Bento leans on ready-made integrations for platforms like Shopify and WordPress and leads with its UI. More control with Bitelio; more out-of-the-box connections with Bento.

### Is migration from Bento to Bitelio easy?

For the email portion, yes: export contacts from Bento, bring them into Bitelio, rebuild workflows through the API or dashboard, and hook Bitelio into your app — count on a few hours for an email-only move. Bento's CRM, live chat, and multi-channel features have no equivalent in Bitelio, so plan replacements for those separately.


---

> Source: https://dev.bitelio.com/vs/bento

---

# https://dev.bitelio.com/vs/brevo

# All-in-one alternative for Brevo

Cleaner pricing, a leaner API, and contacts without limits. Everything email needs and nothing it doesn't — designed for developers rather than marketing departments.

## Why teams choose Bitelio

### Simpler Pricing

1,000 emails/month on the free plan, then Pro at $19/mo with 15,000 included. Contact count never factors in, and growth never triggers surprise charges.

### Developer-First

A tidy API, documentation that respects your time, and setup measured in minutes. For developers who'd rather ship than decode a marketing suite.

### Transparent Overage

Past your allowance, it's a flat $1.20 per extra 1,000 emails. No mandatory tier hops, no month-end bill shock.

### Full Data Control

Contacts, events, and analytics are yours to pull at any moment through the API or dashboard — lock-in isn't part of the deal.

### Unlimited Contacts

List growth is free. Where Brevo's price climbs alongside your contact count, Bitelio only ever charges for the emails you send.

### Email-Focused

One job, done well: email. No SMS module, no chat widget, no CRM sprawl — just focused, dependable email automation.

## Feature comparison

| Feature | Bitelio | Brevo |
| --- | --- | --- |
| Pricing Model | Free plan + tiers from $19/mo | Monthly tiers by contacts |
| Contact Limits | Unlimited | Tier-based limits |
| Target Audience | Developers & SaaS | All-in-one marketing suite |
| Setup Time | 5 minutes | 30+ minutes |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | Yes |
| Workflow Automation | Included | Higher tiers only |

## FAQ

### What is the difference between Bitelio and Brevo (Sendinblue)?

Bitelio is a developer-focused platform: one clean API, plans priced by emails sent, unlimited contacts everywhere. Brevo is a broad all-in-one marketing suite — more surface area, more complexity, and tiered pricing driven by how many contacts you keep.

### Is Bitelio cheaper than Brevo?

It depends on your usage pattern. Bitelio offers a free plan with 1,000 emails/month, Pro at $19/mo with 15,000 emails included, and Scale at $99/mo with 100,000 — plus a flat $1.20 per extra 1,000 emails. Contacts are unlimited on every plan, which is often more cost-effective for businesses with large contact lists but moderate email volume. Brevo charges based on contact count, which can become expensive as your audience grows.

### Do I keep control of my data with Bitelio?

Yes. Contacts, events, and analytics can be exported anytime through the API or dashboard, with no lock-in of any kind. All processing happens on EU infrastructure under GDPR.

### Is Bitelio easier to use than Brevo?

For a developer, definitely. Bitelio sticks to the email essentials — a clean API and minimal setup — while Brevo bundles SMS, chat, and a CRM, and that breadth brings complexity with it. Want pure email automation? Bitelio keeps things simple. Want a full marketing suite? Brevo may serve you better.

### How easy is it to migrate from Brevo to Bitelio?

Easily. Export your contacts from Brevo, bring them into Bitelio as a CSV, and repoint your application at Bitelio's well-documented API. Most teams are done in under a day.


---

> Source: https://dev.bitelio.com/vs/brevo

---

# https://dev.bitelio.com/vs/buttondown

# Full-platform alternative to Buttondown

Buttondown stops at newsletters. Bitelio runs newsletters, transactional email, and workflow automation from a single platform — unlimited contacts included, with 1,000 free emails every month.

## Why teams choose Bitelio

### Transactional Emails

Receipts, password resets, alerts, and notifications go out through the very platform that publishes your newsletter. This entire category simply doesn't exist in Buttondown.

### Workflow Automation

String triggers, wait steps, and conditions together into automated sequences — welcome series, drips, win-back flows. Buttondown ships nothing of the sort.

### Dynamic Segmentation

Segments rebuild themselves as contact data and behavior shift, so the right message reaches the right readers — without you maintaining static lists by hand.

### Unlimited Contacts

Hold as many contacts as you want — the meter runs on sending, not storage. Buttondown, by contrast, prices every plan on subscriber count.

### EU-Hosted & GDPR-Compliant

All processing happens on EU infrastructure in line with GDPR, and the API lets you pull out contacts and data whenever you choose.

### Developer API

A complete REST API with SDKs puts everything under programmatic control: fire emails from your backend, record custom events, manage contacts. The dashboard is entirely optional.

## Feature comparison

| Feature | Bitelio | Buttondown |
| --- | --- | --- |
| Free Tier | 1,000 emails/month | Up to 100 subscribers |
| Pricing Model | Free plan + tiers from $19/mo | Per-subscriber monthly plans |
| Transactional Emails | Yes | No |
| Marketing Campaigns | Yes | Yes |
| Workflow Automation | Yes | No |
| Dynamic Segmentation | Yes | No |
| API Access | Yes | Limited |
| Custom Domains | Yes | Yes |

## FAQ

### When should I choose Buttondown over Bitelio?

If you're a solo writer who wants nothing more than a minimal, beautifully simple newsletter tool, Buttondown is hard to beat — the writing experience is its whole reason for being. Reach for Bitelio when your needs extend past publishing: transactional email alongside your newsletters, workflow automation, dynamic segments, or full programmatic control through a modern API.

### What is the pricing difference between Bitelio and Buttondown?

The two price on entirely different axes. Bitelio meters emails sent — 1,000/month free, Pro at $19/month with 15,000 included, then a flat $1.20 per extra 1,000 — with unlimited contacts on every plan. Buttondown meters subscribers: free up to 100, then from $9/month for up to 1,000, climbing alongside your list. A large audience that hears from you only occasionally is dramatically cheaper to keep on Bitelio.

### Can Bitelio replace Buttondown for newsletter publishing?

It can. Marketing campaigns in Bitelio cover newsletter-style broadcasts to your full list or any segment, complete with scheduling, open and click tracking, and unsubscribe handling. One caveat: Bitelio is developer-first, so writers who want a no-code, prose-centric editor may still feel more at home in Buttondown.

### What does Bitelio offer that Buttondown doesn't?

Four big things: transactional email (receipts, password resets, notifications), multi-step workflow automation triggered by events, dynamic audience segmentation, and a complete API for programmatic control — plus unlimited contacts on every plan. Buttondown stays squarely in newsletter territory and offers no transactional sending at all.


---

> Source: https://dev.bitelio.com/vs/buttondown

---

# https://dev.bitelio.com/vs/convertkit

# Developer-first alternative to ConvertKit

ConvertKit serves creators; Bitelio serves the developers behind the product. You get the same automation muscle with a far better developer experience, none of the creator-tool overhead, and unlimited contacts on every plan.

## Why teams choose Bitelio

### Developer-First API

A clean, modern REST API sits at the core — straightforward endpoints for sending email and managing workflows, with no visual-builder ceremony in the way.

### Transparent Pricing

Sending-based plans: 1,000 emails/month free, paid tiers from $19/mo, and a flat $1.20 per extra 1,000 emails — you never get shoved into a bigger tier.

### All-in-One Email

Password resets, product launches, and automated sequences all ship from one place. ConvertKit stops at marketing — transactional email isn't on the menu.

### EU-Hosted & GDPR-Compliant

Data lives on EU infrastructure under GDPR-compliant processing, and the API lets you export contacts and records whenever you like. ConvertKit runs on US servers.

### 5-Minute Setup

Grab an API key, authenticate, send — that's the whole onboarding. No forms to assemble, no landing pages standing between you and your first email.

### Unlimited Contacts

Your contact database can grow without limit — there are no subscriber brackets to outgrow and no upgrade pressure as your audience expands.

## Feature comparison

| Feature | Bitelio | ConvertKit |
| --- | --- | --- |
| Pricing Model | Free plan + tiers from $19/mo | Pay per subscriber |
| Target Audience | Developers | Creators/marketers |
| Transactional Emails | Yes | No |
| Marketing Campaigns | Yes | Yes |
| Workflow Automation | Yes | Yes |
| Landing Pages | No | Yes |
| Product Selling | No | Yes |
| API-First Design | Yes | No |

## FAQ

### When should I choose ConvertKit over Bitelio?

ConvertKit earns its keep if you're a creator monetizing an audience — course sellers, bloggers, and podcasters get landing pages, digital product sales, and an interface built for non-technical users. Bitelio is the stronger pick for developers: an API-first design, transactional and marketing email under one roof, and a workflow that favors code over drag-and-drop builders.

### What is the pricing difference between Bitelio and ConvertKit?

ConvertKit bills by list size, so your invoice climbs as subscribers accumulate — even in months when you barely send. A 10,000-subscriber list runs $119/month there regardless of activity. Bitelio flips the model: pricing follows emails sent, with 1,000/month free, Pro at $19/month covering 15,000 emails, and a flat $1.20 per extra 1,000 beyond that. Contacts are unlimited on every plan, so growing your audience never touches your bill.

### Can Bitelio handle creator workflows like ConvertKit?

Largely, yes. Automated sequences, event-triggered emails, and audience segmentation all work in Bitelio much as they do in ConvertKit. What you won't find are landing page builders or product-selling tools — Bitelio deliberately stays focused on email delivery and automation.

### Does Bitelio have landing pages like ConvertKit?

No — form and landing page builders are intentionally out of scope. Bitelio concentrates on being an excellent email platform for developers. Need a landing page? Build it with whatever stack you prefer and wire it to Bitelio through the API. You keep total design freedom, and the platform stays lean and developer-friendly.

### How easy is it to migrate from ConvertKit to Bitelio?

Quite easy. Pull a CSV of your subscribers out of ConvertKit, bring them into Bitelio through the dashboard or API, rebuild your sequences in the workflow builder, and point your forms at Bitelio's API. A few hours covers most migrations — though any ConvertKit landing pages will need a new home, since Bitelio doesn't replicate that feature.


---

> Source: https://dev.bitelio.com/vs/convertkit

---

# https://dev.bitelio.com/vs/customerio

# Simpler alternative to Customer.io

Customer.io opens at $100/month and expects weeks of setup. Bitelio hands you the same event-driven automation in one all-in-one platform — and you can be sending inside of five minutes.

## Why teams choose Bitelio

### Developer-First Experience

APIs built the way engineers expect — minimal, predictable, and free of marketing jargon. Integration is measured in minutes, not sprint cycles.

### Transparent Pricing

A free plan, flat tiers from $19/mo, and not a single hidden line item. Profile counts and list sizes are irrelevant — sent email is the only unit.

### Unlimited Contacts

Keep an unbounded contact base at no cost. Active-profile fees simply don't exist here — sending is the sole thing on the meter.

### Quick Setup

Integration takes minutes, and there's no gauntlet in front of it — no onboarding program, no sales call, no procurement dance. Sign up and send.

### EU-Hosted & GDPR-Compliant

Data is processed on EU infrastructure in accordance with GDPR, and contacts and events export freely through the API. You are never locked in.

### Simplicity at Scale

Workflows stay simple even as volume climbs — enterprise-level output without the over-engineering or the dedicated ops headcount.

## Feature comparison

| Feature | Bitelio | Customer.io |
| --- | --- | --- |
| Free Tier | 1,000 emails/month | Limited free tier |
| Pricing Model | Free plan + tiers from $19/mo | Complex usage-based tiers |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | Yes |
| Workflow Automation | Yes | Yes |
| Behavioral Segmentation | Yes | Yes |
| Visual Journey Builder | Yes | Yes |
| Developer-First API | Yes | No |

## FAQ

### When should I choose Customer.io over Bitelio?

With a dedicated marketing-ops team and genuinely complex journey requirements, Customer.io's visual journey builder and advanced behavioral segmentation shine — it is enterprise tooling through and through. Bitelio fits teams who prefer developer-friendly APIs and leaner workflows, and who would rather skip the overhead of an enterprise marketing platform altogether.

### What is the pricing difference between Bitelio and Customer.io?

Bitelio keeps it flat: 1,000 emails/month free, Pro at $19/mo covering 15,000 emails, Scale at $99/mo covering 100,000, then $1.20 per extra 1,000 — and contacts are unlimited everywhere. Customer.io blends messages sent, active profiles, and feature access into layered usage tiers, and because profiles factor into the price, costs climb alongside your contact base. Small and mid-sized teams generally pay considerably less with Bitelio.

### Is migration from Customer.io to Bitelio complex?

That depends on what you've built. Straightforward transactional sending and simple workflows port over quickly — swap the API integration and recreate the flows. Elaborate visual journeys and deep behavioral segments will need some flattening along the way. For most teams, a few days of engineering time covers the whole move.

### What does Bitelio simplify compared to Customer.io?

Bitelio trims the enterprise layer while keeping the substance. In place of sprawling visual builders you get a clean, developer-first API; workflows live in code or a simple UI rather than elaborate journey maps; and pricing is a free plan plus flat tiers from $19/mo with unlimited contacts — not a tier matrix. Setup takes minutes, not weeks. And your data stays yours: contacts and events export through the API whenever you want, with no lock-in.


---

> Source: https://dev.bitelio.com/vs/customerio

---

# https://dev.bitelio.com/vs/klaviyo

# Affordable alternative to Klaviyo

Klaviyo's e-commerce muscle comes with an enterprise invoice. Bitelio matches the email automation — abandoned carts, order flows, campaigns — for a fraction of the price, with no contact-based billing and no fine print.

## Why teams choose Bitelio

### Affordable Pricing

Tiers start at $19/mo where Klaviyo charges by contact count. Stores typically trim email spend by 60-90% without giving up any automation capability.

### E-commerce Ready

Order confirmations, shipping updates, abandoned-cart recovery, product campaigns — every store email scenario runs through one flexible API.

### Developer-Friendly

A modern API that treats developers as first-class users. Shopify, WooCommerce, or a custom cart — webhooks and API calls connect them all.

### Unlimited Contacts

Customer lists of any size cost nothing to keep. Klaviyo reprices you upward as contacts accumulate; Bitelio only counts what you send.

### EU-Hosted & GDPR-Compliant

EU infrastructure and GDPR-compliant processing by default, with API export of contacts and data whenever you want it. Klaviyo operates from the US.

### Simple Integration

Wire up your store with webhooks or direct API calls — no sprawling Shopify app to babysit. The integration does exactly what you built it to do.

## Feature comparison

| Feature | Bitelio | Klaviyo |
| --- | --- | --- |
| Pricing Model | Free plan + tiers from $19/mo | Contact-based tiers |
| Typical Cost | Affordable | Very expensive |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | Yes |
| Workflow Automation | Yes | Yes |
| E-commerce Integration | API-based | Native deep |
| SMS Marketing | No | Yes |
| Predictive Analytics | No | Yes |

## FAQ

### When should I choose Klaviyo over Bitelio?

Klaviyo remains the pick for established e-commerce brands that lean on deep native integrations (Shopify, WooCommerce), SMS marketing, and AI-driven predictive analytics — and have the dedicated team and budget those features assume. Bitelio suits stores and developers who want the same caliber of email automation, e-commerce included, without paying enterprise rates for it.

### How much cheaper is Bitelio compared to Klaviyo?

The gap can be dramatic. At 10,000 contacts, Klaviyo lands somewhere between $150 and $300+ per month depending on email volume. Bitelio ignores contact count entirely: 1,000 emails/month free, Pro at $19/mo covering 15,000 emails, Scale at $99/mo covering 100,000, and a flat $1.20 per extra 1,000 after that. Because contacts are unlimited on every plan, the bigger your list gets, the wider the savings grow.

### Can Bitelio handle e-commerce emails?

Absolutely. Order confirmations and shipping updates run as transactional sends; launches and sales run as marketing campaigns; abandoned-cart and post-purchase sequences run as automated workflows. The integration happens over API rather than a native Shopify plugin — which trades a little setup work for far more control over your email logic.

### Does Bitelio integrate with Shopify like Klaviyo?

Via API, yes. Klaviyo ships a native Shopify app with prebuilt flows; Bitelio instead hands you webhooks and a full API so you can construct precisely the integration your store needs — custom or off-the-shelf. The trade is a bit of developer time for a lot of flexibility: you build it once, and it does exactly what you designed it to do.

### What Klaviyo features does Bitelio not have?

Bitelio stays deliberately email-only, so Klaviyo's SMS channel, native platform apps, AI product recommendations, and predictive analytics have no counterpart here. Brands that depend on those enterprise features — and can fund them — should stick with Klaviyo. Everyone else gets equally capable email automation at a fraction of the spend.


---

> Source: https://dev.bitelio.com/vs/klaviyo

---

# https://dev.bitelio.com/vs/loops

# No-limits alternative to Loops

Everything you like about Loops — transactional, marketing, and automation under one roof — minus the contact caps, the lock-in, and the surprise line items. Transparency is the whole point.

## Why teams choose Bitelio

### Dedicated Sending IP

On the Scale plan your mail leaves from a dedicated IP with priority support behind it — your sender reputation belongs to you alone, not a shared pool.

### EU-Hosted & GDPR-Compliant

EU infrastructure, GDPR-compliant processing, and an API that hands over your contacts and data on demand. Leaving is always an option — which is exactly the point.

### Unlimited Contacts

Audience growth carries no penalty here — no tier to bump, no surprise charge to absorb. The only thing metered is the email you actually send.

### Predictable Pricing

Free to begin, flat tiers from $19/mo, and $1.20 per extra 1,000 emails after that. You'll never sit through a sales call or discover a hidden fee.

### Full API Access

Every plan gets the entire API — documented, unrestricted, and never gated behind a "talk to sales" button.

### All Features Included

Transactional sending, campaigns, workflows, and segmentation come with every plan. Nothing is artificially fenced off by tier.

## Feature comparison

| Feature | Bitelio | Loops |
| --- | --- | --- |
| Pricing Model | Free plan + tiers from $19/mo | Monthly subscription tiers |
| Contact Limits | Unlimited | Tier-based limits |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | Yes |
| Workflow Automation | Yes | Yes |
| Dynamic Segmentation | Yes | Yes |
| API Access | Yes | Yes |

## FAQ

### What is the main difference between Bitelio and Loops?

The core split is pricing and data control. Loops sells subscription tiers capped by contact count; Bitelio meters emails sent and puts unlimited contacts on every plan. Feature-wise they overlap heavily, but Bitelio adds full API access and data export on every tier — which means more predictable costs and data that stays portable.

### Is Bitelio cheaper than Loops?

Usage decides it. Bitelio's free plan carries 1,000 emails/month; Pro is $19/month with 15,000 included and Scale is $99/month with 100,000 — overage runs a flat $1.20 per 1,000 emails, and contacts never cost extra. Loops bills a monthly subscription tied to how many contacts you hold. Teams whose lists keep growing usually come out ahead on Bitelio.

### Does Bitelio give me more control over my data than Loops?

It does. The API exposes contacts, events, and sending data for export at any moment, so nothing is ever trapped in the platform. Hosting sits on EU infrastructure with GDPR-compliant processing throughout.

### Does Bitelio have the same modern features as Loops?

Feature parity is essentially there: transactional email, marketing campaigns, workflow automation, dynamic segmentation, and a modern API — the same toolkit Loops offers. Where Bitelio departs is the absence of contact caps and its straightforward per-email pricing.

### How easy is it to migrate from Loops to Bitelio?

Very. Export your contacts out of Loops, load them into Bitelio via CSV, then swap your application over to Bitelio's API. A few hours is the typical timeline from start to finish.


---

> Source: https://dev.bitelio.com/vs/loops

---

# https://dev.bitelio.com/vs/mailchimp

# All-in-one alternative for Mailchimp

Mailchimp was built for marketing teams. Bitelio was built for the developers behind them — total control, a modern API, and billing tied to emails sent rather than contacts stored. Same capabilities, far better DX.

## Why teams choose Bitelio

### Transparent Pricing

Plans keyed to emails sent, never list size. Free to begin, Pro at $19/mo, and a flat $1.20 per extra 1,000 emails past your allowance.

### API-First

A REST API that treats developers as the primary audience — integration takes a fraction of the effort Mailchimp's marketing-oriented API demands.

### 5-Minute Setup

Sending within minutes of signup. No audience setup, no list plumbing — call the API and go.

### Unlimited Contacts

Hold your entire audience free of charge; only outgoing email counts toward your bill. Mailchimp meters every stored contact.

### All-in-One

Product emails and marketing sends share one platform — no separate Mandrill account to wire up.

### Event-Driven

Kick off workflows from real user actions — automation depth Mailchimp doesn't reach.

## Feature comparison

| Feature | Bitelio | Mailchimp |
| --- | --- | --- |
| Pricing Model | Free plan + tiers from $19/mo | Pay per contact |
| Target Audience | Developers | Marketers |
| API Quality | Modern REST | Legacy/complex |
| Transactional Emails | Built-in | Mandrill (separate) |
| Marketing Campaigns | Yes | Yes |
| Event-Based Triggers | Yes | Limited |
| Developer Experience | Excellent | Marketing-first |
| Setup Time | 5 minutes | 1-2 hours |

## FAQ

### When should I choose Mailchimp over Bitelio?

Mailchimp is the right call for marketers who live in drag-and-drop builders and want a marketing-first interface — it's genuinely strong for visual design and non-technical teams. Bitelio wins for developers: API-first architecture, transactional and marketing email in one product, and code where Mailchimp offers click-through wizards.

### What is the difference between Bitelio and Mailchimp pricing?

Mailchimp charges per contact stored, regardless of how many emails you send. Bitelio prices by sending volume instead: a free plan with 1,000 emails/month, Pro at $19/mo with 15,000 emails included, and Scale at $99/mo with 100,000 — plus a flat $1.20 per extra 1,000 emails. Contacts are unlimited on every plan, so with Mailchimp your cost increases as your list grows, while with Bitelio it only grows with what you send.

### Can Bitelio handle both transactional and marketing emails?

Yes — and it's a core reason teams switch. Receipts and password resets share a platform with newsletters and campaigns. Mailchimp splits transactional email off into Mandrill, a separate add-on service, which means one more integration to maintain.

### Is Bitelio's API easier to use than Mailchimp's?

Substantially, yes. Bitelio exposes a modern REST API built with application developers in mind. Mailchimp's API grew out of its marketing product, so you inherit concepts like "audiences," "campaigns," and "merge fields" before you can send anything. Developers routinely describe integrating Bitelio as an order of magnitude simpler.

### Does Bitelio have a visual email builder like Mailchimp?

Bitelio ships a lightweight editor, but most customers bring their own HTML templates — which unlocks version control, testing, and reuse. Need true drag-and-drop? Mailchimp does it better. Prefer writing beautiful, responsive emails in code? That's exactly what Bitelio is built for.


---

> Source: https://dev.bitelio.com/vs/mailchimp

---

# https://dev.bitelio.com/vs/mailerlite

# Developer-first alternative for MailerLite

MailerLite gets along with developers; Bitelio was designed around them. An API-first core, unlimited contacts, and billing pegged to emails sent — not subscriber tiers.

## Why teams choose Bitelio

### Transparent Overage

Beyond your allowance, overage is a flat $1.20 per extra 1,000 emails — none of the forced tier climbing that subscriber pricing imposes.

### API-First Design

Engineered for developers from the first commit: a modern REST API with thorough documentation that slots email neatly into your product.

### Priced by Emails Sent

Volume sent is the only variable in your bill. Your contact list can balloon without ever forcing an upgrade or a price bump.

### EU-Hosted & GDPR-Compliant

EU infrastructure, GDPR-aligned processing, and true data ownership — API access and exports whenever you want, vendor lock-in never.

### Fast Setup

Live in five minutes: simple auth, tidy endpoints, docs that answer the question you actually have. No visual builder to learn first.

### Unlimited Contacts

Contacts never cost anything, however many you add. Your database expands freely while pricing stays anchored to emails sent.

## Feature comparison

| Feature | Bitelio | MailerLite |
| --- | --- | --- |
| Pricing Model | Free plan + tiers from $19/mo | Pay per subscriber |
| Free Tier | 1,000 emails/month | 1,000 subscribers |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | Yes |
| Workflow Automation | Yes | Yes |
| Drag-and-Drop Builder | Basic | Advanced |
| API Quality | Modern REST | Good REST |
| Developer Experience | Excellent | Good |

## FAQ

### What is the main difference between Bitelio and MailerLite?

Pricing model and center of gravity. Bitelio bills by emails sent and gives every plan unlimited contacts; MailerLite bills by subscriber count. Both treat developers well, but Bitelio is API-first at its core, while MailerLite leads with visual builders and offers a solid API alongside.

### Is Bitelio more expensive than MailerLite?

That hinges on how you use email. MailerLite's bill grows with your subscriber list (around $10/month at 1,000 subscribers). Bitelio ignores list size entirely: free for 1,000 emails/month, Pro at $19/month with 15,000 included, Scale at $99/month with 100,000, then a flat $1.20 per extra 1,000 emails. Since contacts are unlimited on every plan, anyone with a large list and moderate volume usually comes out ahead on Bitelio — the list itself never costs a cent.

### How much control do I have over my data with Bitelio?

Complete control. Contacts, events, and analytics export on demand via API or dashboard, with zero lock-in. Processing happens on EU infrastructure under GDPR-compliant handling — a real advantage for privacy-sensitive products.

### Does Bitelio have a drag-and-drop builder like MailerLite?

There's a simple editor built in, though most Bitelio users write their templates in HTML for the version control, testing, and reusability that code brings. MailerLite's visual drag-and-drop tooling is stronger for non-technical users. Developers who template in code will prefer Bitelio; marketer-heavy teams may prefer MailerLite.

### How does Bitelio's API compare to MailerLite?

Both offer capable REST APIs — the difference is emphasis. Bitelio is built API-out, with programmatic sending and automation as the main event, so embedding email in your application is straightforward. MailerLite is built UI-out, with its API in a supporting role. For code-driven email work, Bitelio's developer experience comes out ahead.


---

> Source: https://dev.bitelio.com/vs/mailerlite

---

# https://dev.bitelio.com/vs/mailgun

# All-in-one alternative for Mailgun

Mailgun stops at transactional delivery. Bitelio builds campaigns, workflow automation, and segmentation on top of it — a single platform with a real free plan and unlimited contacts at every tier.

## Why teams choose Bitelio

### Marketing Campaigns

Reach every contact or just one segment with one-off broadcasts. Schedule them, measure them — none of which Mailgun provides.

### Workflow Automation

Assemble sequences from triggers, wait steps, and conditions. Made for welcome series, drip nurtures, and cart-recovery emails.

### Dynamic Segmentation

Segments rebuild themselves as contact attributes and behavior evolve, keeping your targeting sharp without manual list upkeep.

### Unlimited Contacts

Bring your whole audience — every plan stores unlimited contacts, and your bill only reflects the emails you send.

### EU-Hosted & GDPR-Compliant

EU infrastructure, GDPR-aligned processing, compliance from day one. Export everything through the API whenever you need to.

### All-in-One Platform

Run transactional, marketing, and automated email from one place instead of juggling separate services and glue code.

## Feature comparison

| Feature | Bitelio | Mailgun |
| --- | --- | --- |
| Free Tier | 1,000 emails/month | Limited trial |
| Pricing Model | Free plan + tiers from $19/mo | Tiered monthly plans |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | No |
| Workflow Automation | Yes | No |
| Dynamic Segmentation | Yes | No |
| Email Validation | Basic | Advanced |
| Custom Domains | Yes | Yes |

## FAQ

### When should I choose Mailgun over Bitelio?

Mailgun earns its place if advanced email validation matters to you, or you're pushing millions of messages a day and want a long-established infrastructure vendor with deep deliverability tooling. Bitelio is the better fit when you want campaigns, workflow automation, and transactional email running together on one platform.

### What is the pricing difference between Bitelio and Mailgun?

Bitelio offers a free plan with 1,000 emails/month, Pro at $19/mo with 15,000 emails included, and Scale at $99/mo with 100,000 included. Beyond your allowance you pay a transparent $1.20 per extra 1,000 emails — no forced tier jumps. Every plan includes unlimited contacts, marketing campaigns, and workflow automation at no additional cost — with Mailgun, marketing requires separate tools.

### How involved is migrating from Mailgun to Bitelio?

You'll need to rework your API calls, since Bitelio's endpoints and parameters differ from Mailgun's. The core concepts carry over cleanly, though — templates, webhooks, and custom domains behave similarly on both — and your existing email templates adapt with only minor tweaks. Expect a few hours of development time for the integration.

### What does Bitelio add beyond transactional emails?

Campaigns for one-off broadcasts to your whole list or a chosen segment, automation for trigger-driven multi-step sequences with delays and conditions, and segmentation that keeps itself current as contact data and behavior change. The result: transactional and marketing email in a single product — with your data always yours, thanks to API access and one-click exports.


---

> Source: https://dev.bitelio.com/vs/mailgun

---

# https://dev.bitelio.com/vs/mailjet

# All-in-one alternative to Mailjet

Mailjet covers the email basics well, but workflow automation simply isn't there. Bitelio pairs built-in automation with unlimited contacts on every plan — so you never have to bolt on a second tool.

## Why teams choose Bitelio

### Workflow Automation

Chain triggers, wait steps, and conditions into multi-step sequences — onboarding journeys, drip series, win-back campaigns. Nothing comparable exists in Mailjet.

### Dynamic Segmentation

Segments that refresh themselves as contact attributes and behavior change, letting you aim campaigns far more precisely than Mailjet's basic lists allow.

### Event Tracking

Pipe any custom event out of your product and turn it into a workflow trigger or a segment rule. Your app's activity becomes the engine behind your email.

### Unlimited Contacts

Keep every contact you have ever collected at no extra charge. Billing follows sending volume alone, and unlimited contacts come standard on all plans.

### EU-Hosted & GDPR-Compliant

Everything runs on EU infrastructure with GDPR-compliant processing. API access and exports give you full ownership of your data — with zero servers to look after.

### All-in-One Platform

Transactional sending, marketing campaigns, and automation live in a single product. One subscription handles it all — no bolt-on workflow tool required.

## Feature comparison

| Feature | Bitelio | Mailjet |
| --- | --- | --- |
| Free Tier | 1,000 emails/month | 200 emails/day (6,000/month) |
| Pricing Model | Free plan + tiers from $19/mo | Monthly subscription plans |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | Yes |
| Workflow Automation | Yes | No |
| Dynamic Segmentation | Yes | Basic |
| Event Tracking | Yes | Yes |
| Custom Domains | Yes | Yes |

## FAQ

### When does Mailjet make more sense than Bitelio?

Mailjet is the better fit when inbox preview testing or built-in campaign A/B testing sits at the top of your list — it is a long-established platform with a wide feature set. Pick Bitelio when workflow automation matters, or when you would rather have unlimited contacts and a flat overage rate than get pushed into a bigger tier the moment you outgrow your plan.

### How do Bitelio and Mailjet compare on price?

Bitelio starts free with 1,000 emails/month. Pro runs $19/month and covers 15,000 emails; Scale runs $99/month and covers 100,000. Go past your allowance and you simply pay a flat $1.20 per additional 1,000 emails. Mailjet sells monthly subscription tiers — Essential begins around $17/month for 15,000 emails and climbs from there. The practical difference: every Bitelio plan ships with unlimited contacts and predictable overage, so exceeding your volume never forces a tier upgrade.

### How hard is it to move from Mailjet to Bitelio?

Because the two APIs are structured differently, you will need to update your integration code. The underlying concepts — templates, webhooks, custom sending domains — translate one-to-one, though. The technical switch usually wraps up within a few hours, and contact lists and templates carry over with little rework.

### What do I get with Bitelio that Mailjet lacks?

The headline addition is multi-step workflow automation — triggers, delays, and branching conditions that power onboarding journeys and drip sequences — something Mailjet does not offer at any tier. Beyond that, every Bitelio plan comes with unlimited contacts and a flat $1.20 per extra 1,000 emails.


---

> Source: https://dev.bitelio.com/vs/mailjet

---

# https://dev.bitelio.com/vs/postmark

# All-in-one alternative for Postmark

Match Postmark on transactional reliability, then keep going: marketing campaigns, workflow automation, and segmentation in the same product — at no added cost.

## Why teams choose Bitelio

### Marketing Campaigns Included

Newsletters, launches, promos — send them all without adding a marketing vendor to your stack. One product, one invoice.

### Workflow Automation

Compose trigger-based sequences with delays and branching conditions. Welcome new users, warm up leads, win back lapsed customers — hands-free.

### Dynamic Segmentation

Slice your audience by behavior, attributes, and engagement, then reach exactly the right people at exactly the right moment.

### Unlimited Contacts

However big your list gets, storage is free on every plan — costs follow what you send, not who you keep.

### EU-Hosted & GDPR-Compliant

Hosted on EU infrastructure with GDPR-aligned processing. Your data remains yours, with API access and exports on demand.

### Simple, Transparent Pricing

A free plan covers 1,000 emails/month; Pro starts at $19/mo with 15,000 included and a flat $1.20 per extra 1,000. Transactional and marketing sends are billed identically — no split pricing.

## Feature comparison

| Feature | Bitelio | Postmark |
| --- | --- | --- |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | No |
| Workflow Automation | Yes | No |
| Dynamic Segmentation | Yes | No |

## FAQ

### What is the main difference between Bitelio and Postmark?

Postmark does one thing — transactional email — and does it well. Bitelio covers that same ground, then adds marketing campaigns, workflow automation, and dynamic segmentation. Every Bitelio plan also comes with unlimited contacts, so your bill reflects sending volume rather than list size.

### Is Bitelio as reliable as Postmark for transactional emails?

Yes. Bitelio delivers through AWS SES, matching Postmark's reputation for reliability and inbox placement. Custom domains, DKIM authentication, and detailed delivery analytics are standard on both — Bitelio simply layers marketing and automation on top.

### Can I use Bitelio for just transactional emails like Postmark?

Of course. Plenty of teams run Bitelio exactly the way they ran Postmark — transactional only. Campaigns and workflows sit ready for whenever you want them, and switching them on never costs extra.

### Why should I choose Bitelio over Postmark?

Pick Bitelio when you'd rather run product email and marketing from a single platform. Campaigns, automation, and segmentation come included, so there's no second subscription to manage — and your data stays fully in your hands through API access and on-demand exports.

### How easy is it to migrate from Postmark to Bitelio?

Very easy. Point your application at Bitelio's clean, well-documented API, verify your custom domain, and you're sending. A typical migration wraps up within a few hours.


---

> Source: https://dev.bitelio.com/vs/postmark

---

# https://dev.bitelio.com/vs/resend

# All-in-one alternative for Resend

Resend handles product email and stops there. Bitelio puts transactional sending, marketing campaigns, and automation under one roof — so you never need a second tool or a second invoice.

## Why teams choose Bitelio

### Marketing Campaigns

Broadcast to your whole list or a single segment, schedule delivery, and watch the results roll in — a capability Resend simply doesn't have.

### Workflow Automation

Chain emails into sequences driven by triggers, delays, and conditions — ideal for onboarding flows, drips, and abandoned-cart nudges.

### Dynamic Segmentation

Define segments once and let them refresh themselves from contact data and behavior, so every campaign lands with precision.

### Unlimited Contacts

Keep your entire audience on any plan at no extra charge — billing follows sending volume, never list size.

### EU-Hosted & GDPR-Compliant

Everything runs on EU infrastructure with GDPR-aligned processing, so compliance is the default — and your data exports via API whenever you want.

### All-in-One Platform

Transactional, marketing, and automation live in the same product — no stitching together tools or maintaining extra integrations.

## Feature comparison

| Feature | Bitelio | Resend |
| --- | --- | --- |
| Free Tier | 1,000 emails/month | 3,000 emails/month |
| Pricing Model | Free plan + tiers from $19/mo | Fixed subscription |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Yes | No |
| Workflow Automation | Yes | No |
| Dynamic Segmentation | Yes | No |
| Event Tracking | Yes | Yes |
| Custom Domains | Yes | Yes |

## FAQ

### When does Resend make more sense than Bitelio?

If transactional email is the only thing on your roadmap, Resend is a solid pick — it comes with a bigger free tier and a polished developer experience for that single job. The case for Bitelio starts the moment you also want marketing campaigns, automation workflows, or one platform running transactional and marketing email side by side.

### What is the pricing difference between Bitelio and Resend?

Bitelio offers a free plan with 1,000 emails/month, then Pro at $19/mo with 15,000 emails included and Scale at $99/mo with 100,000 included — beyond your allowance, you pay a transparent $1.20 per extra 1,000 emails instead of jumping tiers. Every plan includes unlimited contacts, marketing campaigns, and workflow automation at no additional cost. If you need both transactional and marketing emails, Bitelio may be more cost-effective overall since you won't need a separate marketing platform.

### How much work is switching from Resend to Bitelio?

Since the two APIs are structured differently, you'll point your code at Bitelio's endpoints and adjust the parameter format. The good news: templates, webhooks, and custom domains rest on similar concepts in both platforms, so nothing needs redesigning. Budget a few hours of engineering time for the swap.

### What does Bitelio offer that Resend doesn't?

Three things, mainly: marketing campaigns (one-off broadcasts sent to segments), workflow automation (trigger-driven, multi-step sequences with conditions), and audience segments that update themselves as contact data changes. Together they let a single platform cover both your product emails and your marketing. You also stay in charge of your data — API access and one-click exports are always available.


---

> Source: https://dev.bitelio.com/vs/resend

---

# https://dev.bitelio.com/vs/sendgrid

# All-in-one alternative for SendGrid

Clear plans, unlimited contacts, zero setup gauntlet. No gated features, no enterprise sales pitches — a platform made for developers rather than procurement departments.

## Why teams choose Bitelio

### Simple, Transparent Pricing

Start free, move to $19/mo when you're ready, and pay a flat $1.20 per extra 1,000 emails beyond your allowance. Nothing hidden, no sales calls to schedule.

### 5-Minute Setup

From signup to first send in minutes. A modern API, docs that get to the point, and no configuration rabbit holes — paste the snippet and ship.

### Marketing Included

Campaigns, automation, and segmentation come standard. With SendGrid, the same capabilities live in a separate Marketing Campaigns product that costs extra.

### Unlimited Contacts

Your list can grow as large as it likes on any plan — pricing tracks emails sent, not contacts stored.

### EU-Hosted & GDPR-Compliant

Data lives on EU infrastructure and is processed in line with GDPR. You keep full control, with API access and exports available around the clock.

### No Feature Gating

Every plan — Free included — gets campaigns, automation, and segmentation. Basic automation never hides behind an "enterprise" paywall.

## Feature comparison

| Feature | Bitelio | SendGrid |
| --- | --- | --- |
| Pricing Model | Free plan + tiers from $19/mo | Monthly subscription tiers |
| Setup Time | 5 minutes | Hours of setup work |
| Transactional Emails | Yes | Yes |
| Marketing Campaigns | Included | Separate product |
| Workflow Automation | Yes | Enterprise only |
| Dynamic Segmentation | Yes | Limited |
| API Simplicity | Modern REST | Aging, complex API |

## FAQ

### What is the difference between Bitelio and SendGrid pricing?

Bitelio has a free plan with 1,000 emails/month, then Pro at $19/mo with 15,000 emails included and Scale at $99/mo with 100,000 included. If you send more, you pay a transparent $1.20 per extra 1,000 emails — no forced tier jumps. Every plan includes unlimited contacts, marketing campaigns, and workflow automation. SendGrid's tiers charge for contact storage and sell marketing as a separate product.

### Why is SendGrid so complicated to set up?

SendGrid was designed around large-enterprise requirements: IP configuration, sender authentication, subuser hierarchies, and a legacy API you have to learn your way around before anything works. Bitelio takes the opposite approach — a clean, modern API that has developers sending within minutes.

### Does Bitelio have the same deliverability as SendGrid?

Yes. Bitelio sends through AWS SES, whose deliverability stands up to SendGrid's. Custom domains, DKIM authentication, and dedicated IPs for high-volume senders are available on both — the difference is that Bitelio hands you these capabilities without the configuration maze.

### Can I migrate from SendGrid to Bitelio?

Yes — and it's simpler than you might expect. Pull your contact list out of SendGrid, load it into Bitelio via CSV, then point your application at Bitelio's straightforward API. Most teams finish inside a day.

### What SendGrid features does Bitelio not have?

Bitelio concentrates on modern email workflows and deliberately skips the enterprise-specific extras. For roughly 95% of use cases, everything you need is already here.


---

> Source: https://dev.bitelio.com/vs/sendgrid

---

# https://dev.bitelio.com/guides/double-opt-in

# Double Opt-In: What It Is and How to Set It Up

Double opt-in confirms every subscriber with a verification email. Learn how it works, how to set it up, and why it improves deliverability and consent.

Double opt-in is a subscription process that asks every new contact to confirm their email address before they join your list. Instead of adding someone the instant they submit a form, you send them a confirmation email and wait for them to click a verification link.

That single extra step changes the quality of your entire mailing list. It filters out typos, bots, and spam traps, creates a documented record of consent, and protects the sender reputation that determines whether your future emails land in the inbox. This guide explains how double opt-in works, how it compares to single opt-in, how to set it up, and when each approach makes sense.

## Single vs Double Opt-In

Both methods start the same way-a visitor enters their email in a signup form. What happens next is where they diverge.

### Single Opt-In

With single opt-in, the address is added to your list immediately on form submission. There is no verification step. This is the fastest way to grow a list and removes all friction, but it also means every typo, disposable address, and bot signup lands directly in your database.

### Double Opt-In

With double opt-in, the address is held in a pending state until the contact clicks a confirmation link sent to their inbox. Only confirmed contacts become active subscribers. You lose the people who never confirm, but everyone who remains has proven that the address is real and that they want to hear from you.

| Factor | Single Opt-In | Double Opt-In |
| --- | --- | --- |
| List growth speed | Faster | Slower |
| List quality | Lower (typos, bots) | Higher (verified) |
| Consent evidence | Weak | Strong, timestamped |
| Deliverability risk | Higher | Lower |
| Signup friction | None | One extra click |

## Benefits of Double Opt-In

The confirmation step costs you a few signups, but it pays dividends in the metrics that actually matter for a long-term email program.

### Higher List Quality

Confirmation catches mistyped addresses (like `gmial.com`), abandoned inboxes, and automated bot signups before they ever enter your list. What you are left with is a database of real, reachable people.

### Better Deliverability

A verified list keeps bounce rates low and engagement high. Mailbox providers reward that behavior with better inbox placement, so double opt-in indirectly lifts the performance of every campaign you send.

### Documented GDPR Consent

The confirmation click produces a timestamped, IP-logged record that consent was freely and unambiguously given-exactly the audit trail privacy regulations expect you to be able to produce on request.

### Spam-Trap Protection

Spam traps and recycled addresses rarely click a confirmation link. Filtering them out at signup keeps them off your list and protects you from blocklistings that can silently tank your sending.

#### Quality Beats Quantity

A smaller list of confirmed subscribers almost always outperforms a larger unconfirmed one. Engagement, not raw size, is what drives revenue and what mailbox providers measure when deciding where to place your mail.

## How the Confirmation Flow Works

From the subscriber's point of view, double opt-in is a short, familiar sequence. Behind the scenes, your email platform is verifying the address and recording consent at each step.

### 1\. The Visitor Submits the Signup Form

A person enters their email address on your form. Rather than being added as an active subscriber, they are stored in a pending or unconfirmed state.

### 2\. A Confirmation Email Is Sent

Your platform immediately sends an automated confirmation email containing a unique verification link. This is a transactional message, so it should arrive within seconds.

### 3\. The Subscriber Clicks to Confirm

Clicking the link proves the person controls the inbox and wants to subscribe. Your system records the confirmation, typically along with a timestamp and IP address for your consent log.

### 4\. The Contact Becomes an Active Subscriber

The status flips from pending to confirmed, the contact starts receiving your campaigns, and any welcome automation or first email you have configured begins.

#### Show a Clear Confirmation Page

After the subscriber clicks, redirect them to a friendly "You're confirmed!" page. It reassures people the process worked and is a great spot to set expectations or offer a first piece of content.

## How to Set Up Double Opt-In

Most modern email platforms make double opt-in a setting you can toggle. The steps below apply whether you use a hosted form or your own custom signup.

1

### Enable Double Opt-In on Your List

In your email platform, turn on the double opt-in (or confirmed opt-in) option for the list or audience you are collecting. This tells the system to hold new contacts as pending until they confirm.

2

### Customize the Confirmation Email

Edit the automated confirmation message so it matches your brand, states clearly what the person is confirming, and features a single, obvious confirmation button.

3

### Set the Confirmation Redirect

Point the confirmation link to a thank-you or success page so subscribers get instant feedback that they are now on the list.

4

### Authenticate Your Sending Domain

Confirmation emails only work if they arrive. Make sure SPF, DKIM, and DMARC are configured so the verification message reaches the inbox instead of the spam folder.

5

### Test the Full Flow

Submit your own address, confirm the timing and appearance of the email, click the link, and verify the contact moves from pending to confirmed before you go live.

#### Pairs With Strong List-Building Habits

Double opt-in works best alongside good acquisition practices. See our [email list building guide](/guides/email-list-building) for how to collect subscribers the right way from the start.

## When Double Opt-In Is Worth It

Double opt-in is not automatically the right choice for every list. The decision comes down to how much you value list quality and consent evidence versus raw signup volume.

### Choose Double Opt-In When

-   You send marketing newsletters or promotions.
-   You collect signups from paid, cold, or high-volume traffic.
-   You operate in strict-consent regions like the EU.
-   Deliverability and long-term reputation are priorities.
-   You want defensible, timestamped proof of consent.

### Single Opt-In May Fit When

-   Signup friction directly costs conversions or revenue.
-   You are collecting emails during checkout or purchase.
-   A lead magnet or reward is delivered by that first email.
-   The list is low-risk and transactional in nature.
-   Your audience already trusts and expects your mail.

If you are unsure, err toward double opt-in for anything marketing-related. The small dip in signup count is almost always worth the protection it gives your sender reputation and your compliance posture. For a deeper look at the rules involved, read our [GDPR email compliance guide](/guides/gdpr-email-compliance).

## Best Practices for the Confirmation Email

The confirmation email is the single point of failure in a double opt-in flow. If people do not open it, understand it, or trust it, they never subscribe. Optimize it carefully.

### Send it instantly

Trigger the email the moment someone submits the form. People confirm while intent is high; a delay of even a few minutes noticeably lowers confirmation rates.

### Use a clear, expected subject line

Say exactly what it is, such as "Confirm your subscription." Avoid clever or vague subject lines that could be mistaken for spam or ignored.

### Make the call to action obvious

Feature one prominent button or link to confirm. Remove navigation, extra offers, and competing links that distract from the single action you need.

### Remind them why they are getting it

A short line like "You signed up for our newsletter" reduces confusion and reassures people who forgot they just filled out your form.

### Set expectations for what comes next

Briefly note what they will receive and how often. Clear expectations build trust and reduce future unsubscribes and spam complaints.

### Keep it plain and lightweight

A simple, mostly text confirmation email loads fast, renders everywhere, and is less likely to trip spam filters than a heavy, image-only design.

#### Don't Forget the Reminder

A meaningful share of people miss the first confirmation email. Sending one polite reminder a day or two later can recover a noticeable percentage of pending signups without annoying anyone.

## Related Guides

- [Email List Building](/guides/email-list-building): Grow a healthy, permission-based list from the ground up.

- [GDPR Email Compliance](/guides/gdpr-email-compliance): Understand consent, records, and the rules for EU subscribers.

- [Email Deliverability Guide](/guides/email-deliverability): Keep your emails landing in the inbox, not the spam folder.

---

> Source: https://dev.bitelio.com/guides/double-opt-in

---

# https://dev.bitelio.com/guides/email-api-guide

# Email API Explained: How It Works, With Code Examples | Bitelio

What an email API is and why developers use one—covering how requests flow, working examples in Node.js, Python, PHP, Ruby, and Go, best practices, and how to pick a provider.

An email API gives your application the power to send, receive, and manage email through code. From password resets and order confirmations to full marketing campaigns, it's the standard way to make email a reliable, scalable part of your software rather than a fragile afterthought.

In this guide you'll find the complete picture: the mechanics behind email APIs, ready-to-run code in five languages, hard-won best practices, and a framework for picking the right provider.

## What is an Email API?

An email API is an HTTP interface for sending and managing email—no hand-configured SMTP servers required. The provider absorbs all the messy delivery mechanics behind clean endpoints: one request sends the message, and webhooks report back on what happened to it.

### SMTP (Traditional)

-   • The raw protocol for transmitting mail
-   • Connection management falls on you
-   • Error handling is your problem too
-   • Little visibility into delivery outcomes
-   • Noticeably harder to implement
-   • Port 25, 587, or 465

### Email API (Modern)

-   • RESTful interface over HTTP
-   • Zero connection bookkeeping
-   • Errors come back as structured responses
-   • Tracking and analytics out of the box
-   • Far quicker to integrate
-   • Standard HTTP/HTTPS

#### When to Use Email APIs

Transactional messages (password resets, order confirmations), automated notifications, and code-driven campaigns are exactly what email APIs were built for. Any time software is the one hitting "send," an API beats raw SMTP in nearly every scenario.

## How Email APIs Work

### 1\. Authentication

Each request carries an API key—typically in a header—that tells the service who you are and confirms you're allowed in.

### 2\. Make HTTP Request

You POST a JSON payload to the endpoint containing everything about the message: recipient, subject, body, and any extras.

### 3\. API Validates & Queues

The service checks the payload, drops the message into its delivery queue, and hands back a response containing the email's ID and current status.

### 4\. Email Delivery

From there the provider takes over—negotiating SMTP connections, retrying failures, and getting the message to the recipient's mail server.

### 5\. Webhooks & Tracking

Delivery events (delivered, bounced, opened, clicked) stream back to you as webhook calls, and the API lets you look up any email's status on demand.

## Email API Code Examples

The snippets below show a Bitelio API send in five popular languages:

### JavaScript / Node.js

Node.js Example

```
// Using fetch (Node.js 18+ or with node-fetch)
const response = await fetch('https://api.bitelio.com/v1/send', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': 'Bearer YOUR_API_KEY'
  },
  body: JSON.stringify({
    to: 'user@example.com',
    subject: 'Welcome to our platform!',
    body: '<h1>Welcome!</h1><p>Thanks for signing up.</p>',
    // Optional fields
    from: 'noreply@yourdomain.com',
    name: 'Your Company',
    replyTo: 'support@yourdomain.com'
  })
});

const data = await response.json();

if (response.ok) {
  console.log('Email sent!', data.emailId);
} else {
  console.error('Failed to send:', data.error);
}
```

### Python

Python Example

```
import requests

response = requests.post(
    'https://api.bitelio.com/v1/send',
    headers={
        'Content-Type': 'application/json',
        'Authorization': 'Bearer YOUR_API_KEY'
    },
    json={
        'to': 'user@example.com',
        'subject': 'Welcome to our platform!',
        'body': '<h1>Welcome!</h1><p>Thanks for signing up.</p>',
        'from': 'noreply@yourdomain.com',
        'name': 'Your Company'
    }
)

if response.status_code == 200:
    data = response.json()
    print(f"Email sent! ID: {data['emailId']}")
else:
    print(f"Error: {response.json()['error']}")
```

### PHP

PHP Example

```
<?php
$ch = curl_init('https://api.bitelio.com/v1/send');

curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'Content-Type: application/json',
    'Authorization: Bearer YOUR_API_KEY'
]);

curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode([
    'to' => 'user@example.com',
    'subject' => 'Welcome to our platform!',
    'body' => '<h1>Welcome!</h1><p>Thanks for signing up.</p>',
    'from' => 'noreply@yourdomain.com',
    'name' => 'Your Company'
]));

$response = curl_exec($ch);
$httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

$data = json_decode($response, true);

if ($httpCode === 200) {
    echo "Email sent! ID: " . $data['emailId'];
} else {
    echo "Error: " . $data['error'];
}
?>
```

### Ruby

Ruby Example

```
require 'net/http'
require 'json'

uri = URI('https://api.bitelio.com/v1/send')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

request = Net::HTTP::Post.new(uri.path)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_KEY'
request.body = {
  to: 'user@example.com',
  subject: 'Welcome to our platform!',
  body: '<h1>Welcome!</h1><p>Thanks for signing up.</p>',
  from: 'noreply@yourdomain.com',
  name: 'Your Company'
}.to_json

response = http.request(request)
data = JSON.parse(response.body)

if response.code.to_i == 200
  puts "Email sent! ID: #{data['emailId']}"
else
  puts "Error: #{data['error']}"
end
```

### Go

Go Example

```
package main

import (
    "bytes"
    "encoding/json"
    "fmt"
    "io"
    "net/http"
)

type EmailRequest struct {
    To      string `json:"to"`
    Subject string `json:"subject"`
    Body    string `json:"body"`
    From    string `json:"from"`
    Name    string `json:"name"`
}

func main() {
    email := EmailRequest{
        To:      "user@example.com",
        Subject: "Welcome to our platform!",
        Body:    "<h1>Welcome!</h1><p>Thanks for signing up.</p>",
        From:    "noreply@yourdomain.com",
        Name:    "Your Company",
    }

    jsonData, _ := json.Marshal(email)

    req, _ := http.NewRequest("POST", "https://api.bitelio.com/v1/send", bytes.NewBuffer(jsonData))
    req.Header.Set("Content-Type", "application/json")
    req.Header.Set("Authorization", "Bearer YOUR_API_KEY")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        fmt.Println("Error:", err)
        return
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)

    if resp.StatusCode == 200 {
        var result map[string]interface{}
        json.Unmarshal(body, &result)
        fmt.Printf("Email sent! ID: %v\n", result["emailId"])
    } else {
        fmt.Println("Error:", string(body))
    }
}
```

## Common Email API Features

### Sending Features

-   • One-off sends and batch dispatch
-   • Both HTML and plain-text bodies
-   • File attachments
-   • CC and BCC support
-   • Custom header injection
-   • Server-side template rendering
-   • Send scheduling

### Tracking & Analytics

-   • Per-message delivery status
-   • Open tracking
-   • Click tracking
-   • Automatic bounce detection
-   • Spam complaint visibility
-   • Unsubscribe handling
-   • Live analytics dashboards

### Webhooks & Events

-   • Delivery confirmations
-   • Bounce callbacks
-   • Complaint alerts
-   • Unsubscribe notifications
-   • Open and click event streams
-   • User-defined event triggers

### Management Features

-   • Suppression list controls
-   • Contact administration
-   • Domain verification tooling
-   • Template libraries
-   • API key lifecycle management
-   • Rate limiting

## Email API Best Practices

1

### Secure Your API Keys

Keys belong in environment variables, never in source. Maintain distinct keys per environment—dev, staging, production—rotate them on a schedule, and revoke instantly at any sign of exposure.

2

### Implement Proper Error Handling

Each class of HTTP status deserves its own response:

-   200: Success
-   400-499: Client-side problems (malformed request, failed validation) - retrying won't help
-   500-599: Server-side failures - retry using exponential backoff
-   429: You've hit the rate limit - pause, then try again later

3

### Use Webhooks for Delivery Status

Skip the polling loop. Register webhooks and let delivery events (delivered, bounced, opened, clicked) come to you in real time—less load on both sides and faster information.

4

### Respect Rate Limits

Build throttling into your own code rather than bouncing off the provider's ceiling. Queue outgoing mail, dispatch in batches, and treat any 429 as a signal to back off exponentially.

5

### Validate Email Addresses

Check address format before the request ever leaves your app, and watch for the classic typos. For higher stakes, a dedicated validation API can confirm deliverability ahead of time.

6

### Use Templates

Keep email templates on the provider's side instead of baking HTML into your codebase. Marketers and support staff can then tweak copy without waiting on a deploy.

7

### Monitor Deliverability Metrics

Keep bounce rates, complaint rates, and engagement under continuous watch, with alerts wired up for anything unusual. Catching deliverability drift early is always cheaper than fixing it late.

8

### Test in Sandbox/Development Mode

Develop against sandbox or test mode, and rehearse the unhappy paths—error responses, retry behavior, webhook processing—well before anything touches production.

9

### Log API Requests & Responses

Record every exchange with the API—minus secrets such as API keys. Those logs become invaluable when debugging a delivery mystery or analyzing your sending patterns.

10

### Handle Timeouts

Give every API call a sensible timeout—10-30 seconds is typical—and never make an end user wait on the email provider. Push sends onto an async queue whenever latency matters.

## Choosing an Email API Provider

When it's time to pick a provider, weigh your options against these criteria:

### Deliverability Reputation

Prioritize providers whose infrastructure has a proven inbox-placement record. An email API that routinely delivers to spam isn't saving you anything.

### Feature Set

Match capabilities to requirements: templates, webhooks, analytics, scheduling, attachments, and so on. Note that some services are transactional-first while others lean toward marketing.

### Pricing Model

Read the pricing page carefully—per-message rates, tier structures, overage charges. Model the cost at your projected volume, and stay alert to hidden fees or steep jumps as you scale.

### Developer Experience

Thorough docs, an SDK for your stack, error messages that actually explain themselves, and support that answers—these things compound into weeks of saved integration time.

### Scalability & Reliability

Ask the hard questions: will they absorb your traffic spikes? What SLA do they commit to? Is there real redundancy and failover behind the API?

### Compliance & Security

Confirm the provider meets GDPR, CAN-SPAM, and whatever regulations govern your market, and look for recognized security attestations like SOC 2 or ISO 27001.

## Related Email Guides

- [Transactional vs Marketing Email](/guides/transactional-vs-marketing-email): Know which email type you're sending via API.

- [Email Deliverability](/guides/email-deliverability): Get your API-sent mail into the inbox.

- [Email Sender Reputation](/guides/email-sender-reputation): Keep the reputation behind your sends healthy.

---

> Source: https://dev.bitelio.com/guides/email-api-guide

---

# https://dev.bitelio.com/guides/email-authentication

# Email Authentication Explained: SPF, DKIM & DMARC

Email authentication explained: how SPF, DKIM, and DMARC work together to stop spoofing, protect your domain, and get your emails into the inbox.

Email authentication is how receiving mail servers decide whether a message that claims to be from your domain is genuine. It is built on three DNS-based standards—SPF, DKIM, and DMARC—that work as a system to stop spoofing and get your legitimate email into the inbox.

This guide is the hub for all three. We will cover why authentication matters, what each protocol does, and most importantly how they fit together—then link you to the in-depth guide and free checker for each one.

## Why Email Authentication Matters

Without authentication, anyone can put your domain in the From address of an email. Receiving servers have no reliable way to tell a real message from a forgery, so they either let spoofed mail through— damaging your brand and your customers—or treat everything from your domain with suspicion. Authentication solves both problems at once.

### Protects Against Spoofing

Attackers routinely impersonate trusted domains to launch phishing and business email compromise attacks. Authentication lets receivers reject mail that is not genuinely from you, protecting your recipients and your reputation.

### Improves Deliverability

Mailbox providers weigh authentication heavily when deciding between the inbox and the spam folder. Properly authenticated mail is more trusted, which means better inbox placement and fewer messages lost to filtering.

### Required by Major Providers

Since February 2024, Google and Yahoo require SPF, DKIM, and a DMARC policy for anyone sending more than 5,000 messages a day to their users. Authentication has moved from best practice to baseline requirement.

### Gives You Visibility

DMARC reporting shows you every source sending email as your domain—including shadow IT and abuse—so you can spot problems and lock down your sending before they cost you.

#### Authentication Is the Foundation, Not the Whole House

Passing SPF, DKIM, and DMARC removes a major deliverability blocker, but it does not guarantee the inbox. Sender reputation, content quality, and engagement still matter. Authentication is the entry ticket that makes the rest of your work count.

## The Three Protocols at a Glance

Each protocol answers a different question about an incoming email. Here is how they compare:

| Protocol | What it checks | DNS record |
| --- | --- | --- |
| SPF | Which servers may send email for your domain | TXT at root domain |
| DKIM | That the message was signed and not altered | TXT at selector.\_domainkey |
| DMARC | What to do on failure, plus reporting | TXT at \_dmarc |

### SPF: Authorizing Your Senders

SPF (Sender Policy Framework) is a published list of the servers allowed to send email using your domain. You add a single TXT record to your root domain naming each authorized service, and receiving servers reject or flag mail that arrives from an IP address that is not on the list. SPF validates the sending server, but it can break when a message is forwarded, which is exactly why DKIM exists alongside it. [Read the full SPF guide](/guides/what-is-spf) or [test your record with the SPF checker](/tools/spf-checker).

### DKIM: Signing Your Messages

DKIM (DomainKeys Identified Mail) attaches a cryptographic signature to every outgoing message. Your mail server signs with a private key, and receivers fetch the matching public key from a TXT record at `selector._domainkey.yourdomain.com` to verify the signature. Because the signature covers the headers and body, DKIM proves the message was not tampered with in transit—and unlike SPF it survives most forwarding. [Read the full DKIM guide](/guides/what-is-dkim) or [verify your key with the DKIM checker](/tools/dkim-checker).

### DMARC: Setting the Policy

DMARC (Domain-based Message Authentication, Reporting, and Conformance) sits on top of SPF and DKIM. It tells receiving servers what to do when a message fails authentication—monitor (`p=none`), quarantine (`p=quarantine`), or reject (`p=reject`)—and it sends you aggregate reports about every source using your domain. DMARC also enforces alignment, ensuring the authenticated domain matches the one your recipients actually see. [Read the full DMARC guide](/guides/what-is-dmarc) or [validate your policy with the DMARC checker](/tools/dmarc-checker).

## How SPF, DKIM & DMARC Work Together

The three protocols are not alternatives—they are layers. Each one covers a weakness in the others, and DMARC is the piece that turns them into a single, enforceable system. Here is what happens when a receiving server evaluates one of your messages:

### 1\. SPF and DKIM Run First

The receiver checks whether the sending IP is authorized by your SPF record and whether the DKIM signature on the message is valid. Either check can pass or fail independently.

### 2\. DMARC Checks Alignment

DMARC requires that a passing SPF or DKIM result _aligns_ with the domain shown in the visible From header. Alignment is what stops an attacker from passing SPF on their own domain while spoofing yours in the From line. DMARC passes if at least one of SPF or DKIM passes and aligns.

### 3\. The Policy Decides the Outcome

If DMARC passes, the message is delivered normally. If it fails, the receiver applies your published policy—nothing, quarantine, or reject—so you control how forgeries are handled instead of leaving it to each provider's guesswork.

### 4\. Reports Close the Loop

Receivers send DMARC aggregate reports back to you, revealing every source sending as your domain. You use these to authorize legitimate services you forgot about and to spot abuse before tightening your policy.

In practice, all three live side by side in your DNS as TXT records at different locations:

SPF, DKIM & DMARC records for one domain

```
# SPF — published at the root domain
example.com.                 IN TXT  "v=spf1 include:spf.bitelio.com ~all"

# DKIM — published at the selector your provider gives you
bit._domainkey.example.com.  IN TXT  "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEB..."

# DMARC — published at the _dmarc subdomain
_dmarc.example.com.          IN TXT  "v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
```

#### Why You Need All Three

SPF breaks on forwarding, DKIM says nothing about how to treat failures, and DMARC cannot pass without an aligned SPF or DKIM result behind it. Deploy all three and each protocol covers the others' blind spots—giving you the overlapping protection mailbox providers now expect.

## Email Authentication Setup Checklist

Set the three protocols up in order—SPF and DKIM first, then DMARC—so DMARC has something aligned to build on.

1

### Inventory Every Sending Source

List every service that sends email as your domain: your email platform, CRM, help desk, marketing tools, and billing system. Missing one is the most common reason authentication fails later.

2

### Publish One SPF Record

Combine every authorized sender into a single SPF TXT record at your root domain, ending in `~all`. Remember the 10 DNS lookup limit—do not create more than one SPF record.

3

### Enable and Publish DKIM

Have each sending service generate a DKIM key pair, then publish the public key at the selector it provides. Enable signing on every source so no legitimate mail goes out unsigned.

4

### Start DMARC in Monitor Mode

Add a DMARC record at `_dmarc.yourdomain.com` with `p=none` and a `rua` reporting address. This gathers data without affecting delivery.

5

### Review Reports, Then Tighten

Read DMARC reports for two to four weeks, fix any legitimate source that is failing, then move your policy from `p=none` to `p=quarantine` and finally `p=reject`.

#### Bitelio Sets This Up For You

When you add a domain in Bitelio, we generate the exact SPF and DKIM records to paste into your DNS and verify them automatically—so you can focus on getting DMARC to a reject policy with confidence.

## How to Verify Your Setup

Never assume a record is live just because you saved it—DNS changes can take time to propagate and typos are easy. Verify each protocol independently:

- [SPF Checker](/tools/spf-checker): Confirm your record parses correctly and stays under the 10 DNS lookup limit.

- [DKIM Checker](/tools/dkim-checker): Verify the public key resolves for the selector your provider signs with.

- [DMARC Checker](/tools/dmarc-checker): Validate your policy syntax and reporting addresses.

As a final end-to-end test, send a message to a Gmail or Outlook account, open the original headers, and look for `spf=pass`, `dkim=pass`, and `dmarc=pass`. When all three pass and align, your domain is properly authenticated.

## Deep Dives: SPF, DKIM & DMARC

Ready to configure each protocol in detail? Start with the guide for whichever one you are setting up next.

- [What is SPF?](/guides/what-is-spf): Authorize your sending servers with a single SPF record.

- [What is DKIM?](/guides/what-is-dkim): Sign every message so receivers can verify it is unaltered.

- [What is DMARC?](/guides/what-is-dmarc): Set a policy and read reports to enforce authentication.

---

> Source: https://dev.bitelio.com/guides/email-authentication

---

# https://dev.bitelio.com/guides/email-bounce-rate

# Email Bounce Rate Explained: Reduce Hard & Soft Bounces

What email bounce rate means, how hard bounces differ from soft ones, and the practical steps that keep bounces low and your sender reputation intact.

Your email bounce rate tells you what share of your messages never made it to their destination. Some failures are fleeting, others are final—but let bounces pile up and your sender reputation takes a hit that drags down deliverability across the board.

Knowing which kind of bounce you're dealing with, and how to keep them rare, is one of the foundations of a healthy sending program.

## What is Email Bounce Rate?

Simply put, email bounce rate is the fraction of your outgoing mail that receiving servers turned away rather than accepted.

Bounce Rate Formula

```
Bounce Rate = (Bounced Emails ÷ Sent Emails) × 100

Example:
- Sent: 10,000 emails
- Bounced: 150 emails

Bounce Rate = (150 ÷ 10,000) × 100 = 1.5%
```

<2%

### Excellent

A well-maintained list with solid hygiene habits

2-5%

### Concerning

List quality is slipping—time to intervene

\>5%

### Critical

Active damage to your sender reputation is underway

## Hard Bounces vs Soft Bounces

Bounces come in two flavors, and treating them the same is a mistake. How you respond depends entirely on which type you're facing.

### Hard Bounces (Permanent)

A hard bounce means delivery failed for a reason that won't go away. No amount of retrying will get mail to these addresses.

#### Common Causes:

-   • The mailbox doesn't exist
-   • The domain doesn't resolve
-   • The receiving server has permanently refused your mail
-   • The address is malformed

Action Required:

**Purge right away.** These addresses must never receive another send—each repeat attempt tells providers you don't maintain your list.

### Soft Bounces (Temporary)

A soft bounce is a passing failure: the address itself is fine, but something on the receiving end blocked delivery this time around.

#### Common Causes:

-   • The recipient's mailbox has run out of space
-   • The receiving server is offline or overloaded
-   • Your message exceeds size limits
-   • Temporary trouble on the recipient's server

Action Required:

**Let retries run.** Platforms typically reattempt for 24-72 hours. If an address soft bounces 3-5 times in a row, reclassify it as a hard bounce and drop it.

#### Bounce vs Block

A **block** is different from a bounce: the receiving server deliberately refuses your mail because of reputation or content concerns, not because the address is bad. Blocks are a deliverability warning sign, since they typically affect everything you send to that domain.

## Common Bounce Reasons & Error Codes

| Error Type | Reason | Type | Action |
| --- | --- | --- | --- |
| 550 | Mailbox unavailable | Hard | Remove |
| 551 | User not local/Invalid address | Hard | Remove |
| 552 | Mailbox full | Soft | Retry |
| 553 | Mailbox name invalid | Hard | Remove |
| 554 | Transaction failed | Varies | Investigate |
| 421 | Service not available | Soft | Retry |
| 450 | Mailbox busy | Soft | Retry |

## How to Reduce Email Bounce Rates

1

### Use Double Opt-In

Have every new subscriber click a confirmation link before joining your list. This single step proves the address works, is actively monitored, and truly belongs to the signup. Programs adopting double opt-in see bounce rates fall by 50-70%.

2

### Validate Email Addresses

Add real-time validation to your signup forms so bad addresses never enter the list. Your checks should cover:

-   Basic format (an @ sign and a plausible domain)
-   Whether the domain publishes MX records
-   Frequent typos (gmial.com → gmail.com)
-   Disposable address domains (block them if it suits your use case)

3

### Remove Hard Bounces Immediately

Set up automatic suppression for every hard bounce and keep those addresses out permanently. Each repeat send to a dead address broadcasts sloppy list management to mailbox providers.

4

### Clean Your List Regularly

Every 6-12 months, either re-engage or retire subscribers who've gone quiet. Addresses decay naturally (15- 20% per year), so periodic cleanups stop bounces from silently accumulating.

5

### Never Buy Email Lists

A purchased list arrives with 20-40% dead addresses and nobody on it expecting your mail. It will wreck both your bounce rate and your reputation in one stroke. Organic growth takes longer but pays off many times over.

6

### Monitor Soft Bounces

Keep an eye on addresses that soft bounce again and again. Once one racks up 3-5 consecutive failures across campaigns, reclassify it as a hard bounce and take it off the list.

7

### Optimize Email Size

Size-limit rejections are avoidable: stay under 100KB per message by compressing images, trimming markup, and linking to files rather than attaching them.

8

### Maintain Consistent Sending

A steady cadence keeps your list current. Go silent for 3+ months and bounces climb—addresses expire in the meantime, and subscribers who've forgotten you are quicker to complain.

## How Bounce Rate Affects Deliverability

The consequences of an elevated bounce rate reach well beyond the failed messages themselves:

### Damaged Sender Reputation

Mailbox providers watch your bounce numbers closely. Elevated rates read as neglected lists and careless sending, pulling down your reputation score—and once that slips, even mail to perfectly good addresses starts getting filtered to spam.

### Spam Trap Hits

Abandoned addresses often get repurposed as spam traps—decoys designed to expose senders who skip list maintenance. Hit one and you risk a blacklist entry that cripples delivery to every recipient you have.

### IP/Domain Blacklisting

Sustain a high bounce rate long enough and mailbox providers or third-party blacklist operators may list your IP or domain outright—after which getting any mail through becomes a serious struggle.

### Reduced Engagement

Bounce problems and engagement problems travel together. When providers see a big chunk of your list is invalid, they discount the rest of your mail too—trust erodes across the whole program.

#### Recovery Takes Time

A reputation wounded by bounce spikes doesn't heal overnight—expect weeks or months of disciplined, clean sending before providers trust you again. It's far cheaper to prevent the damage in the first place.

## Monitoring & Managing Bounces

### What to Track

-   • Total bounce rate (goal: <2%)
-   • Hard bounces as their own metric
-   • Soft bounces and how often retries succeed
-   • Per-campaign bounce rates
-   • How bounce rates trend over time
-   • The specific error codes behind each bounce

### Automated Actions

-   • Suppress hard bounces the instant they occur
-   • Retry soft bounces 3-5 times within 72 hours
-   • Drop addresses that keep soft bouncing
-   • Fire alerts when bounces cross your threshold
-   • Generate weekly bounce summaries
-   • Check addresses for validity at signup

## Related Email Guides

- [Email Deliverability](/guides/email-deliverability): Your full playbook for landing in the inbox.

- [Email Sender Reputation](/guides/email-sender-reputation): Earn and protect the reputation providers assign you.

- [Email Marketing Best Practices](/guides/email-marketing-best-practices): The end-to-end email marketing playbook.

---

> Source: https://dev.bitelio.com/guides/email-bounce-rate

---

# https://dev.bitelio.com/guides/email-bounces-explained

# Hard vs Soft Bounces: Email Bounces Explained

Learn what an email bounce is, how hard and soft bounces differ, what common bounce codes mean, and how to handle bounces to protect deliverability.

An email bounce is a message that could not be delivered and is returned to the sender with an explanation of why. Every email program produces bounces, but how you respond to them determines whether they stay a harmless side effect or quietly erode your deliverability.

This guide explains what a bounce actually is, how hard bounces differ from soft bounces, what the underlying status codes mean, and the practices that keep bounces from damaging your sender reputation.

## What Is an Email Bounce?

When you send an email, your sending server (the Mail Transfer Agent, or MTA) hands the message off to the recipient's mail server. If that server refuses or fails to accept the message, it returns a bounce notification—formally called a Non-Delivery Report (NDR) or Delivery Status Notification (DSN). That notification contains a status code and a human-readable reason describing exactly what went wrong.

A bounce is different from a rejection you never see. Some messages are silently dropped or filtered into spam without any notice. A bounce, by contrast, is an explicit signal you can act on—which is why capturing and processing bounce data is one of the most valuable things a sender can do.

Bounces also arrive at two different moments. A synchronous bounce happens during the initial SMTP conversation, when the receiving server rejects the message before accepting it. An asynchronous bounce arrives minutes or hours later: the server accepted the message, then discovered it could not deliver it and emailed a notification back to your return-path address. A good email platform captures both and feeds them into the same suppression and retry logic automatically.

Example bounce notification (simplified)

```
Final-Recipient: rfc822; jordan@example.com
Action: failed
Status: 5.1.1
Diagnostic-Code: smtp; 550 5.1.1 <jordan@example.com>
  User unknown; recipient address rejected
```

#### Bounces Are Feedback, Not Failure

A single bounce is normal. The problem is ignoring them. Every bounce tells you something about your list quality or your sending setup, and acting on that feedback is what protects long-term deliverability.

## Hard Bounces vs Soft Bounces

Every bounce is classified as either hard or soft. The distinction is simple but critical: hard bounces are permanent, and soft bounces are temporary. How you treat each type is completely different.

### Hard Bounces (Permanent Failures)

A hard bounce means the message can never be delivered to that address. The failure will not resolve on its own, so retrying is pointless and actively harmful. Common causes include:

-   The mailbox does not exist (a typo, or an address that was deleted)
-   The domain is invalid or no longer registered
-   The receiving server permanently blocks your message
-   The address was fabricated or belongs to a spam trap

Hard bounces should be removed from your list immediately and never emailed again. Continuing to send to them is the single fastest way to wreck your sender reputation.

### Soft Bounces (Temporary Failures)

A soft bounce means delivery failed for now but might succeed on a later attempt. The address itself is usually valid. Common causes include:

-   The recipient's mailbox is full
-   The receiving server is temporarily down or overloaded
-   The message is too large for the recipient's size limits
-   The receiving server is greylisting new senders (a deliberate delay)

Email platforms automatically retry soft bounces on a schedule, typically for 24 to 72 hours. If an address keeps soft bouncing across several sends, most systems eventually convert it to a hard bounce and suppress it.

### Hard vs Soft Bounce Comparison

| Attribute | Hard Bounce | Soft Bounce |
| --- | --- | --- |
| Nature | Permanent | Temporary |
| Status code | 5.x.x (e.g. 550) | 4.x.x (e.g. 450) |
| Typical cause | Invalid or blocked address | Full mailbox, server down, message too large |
| Should you retry? | No | Yes, for a limited window |
| Correct action | Suppress immediately | Retry, then suppress if it persists |

## Common Bounce Codes and Causes

Bounce notifications carry SMTP status codes that tell you exactly why a message failed. The first digit is the most important: a `5` means a permanent failure (hard bounce), while a `4` means a temporary failure (soft bounce). Here are the codes you will encounter most often.

| Code | Meaning | Type |
| --- | --- | --- |
| 550 / 5.1.1 | Mailbox does not exist (user unknown) | Hard |
| 5.1.2 | Invalid or nonexistent domain | Hard |
| 554 / 5.7.1 | Message refused or blocked as spam/policy | Hard |
| 450 / 4.2.1 | Mailbox temporarily unavailable | Soft |
| 452 / 4.2.2 | Mailbox full / over quota | Soft |
| 421 / 4.4.1 | Server unavailable or not responding | Soft |
| 552 / 5.3.4 | Message exceeds size limit | Soft |

#### Read the Text, Not Just the Number

Codes are not perfectly standardized across providers. A mailbox-full error can be returned as either `452` or `552`, and blocks are sometimes reported with vague messages. Always read the diagnostic text alongside the numeric code before deciding whether to suppress or retry an address.

## How Bounces Affect Reputation and Deliverability

Mailbox providers watch your bounce rate closely because it is one of the clearest signals of list quality. A sender who repeatedly hits invalid addresses looks either careless or malicious—both spammers and negligent senders share the same symptom of emailing addresses that do not exist.

### Lower Sender Reputation

Every hard bounce chips away at the reputation score that Gmail, Outlook, and others assign to your domain and IP. A damaged reputation means worse inbox placement across the board.

### More Mail in Spam

As reputation drops, providers route more of your messages—including those to valid, engaged recipients—straight to the spam folder, quietly reducing the reach of every campaign.

### Blocklisting Risk

Sustained high hard bounce rates, especially from hitting spam traps, can land your sending domain or IP on a blocklist, which can halt delivery to entire mailbox providers at once.

### Account Suspension

Most reputable email platforms automatically pause or suspend accounts whose hard bounce rates climb past 5 to 10%, protecting the shared reputation of their sending infrastructure.

For benchmarks, thresholds, and tactics focused specifically on the metric itself, see our companion guide on [email bounce rate](/guides/email-bounce-rate).

## How to Handle Email Bounces

Handling bounces well comes down to reacting correctly to each type and preventing them from occurring in the first place. Here is the workflow every sender should have in place.

### Suppress Hard Bounces Automatically

A suppression list is a record of addresses you must never email again. As soon as an address hard bounces, add it to suppression so it is silently excluded from every future send. This is the most important control you have—it stops a single bad address from bouncing repeatedly and compounding reputation damage.

### Retry Soft Bounces, Then Suppress

Let your platform retry soft bounces on a backoff schedule for a defined window, usually 24 to 72 hours. If an address soft bounces on every attempt across several campaigns, treat it as effectively dead and move it to suppression. Persistent soft bounces are often abandoned mailboxes that will never recover.

### Clean Your List Regularly

Roughly 15 to 20% of email addresses go stale every year as people change jobs and abandon accounts. Run a list-cleaning pass every 6 to 12 months to remove long-inactive contacts and re-verify questionable addresses before they turn into bounces or spam traps.

### Prevent Bounces at the Source

The cheapest bounce is the one that never happens. Stop bad addresses from entering your list in the first place:

-   Use double opt-in so every subscriber confirms a real, working address
-   Validate email syntax and domain (MX records) on your signup forms in real time
-   Never buy or scrape lists—purchased lists routinely contain 20 to 40% invalid addresses
-   Warm up new sending domains and IPs gradually to earn trust before scaling volume

#### Bitelio Manages Bounces for You

Bitelio automatically processes bounce notifications, suppresses hard bounces, retries soft bounces, and keeps every suppressed address out of future sends—so a bad address can only ever bounce once.

## Related Deliverability Guides

- [Email Bounce Rate](/guides/email-bounce-rate): Benchmarks and proven tactics to reduce your bounce rate.

- [Email Deliverability](/guides/email-deliverability): The complete guide to landing in the inbox, not spam.

- [Email Warmup](/guides/email-warmup): Build sender reputation on a new domain or IP the right way.

---

> Source: https://dev.bitelio.com/guides/email-bounces-explained

---

# https://dev.bitelio.com/guides/email-click-through-rate

# Email Click-Through Rate: Benchmarks & CTA Tactics That Work

What drives email click-through rate, how your CTR compares to industry benchmarks, and field-tested CTA techniques for turning opens into clicks.

Click-through rate (CTR) tells you what share of recipients clicked at least one link inside your email. Where open rate grades your subject line, email click-through rate grades everything after the open—your content, your offer, and above all your calls-to-action.

A strong CTR means subscribers are getting real value and taking steps toward converting. Below you'll find the benchmarks, the factors at play, and the CTA techniques that consistently earn more clicks.

## What is Email Click-Through Rate?

Formally, CTR is the share of delivered messages in which the recipient clicked at least one link.

CTR Formula

```
CTR = (Unique Clicks ÷ Delivered Emails) × 100

Example:
- Sent: 10,000 emails
- Delivered: 9,800 emails
- Unique Clicks: 294

CTR = (294 ÷ 9,800) × 100 = 3.0%
```

CTOR Formula

```
CTOR (Click-to-Open Rate) = (Unique Clicks ÷ Unique Opens) × 100

Example:
- Unique Opens: 2,450
- Unique Clicks: 294

CTOR = (294 ÷ 2,450) × 100 = 12.0%
```

#### CTR vs CTOR

The two metrics answer different questions. **CTR** reflects the whole funnel—deliverability and opens included—while **CTOR** looks only at people who opened, isolating how well the content itself performed. Track both: CTR for the big picture, CTOR when tuning your content.

## CTR Benchmarks by Industry

| Industry | Average CTR | Good CTR | Average CTOR |
| --- | --- | --- | --- |
| SaaS / Technology | 2-3% | 4%+ | 10-15% |
| E-commerce / Retail | 3-5% | 6%+ | 12-18% |
| Media / Publishing | 4-6% | 7%+ | 15-20% |
| Financial Services | 2-4% | 5%+ | 10-14% |
| Non-Profit | 2-4% | 5%+ | 10-16% |
| Education | 3-5% | 6%+ | 12-17% |

#### Context Matters

Email type moves the needle enormously: promotions average 2-3%, newsletters 4-6%, transactional messages 10-15%, and behavior-triggered emails 15-30%. Always benchmark like against like rather than lumping every campaign together.

## What Affects Click-Through Rates?

### 1\. Call-to-Action (CTA) Design

How your CTA looks, where it sits, and what it says all shape click behavior. A bold, well-placed button with action-driven copy leaves generic "Click here" links far behind.

### 2\. Email Relevance

Content matched to the recipient earns 2-3x the clicks of a generic blast. Segmentation and personalization are how you guarantee that match.

### 3\. Value Proposition

Nobody clicks without a reason. Give one: exclusive material, a time-boxed deal, or a direct answer to a problem they have. The stronger the promised payoff, the more clicks follow.

### 4\. Mobile Optimization

More than 60% of email reading happens on phones. Skip mobile optimization—tiny links, broken layouts—and expect your mobile CTR to drop by half.

### 5\. Content Scannability

Readers skim, they don't study. Headers, bullets, and generous whitespace let skimmers locate your CTA in seconds—which is exactly how long you have.

### 6\. Number of CTAs

Every extra CTA splits the reader's attention. Emails built around a single primary CTA convert 371% better than emails where several actions compete.

## How to Increase Email Click-Through Rates

1

### Use Clear, Action-Oriented CTA Copy

Tell readers precisely what the click delivers. The formula is simple: an action verb plus a concrete benefit.

✓"Download your free guide"

✓"Start your 14-day free trial"

✓"Get 20% off today only"

✗"Click here"

✗"Learn more"

2

### Design Prominent CTA Buttons

What good buttons have in common:

-   A color that pops against the rest of the email
-   A tap-friendly size on mobile (44x44px at minimum)
-   Breathing room—whitespace that draws the eye toward them
-   Real text rather than an image (faster to load, accessible to all)
-   A repeat of the main CTA at top and bottom when the email runs long

3

### Create a Single, Clear Focus

Give every email exactly one job. When several CTAs fight for attention, total clicks drop—so build the whole message as a runway toward one action.

4

### Personalize Content

"Hi \[Name\]" is table stakes, not personalization. Real relevance comes from behavior: purchases, browsing, stated preferences. It pays off—personalized CTAs deliver 202% higher CTR.

5

### Optimize for Mobile

The mobile essentials:

-   Responsive layouts that reshape to any screen
-   Big, thumbable buttons instead of fine-print links
-   A single column that scrolls naturally
-   Tight copy—phone readers scan even faster
-   At least one CTA visible before any scrolling

6

### Use Urgency and Scarcity (Authentically)

A real deadline or genuinely limited stock gets people moving—"Sale ends tonight" and "Only 5 spots remaining" are powerful when they're true. Manufactured urgency, on the other hand, burns trust the moment readers catch on.

7

### Segment Your Audience

Break your list into groups—by behavior, interest, or demographics—and speak to each one directly. Segmented sends earn 3x the CTR of untargeted blasts.

8

### Include Preview/Teaser Content

Reveal enough to intrigue, hold back enough to reward the click. Product shots, a striking statistic, or the opening of an article all pull readers through—"Read the full article" beats a bare headline.

9

### A/B Test CTAs

Variables worth testing, one at a time:

-   Wording ("Get started" versus "Start free trial")
-   Color (on-brand versus maximum contrast)
-   Position (top, middle, or bottom of the email)
-   Count (a single CTA versus several)
-   Dimensions and shape of the button itself

10

### Improve Email-Landing Page Match

Whatever the email promises, the landing page must deliver instantly. If the email touts "20% off" and the click lands on a generic homepage, visitors bounce on the spot.

## CTA Placement Best Practices

### Short Emails (<200 words)

A single CTA, mid-email or closing.

Intro → Value prop → CTA

### Medium Emails (200-500 words)

One CTA up top, one to close.

Intro + CTA → Content → Final CTA

### Long Emails (>500 words)

CTAs spaced through the content.

CTA → Content → CTA → More content → Final CTA

#### Above the Fold

On mobile, make sure one CTA appears before any scrolling is needed. Plenty of readers never scroll at all—capture them while you have them.

## Common CTR Mistakes to Avoid

### ✗ Too Many CTAs

A crowd of competing CTAs leaves readers unsure what to do—and doing nothing. Commit to one primary action per email.

### ✗ Vague CTA Copy

"Click here" and "Learn more" promise nothing. Spell out the payoff—"Download free guide" or "Start 14-day trial" tell readers exactly what awaits.

### ✗ Image-Only CTAs

Plenty of email clients suppress images by default—an image-based CTA can simply vanish. Build buttons from HTML and text instead.

### ✗ Small, Hard-to-Tap Links

Fingertips need targets bigger than fine print. Keep buttons at 44x44px or larger so mobile readers can actually hit them.

### ✗ No Clear Value Proposition

A click is a small transaction—readers give attention expecting a return. Make the benefit obvious before you ask for the action.

## Related Email Guides

- [Email Open Rates](/guides/email-open-rate): More opens mean more chances to earn clicks.

- [Email Marketing Best Practices](/guides/email-marketing-best-practices): The end-to-end email marketing playbook.

- [Email Deliverability](/guides/email-deliverability): Inbox placement is where engagement begins.

---

> Source: https://dev.bitelio.com/guides/email-click-through-rate

---

# https://dev.bitelio.com/guides/email-deliverability

# Email Deliverability: The Complete Guide to Inbox Placement

A practical guide to email deliverability: what affects it, how to stay out of spam folders, and the authentication, list, and content practices that get you into the inbox.

Email deliverability describes how reliably your messages land in the inbox instead of getting filtered to spam or rejected outright. It's the metric that makes every other email effort count—a brilliant campaign achieves nothing if nobody ever sees it.

In this guide we walk through the full picture of email deliverability, from authentication protocols and infrastructure to list hygiene and content, giving you a clear path to consistently high inbox placement.

## What is Email Deliverability?

At its core, email deliverability is the share of your sent messages that actually arrive in subscribers' inboxes. It's expressed as a percentage, and where you fall on the scale matters:

95%+

### Excellent

Solid reputation, full authentication, and an audience that engages

85-94%

### Good

Workable, but authentication or engagement needs attention

<85%

### Poor

Something is badly wrong—investigate and fix it now

#### Deliverability vs Delivery Rate

Don't confuse the two: **delivery rate** counts messages the receiving server accepted (i.e., didn't bounce), while **deliverability** counts messages that made it into the actual inbox rather than spam. Healthy programs keep both numbers high.

## Key Factors Affecting Deliverability

No single lever controls inbox placement—several interlocking factors decide where your mail ends up:

### 1\. Sender Reputation

Mailbox providers keep a running score on every sender. Strong engagement, minimal complaints, and clean bounce numbers raise that score; sloppy sending habits drag it down.

### 2\. Email Authentication

SPF, DKIM, and DMARC together prove your mail is genuinely yours. Skip them and filters have every reason to treat your messages as potential spam.

### 3\. Email Content

Filters scrutinize everything you write—subject lines, body copy, links, images. Salesy hype, link overload, or bait-and-switch content all raise red flags.

### 4\. List Quality & Engagement

Nothing beats mailing people who actually want to hear from you. Opens and clicks tell providers your mail is valued; silence and spam reports tell them the opposite.

### 5\. Technical Infrastructure

The IP you send from, your domain's history, and your overall setup all color how providers judge your mail. At higher volumes, dedicated IPs and careful warm-up become essential.

## Email Deliverability Best Practices

### Authentication & Technical Setup

1

#### Configure SPF, DKIM, and DMARC

Deploy the complete authentication trio. Together they verify your identity as a sender and lock spoofers out of your domain.

2

#### Use a Dedicated Sending Domain

Route marketing traffic through a subdomain such as mail.yourdomain.com. If that stream ever runs into trouble, your primary domain's reputation stays insulated.

3

#### Warm Up New IPs and Domains

Fresh IPs and domains need a gentle ramp: build volume slowly across 2-4 weeks. A brand-new sender blasting huge volume on day one is a classic spam pattern.

### List Management

4

#### Use Double Opt-In

Ask new subscribers to confirm their address before they join the list. It keeps typos and spam trap addresses out and guarantees genuine interest.

5

#### Clean Your List Regularly

Purge hard bounces the moment they occur, and think about retiring subscribers who've gone silent for 6-12 months. Dead weight on your list quietly erodes your reputation.

6

#### Make Unsubscribing Easy

Put an obvious unsubscribe link in every message. When leaving is difficult, frustrated recipients hit "report spam" instead—and that hurts you far more than any opt-out.

### Content Best Practices

7

#### Avoid Spam Trigger Words

Phrases like "FREE", "ACT NOW", and "LIMITED TIME"—along with strings of exclamation marks and ALL-CAPS text—are magnets for spam filters. Plain, professional language wins.

8

#### Balance Text and Images

Never ship an email that's just one big image. Keep the mix at 60% text or better, and always give your images descriptive alt text.

9

#### Use Relevant Subject Lines

Promise in the subject line only what the email delivers. Clickbait subjects earn short-term opens and long-term spam complaints.

## Common Deliverability Issues & Solutions

### Problem: Emails Going to Spam

**Causes:** Weak sender reputation, absent authentication, filter-triggering content, disengaged recipients

**Solutions:** Audit your SPF/DKIM/DMARC records, tighten up your content, narrow sends to subscribers who engage, and rebuild reputation through gradual warm-up

### Problem: High Bounce Rate

**Causes:** Bad addresses, bought lists, neglected list maintenance

**Solutions:** Adopt double opt-in, run addresses through validation, drop hard bounces the moment they happen, and schedule routine list cleanups

### Problem: Low Engagement Rates

**Causes:** Content that misses the mark, poorly chosen frequency, an aging list

**Solutions:** Split your audience into segments, tailor content to each, experiment with send timing, and run win-back campaigns for dormant subscribers

### Problem: Blacklisted IP or Domain

**Causes:** Complaint spikes, spam trap hits, an account taken over by attackers

**Solutions:** Look yourself up on blacklists (MXToolbox, Spamhaus), file delisting requests, resolve the root cause first, and if the damage is beyond repair, migrate to a fresh sending domain

## Monitoring Email Deliverability

Keep a close eye on these numbers to catch problems before they compound:

### Delivery Rate

The share of mail that didn't bounce. Aim for 98%+, and monitor hard and soft bounces as separate signals.

### Inbox Placement Rate

Of the mail that was delivered, how much landed in the inbox rather than spam. Aim for 95%+; seed list tests reveal the truth here.

### Spam Complaint Rate

How often recipients hit "report spam." Stay under 0.1%—by the time you reach 0.3%, you have a real problem.

### Engagement Metrics

Opens, clicks, and unsubscribes round out the picture. When engagement stays low for a sustained period, deliverability trouble usually follows.

#### Use DMARC Reports

Your DMARC aggregate reports reveal both how well your mail authenticates and whether anyone is attempting to spoof your domain. A weekly review helps you spot deliverability problems while they're still small.

## Related Email Guides

- [What is DKIM?](/guides/what-is-dkim): How DKIM signatures authenticate your mail.

- [What is SPF?](/guides/what-is-spf): How SPF records declare who may send for your domain.

- [Email Sender Reputation](/guides/email-sender-reputation): Earn and protect the reputation that drives inbox placement.

---

> Source: https://dev.bitelio.com/guides/email-deliverability

---

# https://dev.bitelio.com/guides/email-list-building

# How to Build an Email List (the Right Way)

Learn how to build an email list the right way: permission-based opt-in forms, lead magnets, double opt-in, list hygiene, and smart segmentation.

An email list is one of the few marketing assets you actually own. Unlike social followers or ad audiences, your list is not rented from a platform that can change its rules overnight. But that value only holds if the list is built the right way: with permission, from real people who genuinely want to hear from you.

This guide walks through how to grow an email list that performs, from your first opt-in form to the habits that keep a large list healthy. The core principle behind all of it is simple: quality of consent beats quantity of contacts, every time.

## Why a Permission-Based List Matters

A permission-based list is made up of people who explicitly asked to receive your email. That single fact changes everything downstream. When subscribers expect your messages, they open them, click them, and rarely mark them as spam. Mailbox providers like Gmail and Outlook watch those engagement signals closely and use them to decide whether your future emails land in the inbox or the spam folder.

The opposite is also true. Email people who never opted in and you will collect spam complaints, hard bounces, and low engagement. Those signals damage your [email deliverability](/guides/email-deliverability) for everyone on the list, including the subscribers who do want to hear from you. A poisoned reputation is slow and painful to repair.

Permission is also a legal requirement in much of the world. GDPR in the EU and CASL in Canada require demonstrable consent before you send marketing email, and CAN-SPAM in the US requires a clear way to opt out. Building on permission keeps you compliant by default rather than scrambling to fix problems later.

#### Quality Compounds, Quantity Decays

A small engaged list grows more valuable over time as subscribers trust you and buy from you. A large unengaged list decays: complaints rise, deliverability drops, and eventually even your good contacts stop seeing your email. Optimize for the first outcome from day one.

## Opt-In Forms and Where to Place Them

The opt-in form is the front door to your list. Two things determine how many people walk through it: how little friction it creates, and where you put it. Keep the form short. In most cases, an email address is the only field you truly need, and every extra field you add reduces signups. If you need a first name for personalization, ask for that one and nothing more.

Placement matters just as much as design. A form buried in the footer will be ignored. Put your opt-in where attention and intent are highest:

### Above the fold on your homepage

Your homepage is your highest-traffic page. A clear signup with a strong value proposition near the top captures visitors while their interest is fresh.

### Inside and after blog posts

Readers who finish an article are your warmest audience. An inline or end-of-post form that offers more of the same value converts far better than a generic sidebar box.

### At checkout and account creation

A single opt-in checkbox during purchase or signup turns customers into subscribers, provided it is unchecked by default so consent stays explicit.

### Timed or exit-intent popups

Used sparingly, a popup triggered by time on page or exit intent can lift signups significantly. Keep it easy to dismiss so it does not frustrate readers.

Whatever placement you choose, be honest about what subscribers will get and how often. A specific promise such as "one practical email each week" sets expectations and reduces unsubscribes later.

## Lead Magnets That Earn the Opt-In

People rarely subscribe to a list just to receive "updates." They subscribe to get something valuable in return. That something is your lead magnet: a focused, immediately useful resource offered in exchange for an email address.

The best lead magnets are narrow. They solve one specific problem for one specific person, fast. A checklist, a template, a short email course, a discount code, a calculator, or a piece of gated benchmark data all work well because the value is concrete and the payoff is quick. A vague "ultimate 80-page guide" often converts worse than a one-page checklist, because the reader can instantly picture using the checklist today.

Match the lead magnet to where the subscriber is in their journey. Someone reading an introductory blog post wants a starter resource; someone comparing products wants a template or discount that helps them decide. Relevance at the moment of signup is what turns a casual visitor into an engaged subscriber.

## Confirm Intent with Double Opt-In

When someone submits your form, you have a choice. With single opt-in they are added to your list immediately. With double opt-in they first receive a confirmation email and must click a link to complete their subscription. That extra step is one of the highest-leverage habits in list building.

Double opt-in filters out typos, fake addresses, and bots before they ever reach your list. The result is a cleaner list with lower bounce rates and higher engagement, which directly protects your sender reputation. It also gives you a clear, timestamped record of consent, which is valuable evidence under GDPR and similar laws.

Single opt-in grows your list faster in raw numbers, but a meaningful share of those addresses will be dead or disengaged. For most senders the trade is worth it. Learn how to set it up in our dedicated [double opt-in guide](/guides/double-opt-in).

## Why You Should Never Buy an Email List

Buying or renting an email list looks like a shortcut to scale. It is actually a shortcut to failure. Every serious downside of bad list building is concentrated in a purchased list.

### ✗ No consent, no legal basis

The people on a purchased list never agreed to hear from you. Under GDPR and CASL that alone makes emailing them unlawful, exposing you to real fines and complaints.

### ✗ Destroyed sender reputation

Purchased lists are riddled with spam traps and stale addresses. Mailing them triggers complaints and hard bounces that can get your domain and IP blocklisted within a single campaign.

### ✗ Almost no engagement or revenue

Strangers do not know your brand, so they do not open, click, or buy. You pay for volume and receive deliverability damage in return, which then hurts the good contacts you earned honestly.

#### A Bought List Poisons the Whole List

Sender reputation is domain-wide. When a purchased segment generates complaints and spam-trap hits, the damage follows every email you send, including messages to the loyal subscribers who opted in. There is no safe way to isolate the risk.

## Keep Your List Clean with Regular Hygiene

A healthy list is not built once and left alone. Addresses go stale, people change jobs, and interest fades. List hygiene is the ongoing practice of removing contacts that hurt your performance so the ones that remain keep your engagement high.

Build these habits into your routine:

1

### Remove hard bounces immediately

A hard bounce means the address does not exist. Continuing to mail it signals to providers that you do not maintain your list, so suppress it right away.

2

### Re-engage or sunset inactive subscribers

For anyone who has not opened or clicked in 90 to 180 days, send a short win-back campaign. If they still do not respond, remove them rather than dragging down your metrics.

3

### Honor unsubscribes instantly

Make opting out one click, and process it without delay. A frustrated subscriber who cannot leave will click "spam" instead, which is far more damaging than a clean unsubscribe.

Clean lists are not just tidier, they perform better. Every disengaged address you remove lifts your average open and click rates, and those higher rates tell mailbox providers to keep sending you to the inbox.

## Segment From the Start

Most people treat segmentation as something to figure out once the list is large. That is a mistake. The easiest time to organize your list is while it is still small, because the context you capture at signup is almost impossible to reconstruct later.

Start with lightweight signals you already have: which lead magnet someone downloaded, which form or page they subscribed from, whether they are a customer or a prospect, and any single preference you asked for at signup. Store these as tags or fields from day one. Even a simple split between customers and non-customers lets you send far more relevant email than a single broadcast to everyone.

Relevant email is engaged email, and engaged email protects deliverability, so segmentation reinforces every other habit in this guide. For patterns and examples, see our full guide to [email segmentation](/guides/email-segmentation).

#### Bitelio Makes This Practical

With Bitelio you can capture opt-ins, add custom contact fields and tags at signup, and build segments from behavior without writing queries. That means you can start clean and stay organized as your list grows from hundreds to hundreds of thousands of contacts.

## Related Guides

- [Double Opt-In Explained](/guides/double-opt-in): Why confirmed subscriptions build a cleaner, safer list.

- [Email Segmentation](/guides/email-segmentation): Send more relevant email by grouping subscribers the right way.

- [Email Deliverability Guide](/guides/email-deliverability): Keep the list you build landing in the inbox, not spam.

---

> Source: https://dev.bitelio.com/guides/email-list-building

---

# https://dev.bitelio.com/guides/email-marketing-best-practices

# Email Marketing Best Practices: Everything That Actually Works

A complete playbook of email marketing best practices—list growth, copy, design, send timing, testing, deliverability, and legal compliance for 2025.

Few channels can match email marketing's returns: every $1 invested brings back $36-42 on average. Capturing that upside, however, means keeping pace with best practices that shift as technology, privacy law, and subscriber expectations evolve.

This guide walks through the whole discipline—growing a quality list, writing content that converts, keeping your mail deliverable, and staying on the right side of the regulations.

## Building Your Email List

Everything in email marketing rests on the quality of your list. Prioritize subscribers who actively chose you over sheer subscriber counts.

### ✓ Best Practices

-   •**Use double opt-in:** Have subscribers verify their address before joining. You get a cleaner list and fewer spam complaints down the road.
-   •**Offer clear value:** Spell out exactly what lands in their inbox and how often. "Get weekly tips on \[topic\]" converts better than a vague "Subscribe to our newsletter."
-   •**Use multiple touchpoints:** Put signup opportunities everywhere your audience already is—your site, blog posts, checkout flow, social channels, and live events.
-   •**Provide incentives:** Sweeten the deal with lead magnets—an ebook, a discount code, templates, or subscriber-only content.
-   •**Make forms easy:** Every extra field costs signups. Request only what you truly need—usually the email address, occasionally a name.

### ✗ Avoid These Mistakes

-   •**Never buy email lists:** Bought contacts translate directly into complaints, dead engagement, and a wrecked sender reputation.
-   •**Don't use pre-checked boxes:** Consent has to be an active choice. Pre-ticked checkboxes breach GDPR and fill your list with people who never wanted in.
-   •**Avoid hidden signup terms:** Say plainly what kind of email you send and how often—no surprises after the fact.

## Email Content Best Practices

### 1\. Craft Compelling Subject Lines

The subject line is the gatekeeper of every open. Stay under 50 characters, spark curiosity, and make the payoff concrete.

Examples:

-   ✓ "5 proven strategies to reduce churn by 30%"
-   ✓ "Your personalized year-end report is ready"
-   ✓ "Last chance: Sale ends tonight at midnight"
-   ✗ "Newsletter #47"
-   ✗ "Check this out!!!"

### 2\. Personalize Beyond First Names

Real personalization draws on what people do: their purchases, browsing sessions, and stated preferences. The reward is substantial—personalized emails drive 6x the transaction rates of generic sends.

### 3\. Focus on One Primary Goal

Build every email around a single call-to-action. Stacking multiple CTAs splinters attention and drags conversion down—point readers at one action and clear the path to it.

### 4\. Write Scannable Content

Readers skim before they read—if they read at all. Format accordingly:

-   Cap paragraphs at 2-3 sentences
-   Lean on bullets and numbered lists
-   Break sections up with descriptive subheadings
-   Let whitespace do its work
-   Bold the takeaways

### 5\. Create Compelling CTAs

The CTAs that get clicked share four traits:

-   **Action-oriented:** "Download the guide" not "Click here"
-   **Specific:** "Start your 14-day free trial" not "Get started"
-   **Visually prominent:** A button in a color that stands apart
-   **Urgent when appropriate:** "Claim your discount today"

### 6\. Provide Real Value

The reader should come away better off from every email—smarter, entertained, or with a problem solved. Pure promotion wears thin fast; teach and engage instead.

## Email Design Best Practices

1

### Mobile-First Design

Over 60% of opens happen on a phone, so design for that screen first: responsive templates, tap targets of 44x44px or more, and testing on real devices and clients before launch.

2

### Optimize Images

Compress everything so pages load instantly, add alt text since many clients hide images by default, and hold the line at a 60/40 text-to-image balance. An all-image email is never the answer.

3

### Brand Consistency

Keep colors, typography, logo, and voice uniform across every send so your emails are recognizable at a glance. A shared template system makes this effortless.

4

### Accessible Design

Design for every reader: contrast ratios of at least 4.5:1, body text at 14px or larger, links whose text describes their destination, and semantic HTML that screen readers can navigate.

5

### Test Across Email Clients

The same HTML renders wildly differently in Gmail, Outlook, and Apple Mail. Preview across the major clients every time—before the campaign goes to your whole list, not after.

## Timing & Frequency Best Practices

### Best Send Times (General)

-   **B2B:** Tuesday-Thursday, 10am-11am or 2pm-3pm
-   **B2C:** No universal rule—experiment with evenings and weekends
-   **Avoid:** Monday-morning inbox pileups and Friday-afternoon checkouts

#### Test Your Audience

Treat these windows as hypotheses, not rules. Your audience may buck the trend—run A/B tests on timing and follow the data wherever it points.

### Email Frequency Guidelines

-   **Weekly:** The default cadence for newsletters and content programs
-   **2-3x/week:** Sustainable when the audience is engaged and the content is fresh
-   **Daily:** Reserve for news digests, deal alerts, or die-hard communities
-   **Monthly:** You risk fading from memory—works best for carefully curated roundups

#### Monitor Unsubscribes

A jump in unsubscribes right after you increase cadence is your audience saying "too much." Dial back and find the equilibrium.

## Segmentation & Personalization

The numbers speak for themselves: segmented campaigns earn 30% more opens and 50% more clicks than one-size-fits-all sends. Aim each message at the group it's meant for instead of blasting everyone.

### Common Segmentation Criteria

-   • **Demographics:** Age, location, job title, company size
-   • **Behavior:** What they've bought, browsed, and clicked
-   • **Lifecycle stage:** Fresh signup, active customer, lapsed user
-   • **Engagement level:** Regular readers versus the silent majority
-   • **Preferences:** Product interests, favorite topics, desired cadence
-   • **Purchase recency:** Just bought versus gone quiet

### Segment-Specific Campaigns

-   • A welcome sequence for brand-new subscribers
-   • Re-engagement pushes for readers gone quiet
-   • Win-back offers aimed at churned customers
-   • Recommendations built on prior purchases
-   • Geo-targeted offers and event invites
-   • White-glove campaigns for your highest-value customers

## Testing & Optimization

Great email programs are built on relentless testing. Hunches are hypotheses—only the data gets a vote.

### What to A/B Test

-   • **Subject lines:** Length, personal touches, questions versus statements, emoji use
-   • **Send times:** Weekday, hour, and timezone handling
-   • **Content:** Long-form versus short, text-led versus visual, voice and tone
-   • **CTAs:** Wording, color, position, and how many you include
-   • **Sender name:** The brand versus a real human
-   • **Personalization:** Tailored content versus the generic version

### A/B Testing Best Practices

-   • Change a single variable per test so results stay interpretable
-   • Reach statistical significance—at least 1,000+ recipients per variant
-   • Let tests run long enough to smooth out timing effects
-   • Split randomly; hand-picked segments poison the results
-   • Ship the winner, then move on to the next variable

## Legal Compliance

Regulators take email seriously, and so should you—violations bring heavy fines and lasting reputational harm.

### CAN-SPAM (US)

-   • No deceptive subject lines or falsified headers
-   • A physical mailing address in every message
-   • An unsubscribe option that's obvious and simple
-   • Opt-outs processed within 10 business days
-   • Advertising labeled as such where required

### GDPR (EU)

-   • Explicit consent collected before any marketing email
-   • Transparent explanations of how data will be used
-   • Subscriber rights to view, correct, or erase their data
-   • Consent records retained as proof
-   • Security measures proportionate to the data you hold

#### When in Doubt, Get Consent

Requirements differ from one jurisdiction to the next, but one strategy is safe everywhere: collect explicit, documented consent before anyone joins your list, keep the exit door wide open, and act on opt-outs at once.

## Key Metrics to Track

### Engagement Metrics

-   • **Open rate:** Industry average: 15-25%
-   • **Click-through rate (CTR):** Industry average: 2-5%
-   • **Click-to-open rate (CTOR):** Clicks ÷ opens
-   • **Conversion rate:** Goal completions ÷ delivered

### Health Metrics

-   • **Bounce rate:**Target: <2%
-   • **Unsubscribe rate:**Target: <0.5%
-   • **Spam complaint rate:**Target: <0.1%
-   • **List growth rate:** New subscribers vs unsubscribes

### Business Metrics

-   • **ROI:** Revenue generated ÷ cost
-   • **Revenue per email:** Total revenue ÷ emails sent
-   • **Customer lifetime value (CLV):** Long-term value
-   • **Cost per acquisition (CPA):** Acquisition cost

### Deliverability Metrics

-   • **Delivery rate:** Target: 98%+
-   • **Inbox placement rate:** Target: 95%+
-   • **Sender reputation score:** Monitor regularly
-   • **Authentication status:** SPF, DKIM, DMARC passing

## Related Email Guides

- [Email Deliverability](/guides/email-deliverability): Make sure your campaigns actually arrive.

- [Email Open Rates](/guides/email-open-rate): Field-tested tactics for winning more opens.

- [Email Click-Through Rate](/guides/email-click-through-rate): Turn opens into clicks with better CTAs.

---

> Source: https://dev.bitelio.com/guides/email-marketing-best-practices

---

# https://dev.bitelio.com/guides/email-metrics-kpis

# Email Marketing Metrics and KPIs That Matter

Learn which email marketing metrics matter: delivery rate, open rate, CTR, bounce rate, complaints, and conversion, with benchmarks and tips to improve each.

Email marketing metrics are the numbers that tell you whether your campaigns are working. But not every metric deserves your attention, and chasing the wrong one can quietly steer your program in the wrong direction. A soaring open rate means little if nobody clicks, and a strong click rate is wasted if half your list never received the message in the first place.

This guide walks through the email marketing metrics and KPIs that actually matter, grouped by what they measure. For each one you'll get a plain definition, a rough benchmark to aim for, and the most effective ways to improve it. Treat the benchmarks as starting points—your own historical data is always the more meaningful comparison.

## How to Think About Email Metrics

Email metrics fall into three natural layers, and it helps to read them in order. First, deliverability metrics tell you whether your email even reached the inbox. Second, engagement metrics tell you whether people who received it cared. Third, outcome metrics tell you whether that engagement produced business value. A problem at a lower layer poisons everything above it, so always diagnose from the bottom up.

#### Deliverability comes first

There is no point optimizing subject lines if a growing share of your emails is bouncing or landing in spam. Fix delivery, bounce, and complaint rates before you obsess over opens and clicks—otherwise you're tuning a radio that isn't plugged in.

## Deliverability and List-Health Metrics

These metrics protect your sender reputation. Left unwatched, they are also the fastest way to get your email quietly filtered into spam across an entire mailbox provider.

### Delivery Rate

Delivery rate is the percentage of sent emails that were accepted by the recipient's mail server, rather than bounced. It is calculated as delivered divided by total sent. Note that "delivered" is not the same as "reached the inbox"—an email can be accepted and then filtered into spam—but a low delivery rate is an unambiguous red flag.

Benchmark: aim for 99% or higher. Anything below 95% points to serious list-quality or authentication problems.

How to improve it: authenticate your domain with SPF, DKIM, and DMARC; remove invalid and inactive addresses before sending; warm up new sending domains and IPs gradually; and avoid purchased lists, which are riddled with spam traps.

### Bounce Rate

Bounce rate is the percentage of emails that could not be delivered, calculated as bounces divided by sent. Hard bounces are permanent failures (the address doesn't exist), while soft bounces are temporary (a full mailbox or a server hiccup). Hard bounces are the ones that damage reputation and must be suppressed immediately.

Benchmark: keep total bounces under 2%, and hard bounces under 0.5%. A sudden spike almost always means a list-quality or authentication issue.

How to improve it: use double opt-in so addresses are confirmed, validate emails at the point of capture, and automatically remove hard bounces after a single failure. Our [email bounce rate guide](/guides/email-bounce-rate) covers the causes and fixes in depth.

### Spam-Complaint Rate

Spam-complaint rate is the percentage of recipients who marked your email as spam, calculated as complaints divided by delivered. It is one of the most heavily weighted signals mailbox providers use, and even a small rate can trigger widespread filtering.

Benchmark: stay well under 0.1%. Since 2024, Gmail and Yahoo require bulk senders to keep complaints below 0.3%, and treat 0.1% as the healthy ceiling.

How to improve it: make the unsubscribe link obvious, set clear expectations at sign-up about what and how often you'll send, only mail people who genuinely opted in, and stop mailing subscribers who haven't engaged in months.

### Unsubscribe Rate

Unsubscribe rate is the percentage of recipients who opted out after receiving an email, calculated as unsubscribes divided by delivered. A steady, low rate is normal and healthy—it keeps your list clean. A rising rate is a warning that your content, frequency, or targeting is off.

Benchmark: under 0.5% is normal, and under 0.2% is strong. Counter-intuitively, an unsubscribe is far better than a spam complaint, so never hide the opt-out.

How to improve it: offer a preference center so people can dial down frequency instead of leaving entirely, segment so content stays relevant, and avoid over-mailing after a burst of new sign-ups.

## Engagement Metrics

Once your email reliably reaches the inbox, engagement metrics tell you whether the audience actually cares about what you sent.

### Open Rate

Open rate is the percentage of delivered emails that were opened, calculated as unique opens divided by delivered. It reflects how well your subject line, sender name, and send timing earn attention. Since Apple's Mail Privacy Protection began pre-loading tracking pixels in 2021, reported opens are inflated, so treat this metric as directional rather than exact.

Benchmark: 20-30% is typical, with strong B2B campaigns reaching 35% or more. Compare against your own trend line rather than the industry average.

How to improve it: write specific subject lines under 50 characters, use a recognizable sender name, optimize preview text, and send when your audience is active. Our [email open rate guide](/guides/email-open-rate) breaks down benchmarks by sector.

### Click-Through Rate (CTR)

Click-through rate is the percentage of delivered emails that generated at least one click, calculated as unique clicks divided by delivered. Because it requires a deliberate action, CTR is a far more reliable signal of genuine interest than open rate—especially in a post-privacy world.

Benchmark: 2-5% for most campaigns, though triggered and transactional emails often exceed 10% because they arrive at the exact moment of interest.

How to improve it: lead with one clear primary call-to-action, design buttons that stand out and work on mobile, match the offer to the segment, and cut clutter that competes for the click. Our [email click-through rate guide](/guides/email-click-through-rate) goes deeper on tactics.

### Click-to-Open Rate (CTOR)

Click-to-open rate divides unique clicks by unique opens, so it only measures people who actually opened the email. This makes CTOR the cleanest read on how persuasive your content and layout are, independent of how good your subject line was at driving opens in the first place.

Benchmark: 10-20% is a solid range. A high open rate paired with a low CTOR usually means the subject line over-promised and the body under-delivered.

How to improve it: make sure the email body delivers on the subject line's promise, keep the message focused on a single goal, and place your primary call-to-action above the fold where it can't be missed.

## Business-Outcome Metrics

Engagement is a means to an end. Outcome metrics connect email activity to the revenue and results that justify the channel.

### Conversion Rate

Conversion rate is the percentage of recipients who completed the desired action—a purchase, a sign-up, a booking—after receiving your email. It can be measured against delivered emails or against clicks; measuring against clicks isolates how well your landing page finishes the job the email started.

Benchmark: highly variable. For e-commerce promotions, 1-5% of delivered is common; for well-targeted triggered flows like cart abandonment, conversion can run far higher. Your own baseline is the only number that truly matters here.

How to improve it: match the landing page to the email's promise, remove friction from the next step, use a genuine and specific offer, and send to tightly defined segments so the message lands with the right people at the right time.

#### Tie it back to revenue

Where you can, translate conversion into revenue per email sent and overall return on investment. These monetary metrics are what earn email marketing its budget, and they cut through vanity-metric debates about whether an inflated open rate is "good."

## Benchmark Summary

Use these ranges as rough targets, then replace them with your own historical numbers as soon as you have a few months of data.

| Metric | Rough Benchmark |
| --- | --- |
| Delivery rate | 99% or higher |
| Bounce rate | Under 2% total, under 0.5% hard |
| Spam-complaint rate | Under 0.1% (must stay under 0.3%) |
| Unsubscribe rate | Under 0.5% |
| Open rate | 20-30% (privacy-inflated) |
| Click-through rate | 2-5% |
| Click-to-open rate | 10-20% |
| Conversion rate | 1-5% (highly variable) |

## Which Metrics Should You Prioritize?

You can't optimize everything at once, so sequence your attention. Start by guarding the gating metrics—bounce rate and spam complaints—because a failure there quietly caps every other number. With deliverability secure, shift to engagement: use click-through and click-to-open rate to sharpen content, and lean on open rate only as a directional signal given its privacy-driven inflation.

Finally, anchor the whole program to conversion and revenue per email, the metrics that connect your work to the business. When you review results, always compare against your own past performance and change one variable at a time. That discipline turns a wall of numbers into a clear, repeatable path to improvement.

## Related Email Metrics Guides

- [Email Open Rates](/guides/email-open-rate): Benchmarks by sector and proven ways to lift your open rate.

- [Click-Through Rate](/guides/email-click-through-rate): How to design emails that earn more clicks.

- [Email Bounce Rate](/guides/email-bounce-rate): Understand hard vs soft bounces and how to keep yours low.

---

> Source: https://dev.bitelio.com/guides/email-metrics-kpis

---

# https://dev.bitelio.com/guides/email-open-rate

# Email Open Rates: Benchmarks by Industry & Ways to Boost Yours

Everything that drives email open rates: sector-by-sector benchmarks, how B2B compares to B2C, the Apple MPP effect, and concrete tactics to lift your numbers.

Email open rate tracks what share of recipients actually open the messages you send. Few metrics matter more in email marketing—it reveals whether your subject lines land, whether people recognize your sender name, and whether you're mailing at the right moment.

Privacy features have made the number less precise in recent years, but tracked thoughtfully, open rate still offers real insight into how your audience responds to your email program.

## What is Email Open Rate?

The math is straightforward: take unique opens and divide by delivered emails—that is, everything you sent minus the bounces.

Open Rate Formula

```
Open Rate = (Unique Opens ÷ Emails Delivered) × 100

Example:
- Sent: 1,000 emails
- Bounced: 50 emails
- Delivered: 950 emails
- Unique Opens: 285

Open Rate = (285 ÷ 950) × 100 = 30%
```

#### Unique vs Total Opens

A recipient who opens your email five times counts once under **unique opens** but five times under **total opens**. Base your open rate on unique opens—otherwise repeat readers quietly inflate the figure.

## Email Open Rate Benchmarks by Industry

What counts as "normal" shifts considerably from one sector, audience, and email type to the next:

| Industry | Average Open Rate | Good Open Rate |
| --- | --- | --- |
| SaaS / Technology | 20-25% | 30%+ |
| E-commerce / Retail | 15-20% | 25%+ |
| Financial Services | 18-23% | 28%+ |
| Healthcare | 20-25% | 30%+ |
| Education | 22-28% | 33%+ |
| Media / Publishing | 18-23% | 28%+ |
| Non-Profit | 24-30% | 35%+ |

#### Post-Apple MPP Benchmarks

Ever since Apple Mail Privacy Protection arrived in 2021, reported open rates across the industry run 5-15 percentage points above true engagement. Benchmark against your own past campaigns rather than treating industry tables as ground truth.

## B2B Email Open Rates

Business-to-business email reliably beats consumer benchmarks. The reason is intent: these subscribers joined your list to solve a professional problem, so they pay closer attention.

| B2B Industry | Average Open Rate | Top Performers |
| --- | --- | --- |
| SaaS / Technology | 22–28% | 35%+ |
| Professional Services | 25–32% | 40%+ |
| Financial Services | 20–26% | 33%+ |
| Agency / Marketing | 18–24% | 30%+ |
| Transactional / Receipts | 45–65% | 70%+ |

### B2B-Specific Tactics

-   • Schedule for Tuesday–Thursday, 10am–2pm in each recipient's timezone
-   • Put your company or product name in the subject so it's instantly recognized
-   • Tailor content by role, industry, or company size
-   • Speak to the specific challenges of the recipient's position
-   • Dial back frequency—1–2 sends per month is plenty for cold lists

### B2B vs B2C Differences

-   • B2B buyers deliberate more—longer subject lines are tolerated
-   • Weekend inbox activity drops sharply for B2B audiences
-   • Shared team inboxes in B2B can distort your numbers
-   • Unsubscribes run lower in B2B (0.1–0.3% versus 0.3–0.5%)
-   • B2B transactional mail (invoices, updates) opens at far higher rates

#### Segment Transactional vs Marketing

Track transactional messages (receipts, password resets, notifications) separately from marketing sends. Because transactional mail routinely opens at 40–60%, blending the two streams will make your marketing numbers look better than they are.

## What Affects Email Open Rates?

### 1\. Subject Line

Nothing influences opens more than the subject line. Aim for relevance and genuine intrigue—never clickbait. Specific, personalized subjects consistently outperform vague ones.

✓"John, your invoice is ready" (personal, specific, clear)

✓"3 proven ways to increase conversion rates" (specific value)

✗"You won't believe this!" (clickbait, vague)

✗"Newsletter #47" (generic, uninteresting)

### 2\. Sender Name

The "from" field is the first thing recipients weigh when deciding to open. Choose a name they'll know on sight—your brand, or a real person like "John from Company". An address such as "noreply@company.com" invites deletion.

### 3\. Send Time & Day

When you send shapes whether you're seen. For B2B, midweek mornings shine—Tuesday through Thursday, 10am-2pm. B2C behavior is more varied, so experiment with evenings and weekends. Steer clear of Monday mornings and Friday afternoons regardless.

### 4\. List Quality & Segmentation

An engaged list opens more, full stop. Segment by behavior, interest, or demographics so every send feels relevant—and don't let dormant subscribers sit there dragging your averages down; re-engage or remove them.

### 5\. Deliverability & Sender Reputation

An email sitting in spam gets zero opens. Protect your inbox placement with full authentication (SPF, DKIM, DMARC), a low complaint rate, and consistently strong engagement.

### 6\. Email Frequency

Over-mail and you breed fatigue and unsubscribes; under-mail and you fade from memory. Most marketing programs find their rhythm somewhere between 1-4 emails weekly—test to locate yours.

### 7\. Mobile Optimization

With 60%+ of opens happening on phones, mobile is the default context. Keep subjects to 40-50 characters, write purposeful preview text, and build with responsive design.

## How to Improve Email Open Rates

1

### Write Compelling Subject Lines

Experiment with formats—questions, personal touches, numbers, tasteful urgency—while staying under 50 characters. Let A/B tests, not intuition, tell you what your audience responds to.

2

### Personalize Beyond First Names

Draw on real signals: what someone bought, browsed, or where they're located. A message framed as "Products you recently viewed" or "Based on your interest in \[topic\]" beats a one-size-fits-all blast every time.

3

### Segment Your Audience

Divide your list by engagement, purchase behavior, demographics, or stated interests, then tailor each send. The payoff is real: segmented campaigns post open rates 14-100% above unsegmented ones.

4

### Optimize Preview Text

That snippet beside your subject line is prime real estate. Use it to extend the subject's promise or layer in extra intrigue—never leave it showing "View this email in your browser".

5

### Clean Your Email List Regularly

Drop anyone silent for 6-12 months. Yes, the list shrinks—but open rates and sender reputation climb sharply in return. A smaller engaged list beats a bloated indifferent one.

6

### Test Send Times

Split-test identical emails across different send windows and watch where your audience responds. Getting the timing right can lift opens by 20-50% on its own.

7

### Re-engage Inactive Subscribers

Give dormant subscribers one last chance before cutting them: a "We miss you" or "Still interested?" campaign, perhaps sweetened with an offer. Whoever stays silent after that comes off the list.

8

### Use a Recognizable Sender Name

Pick a sender name and stick with it. Familiarity drives opens—recipients trust names they've seen before, and frequent changes reset that trust to zero.

## Apple Mail Privacy Protection Impact

Starting with iOS 15, Apple Mail Privacy Protection fetches images and tracking pixels before the user does anything—undermining the reliability of open tracking for anyone on Apple Mail.

### What Changed

-   • All images get pre-fetched by Apple Mail automatically
-   • An "open" registers even when nobody reads the message
-   • Apple Mail accounts for 30-50% of typical lists
-   • Reported open rates run 5-15% above actual engagement
-   • Automations triggered by opens lose precision

### How to Adapt

-   • Make click rate your headline engagement metric
-   • Measure conversions and replies, not opens alone
-   • Adopt multi-touch attribution
-   • Benchmark against your own history, not industry tables
-   • Break out metrics by email client for a true picture

#### Beyond Open Rates

Now that open data is noisy, weight your analysis toward click-through rate, conversions, replies, and revenue per email. Those numbers reflect genuine engagement and actual return far more faithfully.

## Related Email Guides

- [Email Click-Through Rate](/guides/email-click-through-rate): Sharpen your CTAs and win more clicks.

- [Email Deliverability](/guides/email-deliverability): Land in the inbox so opens can happen at all.

- [Email Marketing Best Practices](/guides/email-marketing-best-practices): The full email marketing strategy playbook.

---

> Source: https://dev.bitelio.com/guides/email-open-rate

---

# https://dev.bitelio.com/guides/email-segmentation

# Email Segmentation: Strategies and Best Practices

Email segmentation groups subscribers by behavior, engagement, and lifecycle to send more relevant campaigns. Learn segment types, examples, and best practices.

Email segmentation is the practice of dividing your subscriber list into smaller, focused groups so that each group receives messages that are actually relevant to them. Instead of sending one email to everyone and hoping it lands, you match the message to the audience.

It is one of the highest-leverage things you can do in email marketing. The gap between a single batch-and-blast campaign and a well-segmented one shows up in every metric that matters: opens, clicks, revenue, unsubscribes, and long-term deliverability. This guide covers what segmentation is, the segment types worth knowing, how to build segments in practice, examples that consistently perform, and the pitfalls to avoid.

## What Is Email Segmentation?

A segment is a group of contacts who share one or more characteristics. Those characteristics might be something they did (opened your last three emails), something they are (a customer in France), or something about where they are in their journey with you (subscribed yesterday). A segment answers a simple question: _who should receive this message?_

The important distinction is between static and dynamic grouping. A list is a fixed container you add people to. A segment is a live query: you define the rules once, and the audience updates itself as your data changes. When a subscriber opens an email, makes a purchase, or goes quiet for two months, they move in and out of the relevant segments automatically. That is what makes segmentation scalable, even with millions of contacts.

#### Segments vs. tags and fields

Tags and profile fields are the raw ingredients. A segment is the recipe that combines them into an audience you can send to. You might tag someone `webinar-2026` and store their country in a field, then build a segment that targets webinar attendees in North America who have not purchased yet.

## Why Segmentation Matters

Relevance is the entire game. People engage with email that speaks to their situation and ignore email that does not. Segmentation is how you manufacture relevance at scale.

### Higher Engagement

Targeted campaigns consistently outperform broad ones on opens and clicks because the content matches what the reader cares about right now.

### Better Deliverability

Mailbox providers reward engagement. Concentrating volume on people who open and click, and easing off those who do not, keeps you landing in the inbox.

### More Revenue Per Send

A message tied to demonstrated intent, like a browsed category or an abandoned cart, converts far better than a generic promotion sent to the whole list.

### Fewer Unsubscribes

When people only hear from you about things that are relevant, they have far less reason to leave or mark your mail as spam.

#### Segmentation starts with a healthy list

You can only segment on data you actually collect. If you want richer segments, capture the right signals at sign-up and keep your list clean. See our [guide to email list building](/guides/email-list-building) for how to gather the attributes that make segmentation powerful.

## Types of Email Segments

Most useful segments fall into four broad families. You will usually combine them, but it helps to understand each one on its own.

### Behavioral Segments

Behavioral segments group people by what they did. Clicks on a specific link, pages visited, products browsed, a form submitted, or a purchase completed all count as behavior. These segments are powerful because action reveals intent far more reliably than anything a subscriber tells you about themselves. Someone who clicked a pricing link and viewed a demo is a different audience from someone who only ever opens your newsletter.

### Engagement Segments

Engagement segments group people by how active they are with your email specifically, usually measured by recency of opens and clicks. Typical buckets are highly engaged (opened in the last 30 days), moderately engaged, lapsing (no activity in 60 to 90 days), and dormant. This is the most important family for protecting deliverability, because it lets you re-engage the lapsing group with a dedicated campaign and suppress the truly dead weight before it drags your reputation down.

### Demographic and Profile Segments

Demographic segments use attributes about who the person is: location, language, job role, company size, industry, plan tier, or any custom field you store. These are useful for localizing content, complying with regional rules, and tailoring messaging to different types of customers. They tend to be more stable than behavioral segments and pair well with them, for example, "enterprise buyers in the EU who clicked the security page".

### Lifecycle Segments

Lifecycle segments group people by where they are in their relationship with you: brand-new subscriber, onboarding, active customer, at-risk, churned, or win-back candidate. The same person moves through these stages over time, and the right message changes at each one. A welcome series, an onboarding nudge, and a win-back offer are all lifecycle-driven. These segments are the backbone of automated, evergreen email.

## How to Build a Segment

Good segments are built backward from a decision, not forward from your data. Work through these steps.

1

### Start From the Message

Decide what you want to say and what action you want. "Announce a new feature to people who would care" or "win back subscribers going quiet" tells you exactly who the segment should include.

2

### Pick the Signals

Identify the data that defines that audience: an event (clicked a link), a profile field (country), an engagement window (opened in 30 days), or a tag. Confirm you actually collect it.

3

### Write the Conditions

Combine your signals with AND / OR logic. Layering conditions ("engaged AND in the EU AND has not purchased") sharpens the audience, but each extra condition also shrinks it, so add rules deliberately.

4

### Check the Size

Preview how many contacts match. If the segment is tiny, loosen a condition; if it is nearly your whole list, you have not really segmented. Aim for an audience large enough to be worth a dedicated send.

5

### Send, Automate, and Refine

Attach the segment to a campaign or an automation so it stays evergreen. Then watch performance and adjust the rules over time as you learn what the audience responds to.

#### Dynamic segments in Bitelio

With [Bitelio segments](/features/segments) you build these rules visually and the audience re-evaluates itself automatically. Contacts join and leave a segment as their behavior and data change, so an automation attached to a segment keeps working without manual list maintenance.

## Segment Examples That Work

If you are not sure where to start, these segments earn their keep for almost every sender.

| Segment | Who it targets | What to send |
| --- | --- | --- |
| New subscribers | Joined in the last 7 days | Welcome series, best-of content |
| Engaged non-buyers | Opens or clicks but never purchased | First-purchase offer, social proof |
| Lapsing subscribers | No open in 60 to 90 days | Re-engagement campaign, preference update |
| Cart or checkout abandoners | Started but did not complete a purchase | Reminder, incentive, urgency |
| VIP customers | Repeat buyers or high lifetime value | Early access, loyalty perks, referrals |
| Location-based | Subscribers in a country or region | Localized offers, events, currency |

Notice how each example pairs a clearly defined audience with a message that only makes sense for that audience. That pairing is the point of segmentation. If the same email would work just as well for everyone, you probably do not need a segment for it.

## Common Segmentation Pitfalls

### ✗ Over-segmenting

Dozens of narrow segments create maintenance overhead and audiences too small to be statistically or commercially meaningful. Start with a handful that map to real decisions and grow from there.

### ✗ Segmenting on data you do not have

A segment is only as good as the underlying data. If you never collect job role or purchase history, you cannot segment on it. Decide what you want to target first, then make sure you are capturing it.

### ✗ Ignoring engagement

Sending every campaign to your entire list, including people who have not opened in a year, erodes deliverability for everyone. Always factor engagement recency into who receives a broad send.

### ✗ Letting segments go stale

Static, manually maintained groups drift out of date fast. Prefer dynamic segments that re-evaluate on their own, and periodically revisit the rules to confirm they still reflect your goals.

### ✗ Treating segmentation as a substitute for good content

Precise targeting will not save a weak offer or a boring email. Segmentation multiplies the impact of good content; it does not replace it. For the fundamentals, see our best-practices guide below.

## Related Guides

- [Email List Building](/guides/email-list-building): Collect the subscribers and attributes that make segmentation possible.

- [Email Marketing Best Practices](/guides/email-marketing-best-practices): The fundamentals that make every segmented campaign perform better.

- [Bitelio Segments](/features/segments): Build dynamic, self-updating segments visually inside Bitelio.

---

> Source: https://dev.bitelio.com/guides/email-segmentation

---

# https://dev.bitelio.com/guides/email-sender-reputation

# Email Sender Reputation: How to Earn It, Keep It & Repair It

How email sender reputation is scored, the factors that raise or sink it, and step-by-step strategies to build, protect, and recover the trust that drives deliverability.

Email sender reputation is the trust rating that mailbox providers attach to your sending domain and IP address. No other single factor weighs more heavily on whether your messages land in the inbox or get shunted to spam.

The closest analogy is a credit score, but for email: keep it healthy and your mail sails into the inbox; let it slip and you're looking at spam folders or outright blocks. Below we break down how the score works and what it takes to build and protect it.

## What is Email Sender Reputation?

Providers like Gmail, Outlook, and Yahoo assign your domain and IP a score, usually on a 0-100 scale. The inputs include your track record as a sender, how recipients engage with your mail, how often they complain, whether you authenticate, and the overall health of your list.

80-100

### Excellent

Reliable inbox delivery, a trusted sending identity, engaged recipients, full authentication

50-79

### Moderate

Occasional spam-folder placement and mixed signals—improvement needed

<50

### Poor

The bulk of your mail is spammed or blocked—a full-blown deliverability crisis

#### Domain vs IP Reputation

Providers score your **sending domain** (yourdomain.com) and your **IP address** independently, and both count. The domain score follows you wherever you send from; an IP score resets when you move to a different IP—though the new one starts with no history to its name.

## What Affects Sender Reputation?

### 1\. Spam Complaint Rate

**Impact: Critical.** Every "report spam" click cuts deep into your score. Keep complaints under 0.1% (that's 1 per 1,000 sends)—once you hit 0.3%, alarm bells should ring.

Prevention: Mail only confirmed opt-ins, deliver genuine value, and never hide the unsubscribe link.

### 2\. Engagement Metrics

**Impact: Very High.** Providers observe every open, click, reply, forward, and delete. Active engagement proves your mail is wanted; a wall of silence reads like spam.

Boost engagement: Match relevant, useful content to the subscribers who asked for it.

### 3\. Bounce Rate

**Impact: High.** Frequent bounces—hard ones above all—betray a neglected list, bought addresses, or spam traps lurking in your data. Keep the overall rate below 2%.

Prevent bounces: Confirm signups with double opt-in, validate addresses, and suppress hard bounces on sight.

### 4\. Email Authentication

**Impact: High.** SPF, DKIM, and DMARC together certify that your mail really comes from you. Their absence is an instant credibility problem in providers' eyes.

Required: Get all three protocols (SPF, DKIM, DMARC) live before you scale.

### 5\. Spam Trap Hits

**Impact: Critical.** Spam traps are decoy addresses planted to expose careless senders. A single hit can put you on a blacklist overnight.

Avoid: Refuse purchased lists, insist on double opt-in, and retire stale addresses on schedule.

### 6\. Sending Volume & Consistency

**Impact: Moderate.** Providers distrust erratic behavior—an abrupt volume spike, or months of silence broken by a massive blast, both raise suspicion.

Best practice: Keep a steady rhythm and grow volume gradually through a proper warm-up.

### 7\. Content Quality

**Impact: Moderate.** Filter-bait content—link stuffing, deceptive subjects, SHOUTING CAPS—both trips spam filters and depresses engagement.

Write naturally: Professional copy that delivers exactly what the subject line promised.

### 8\. Blacklist Status

**Impact: Critical.** An entry on a major blacklist (Spamhaus, Barracuda, SURBL) can shut down your delivery to entire mail systems at once.

Monitor: Run routine blacklist checks and pursue delisting the moment you find yourself listed.

### 9\. Sending History

**Impact: Cumulative.** Trust accrues send by send. A brand-new domain or IP starts from zero, which is precisely why gradual warm-up exists.

For new senders: Begin small and scale volume steadily across 4-8 weeks.

## How to Build Sender Reputation

Starting from nothing—a fresh domain or IP—means playing the long game and doing everything by the book:

1

### Warm Up New IPs and Domains

Scale sending volume in stages across 4-8 weeks, leading with the subscribers who engage most.

Example Warm-Up Schedule

```
Week 1:  200-500 emails/day
Week 2:  500-1,000 emails/day
Week 3:  1,000-5,000 emails/day
Week 4:  5,000-10,000 emails/day
Week 5:  10,000-20,000 emails/day
Week 6:  20,000-50,000 emails/day
Week 7:  50,000-100,000 emails/day
Week 8+: Full volume

Adjust based on engagement and bounce rates.
```

2

### Start with Highly Engaged Subscribers

Limit warm-up sends to people with recent opens or clicks. Strong early engagement is the fastest route to a positive first impression with providers.

3

### Implement Full Authentication

Get SPF, DKIM, and DMARC configured before the first campaign leaves the gate. Without authentication, reputation-building never gets off the ground.

4

### Maintain Consistent Sending

A predictable daily or weekly cadence earns provider trust in a way that sporadic mega-blasts never will.

5

### Use Double Opt-In

Confirm every address before it joins the list. You get verified, willing subscribers—and spam traps never make it through the door.

6

### Monitor Metrics Closely

Watch bounces, complaints, and engagement throughout the warm-up. The moment numbers slide, pause your volume increases and shore up list quality first.

7

### Provide Immediate Value

First impressions compound. Make good on whatever your signup form promised, right away—strong engagement on those opening sends fast-tracks your reputation.

## Maintaining Good Sender Reputation

Reputation isn't a trophy—it's upkeep. Here's the routine:

### Clean Your List Regularly

On a 6-12 month cycle, either win back or let go of dormant subscribers:

-   • Run re-engagement campaigns aimed at the inactive
-   • Drop anyone who stays unresponsive
-   • Purge hard bounces the moment they appear
-   • Retire chronic soft bouncers (3-5 failures)

### Make Unsubscribing Easy

Counterintuitive but true: a friction-free exit door protects you. Trap people on your list and they'll escape via the spam button—a far costlier outcome.

-   • Put a visible one-click unsubscribe in every send
-   • Act on opt-outs instantly, no confirmation hoops
-   • Treat every unsubscribe as final

### Monitor Reputation Metrics

Your weekly checklist:

-   • Delivery rate (target: 98%+)
-   • Spam complaint rate (target: <0.1%)
-   • Bounce rate (target: <2%)
-   • Opens and clicks
-   • Blacklist status (check monthly)
-   • Sender Score (review quarterly)

### Segment and Personalize

Aim each send at the group it actually serves. The engagement lift from segmentation feeds straight back into your reputation score.

### Use Separate Domains for Different Email Types

Wall off your mission-critical transactional mail from marketing activity:

-   • Transactional: transact.yourdomain.com
-   • Marketing: news.yourdomain.com or marketing.yourdomain.com
-   • Benefits: A marketing misstep can't take your receipts and password resets down with it

## Recovering from Damaged Reputation

A bruised reputation can heal—but only with methodical work and real patience:

1

### Identify the Root Cause

Audit your recent sends: where did complaints spike, bounces surge, or engagement crater? Check blacklists too. Nothing improves until the true cause is found and fixed.

2

### Clean Your List Aggressively

Cut every disengaged subscriber, every bounced address, everyone silent for 6+ months. The list gets smaller—but for recovery, a lean engaged list is worth ten times a bloated one.

3

### Reduce Volume Temporarily

Throttle sending down 50-70% while repairs are underway, mailing only your most engaged readers. Earn the trust back first; scale up second.

4

### Request Blacklist Removal

Pinpoint which lists carry you, resolve whatever landed you there, then file removal requests—nearly every blacklist offers a process for it. Transparency about your fixes helps your case.

5

### Send Valuable, Engaging Content

The way back runs through content people genuinely want. Ease off the promotions and lead with substance—rising engagement is how you show providers the problem is fixed.

6

### Be Patient

Plan on 4-12 weeks of spotless sending before the score meaningfully recovers. Keep watching the metrics, and resist ramping volume back up prematurely.

#### Severe Damage May Require Starting Fresh

Sometimes the damage runs too deep—a sender score under 30, entries on multiple blacklists, outright blocks from major providers. At that point, rebuilding on a fresh subdomain or IP may be more realistic than repair. Treat it strictly as a last resort.

## Reputation Monitoring Tools

### Google Postmaster Tools

Google's free dashboard for Gmail delivery—covers your domain reputation, spam rates, authentication results, and encryption.

[postmaster.google.com →](https://postmaster.google.com)

### Microsoft SNDS

Smart Network Data Services reveals how Microsoft's systems rate your IPs, spam complaint data included.

[Microsoft SNDS →](https://sendersupport.olc.protection.outlook.com/snds/)

### Sender Score (Validity)

A free 0-100 reputation rating built from industry-wide data—the de facto standard benchmark for IP reputation.

[Check Sender Score →](https://www.validity.com/everest/senderscore/)

### MXToolbox Blacklist Check

Scans the major blacklists for your domain or IP. Make it a recurring check so listings never catch you off guard.

[MXToolbox →](https://mxtoolbox.com/blacklists.aspx)

### Talos Intelligence

Cisco's Talos service publishes sender reputation data—look up how your IP is rated and file for delisting where necessary.

[Talos Intelligence →](https://talosintelligence.com)

### BarracudaCentral

Query your standing on Barracuda's reputation and blocklist systems—particularly relevant when you send to enterprise mail environments.

[BarracudaCentral →](https://www.barracudacentral.org/lookups)

## Related Email Guides

- [Email Deliverability](/guides/email-deliverability): The full guide to reaching the inbox.

- [Email Bounce Rate](/guides/email-bounce-rate): Keep bounces down and your reputation up.

- [What is DKIM?](/guides/what-is-dkim): Authentication that strengthens your reputation.

---

> Source: https://dev.bitelio.com/guides/email-sender-reputation

---

# https://dev.bitelio.com/guides/email-warmup

# Email Warmup: How to Warm Up a New Domain or IP

Learn how email warmup works and follow a week-by-week ramp-up schedule to build sender reputation, avoid spam filters, and reach the inbox.

Email warmup is the practice of gradually building up how much email you send from a new domain or IP address so that mailbox providers learn to trust you before you send at full volume.

Think of it like establishing credit. A brand-new domain has no history, so providers like Gmail, Outlook, and Yahoo treat it with suspicion. Start slow, prove you send wanted mail, and your reputation grows. Blast thousands of messages on day one and you look exactly like a spammer.

## What Is Email Warmup?

Email warmup is a controlled ramp-up of sending volume over a period of weeks. Rather than launching your full campaign the moment your domain is authenticated, you begin with a small number of emails to your most engaged contacts and increase the count steadily each day.

The goal is to generate a track record of positive engagement signals, such as opens, replies, and low complaint rates, that tells receiving servers your mail is legitimate and wanted. Every increment is a small test: if the signals stay healthy, you push a bit harder the next day; if they degrade, you hold steady until they recover.

Warmup only works if the foundations are in place first. Before you send a single message, publish your [SPF](/guides/what-is-spf), [DKIM](/guides/what-is-dkim), and [DMARC](/guides/what-is-dmarc) records and confirm they are valid with an [SPF checker](/tools/spf-checker). Warming up a domain that fails authentication just teaches providers to distrust you faster.

## Why Email Warmup Matters

Mailbox providers decide where to place your mail based largely on your sender reputation. A new domain or IP has no reputation at all, and providers treat unknown senders cautiously by default. Warmup is how you convert that neutral, cautious state into an established, trusted one.

### Avoids the Spam Folder

A sudden spike in volume from an unknown sender is a textbook spam signal. Ramping gradually keeps you off filters and blocklists while your reputation is still forming.

### Builds Sender Reputation

Consistent, engaged sending over time is exactly what providers reward. Warmup produces the positive history that underpins long-term inbox placement.

### Protects Your Domain

A bad first impression is expensive to fix. A negative reputation from an over-eager launch can take weeks to repair, during which nearly all of your mail may be filtered.

### Establishes Volume Limits

Providers apply rate limits to new senders. Warmup raises those limits in step with your reputation, so you can eventually send at full scale without throttling.

#### Reputation Is Earned, Not Configured

No DNS record or setting can shortcut a sending reputation. SPF, DKIM, and DMARC prove you are who you claim to be, but only real, engaged sending over time earns the trust that lands you in the inbox.

## Domain Warmup vs. IP Warmup

Reputation is tracked against both your sending domain and the IP address you send from. Which one you need to warm up depends on what is actually new in your setup.

### When to Warm Up a Domain

Any brand-new sending domain needs warmup, because it starts with zero history regardless of the IP behind it. This is true even when you send through a mature shared IP pool: the pool provides a warm IP, but your domain reputation is unique to you and begins from scratch. Domain warmup is the part almost everyone needs.

### When to Warm Up a Dedicated IP

A new dedicated IP needs its own warmup because reputation is also tied to the IP address. Dedicated IPs make sense for high-volume senders who want full control over their reputation, but they demand consistent volume to stay warm. If both the domain and the dedicated IP are new, warm them together and ramp especially slowly, since you are building two reputations at once.

#### Shared vs. Dedicated IPs

Shared IP pools are best for lower or irregular volume, since the aggregate traffic keeps the IP warm even when you go quiet. Dedicated IPs suit senders who reliably push tens of thousands of messages per day and want their reputation isolated from other senders.

## A Sample Email Warmup Schedule

The schedule below is a practical starting point for warming up toward a target of roughly 100,000 emails per day. Treat the numbers as guidelines, not guarantees: your real pace should follow your engagement metrics. If bounces or complaints climb, repeat a week before advancing.

| Week | Daily Volume (approx.) | Focus |
| --- | --- | --- |
| Week 1 | 20 to 200 per day | Most engaged contacts only |
| Week 2 | 500 to 1,000 per day | Recent openers and clickers |
| Week 3 | 2,000 to 5,000 per day | Active subscribers |
| Week 4 | 10,000 to 20,000 per day | Broaden to the wider active list |
| Week 5 | 30,000 to 50,000 per day | Add lightly engaged segments |
| Week 6+ | 75,000 to full volume | Full list once metrics hold steady |

Spread each day's volume across sending hours rather than firing it all at once, and warm up to each major mailbox provider in proportion to how much of your list lives there. A low-volume sender targeting only a few thousand messages per day can compress this into two or three weeks; a very high-volume sender may need eight weeks or more.

## Engagement-First Sending

The single most important warmup principle is to send to your most engaged recipients first. Engagement is the strongest positive signal a mailbox provider can see, so front-loading your ramp with people who open, click, and reply builds reputation far faster than raw volume ever could.

Start with contacts who have opened or clicked in the last 30 days, then expand to 60 and 90 days as your reputation strengthens. Hold back cold, unengaged, or purchased contacts until the very end of the process, if you include them at all. Sending to stale addresses early produces bounces and spam complaints that can undo days of progress.

Content matters too. During warmup, send the mail people most want, such as welcome messages, order confirmations, and content from subscribers who recently opted in. Make unsubscribing easy so that uninterested recipients leave quietly instead of marking you as spam, which is far more damaging to your reputation.

## Monitoring Your Warmup

Warmup is a feedback loop, not a fixed timetable. After every increase in volume, check your key signals before ramping again. If any of them move in the wrong direction, pause and hold volume steady until they recover.

### Key Signals to Watch

| Signal | Healthy Target | Why It Matters |
| --- | --- | --- |
| Bounce rate | Under 2% | High bounces signal a poor-quality list |
| Complaint rate | Under 0.1% | Spam reports directly damage reputation |
| Open rate | Above your list average | Confirms recipients want your mail |
| Spam placement | Falling over time | Shows filters are learning to trust you |

Beyond your own analytics, use free provider tools. Google Postmaster Tools reports your domain and IP reputation, spam rate, and authentication results for Gmail, while Microsoft SNDS does the same for Outlook. Both give you an outside view that your sending platform alone cannot.

For a deeper look at the metrics that define a good sender, see our guides on [email sender reputation](/guides/email-sender-reputation) and [email deliverability](/guides/email-deliverability).

## Email Warmup Tools

A few categories of tooling make warmup easier to run and measure:

### Sending platform controls

A good email platform lets you cap daily volume, schedule sends, and segment by engagement, which is everything you need to run a manual warmup with full control over deliverability.

### Reputation monitoring

Google Postmaster Tools and Microsoft SNDS are free and essential for tracking how the two largest providers perceive you throughout the ramp.

### Authentication checkers

Before you begin, confirm your records resolve correctly with an [SPF checker](/tools/spf-checker). Broken authentication undermines every day of warmup that follows.

### Automated warmup services

Some services exchange artificial messages between seed inboxes to simulate engagement. These can help for cold-outreach mailboxes, but be cautious: fake engagement is not a substitute for sending mail that real recipients actually want, and some providers frown on it.

## Common Email Warmup Mistakes to Avoid

### ✗ Ramping too fast

Doubling volume every day regardless of your metrics is the most common mistake. Let engagement, not impatience, set your pace, and repeat a step whenever your signals wobble.

### ✗ Starting with a cold or purchased list

Warming up with unengaged or bought contacts guarantees bounces and complaints. Always begin with the recipients most likely to open and click.

### ✗ Skipping authentication

Warming up before SPF, DKIM, and DMARC are valid teaches providers to distrust you. Set up and verify authentication first, every time.

### ✗ Sending inconsistently

Large gaps in your sending schedule let reputation decay, especially on dedicated IPs. Keep volume steady and predictable rather than sending in erratic bursts.

### ✗ Ignoring the feedback

A rising complaint rate or falling open rate is telling you to slow down. Pushing more volume through a degrading reputation only deepens the hole.

#### Bitelio Makes Warmup Straightforward

Bitelio gives you the segmentation, scheduling, and deliverability analytics you need to run a controlled warmup, and surfaces bounce and complaint rates in real time so you always know when to advance and when to hold.

## Related Deliverability Guides

- [Email Deliverability Guide](/guides/email-deliverability): Proven strategies to reach the inbox and avoid spam filters.

- [Email Sender Reputation](/guides/email-sender-reputation): Understand and improve the reputation warmup is meant to build.

- [SPF Checker](/tools/spf-checker): Verify your authentication is valid before you start warming up.

---

> Source: https://dev.bitelio.com/guides/email-warmup

---

# https://dev.bitelio.com/guides/gdpr-email-compliance

# GDPR Email Compliance: A Practical Guide

A practical guide to GDPR email compliance: lawful basis, consent and double opt-in, data subject rights, retention, DPAs, and EU data hosting.

If you send email to people in the European Union, the General Data Protection Regulation (GDPR) applies to you, whether or not your company is based in Europe. Email is personal data by definition, and a marketing list is a structured record of who those people are and how they behave. GDPR governs how you collect, store, use, and eventually delete that data.

The good news is that GDPR compliance and good email practice pull in the same direction. Clean, consented lists deliver better, engage more, and complain less. This guide walks through the practical steps that keep your email programme on the right side of the regulation, from choosing a lawful basis to signing a data processing agreement.

#### This is not legal advice

This guide is a practical overview to help you understand the concepts and ask the right questions. It is not legal advice, and it does not create a lawyer-client relationship. For decisions that carry real risk, consult a qualified data protection advisor familiar with your specific circumstances and jurisdiction.

## GDPR and Email: The Basics

GDPR protects the personal data of people in the EU and the wider European Economic Area. For an email sender, almost everything you store about a subscriber counts as personal data: their email address, name, IP address, location, and even behavioural signals like opens and clicks. Two roles matter here.

### You are the data controller

You decide why and how the personal data is processed. That makes you accountable for having a lawful basis, informing subscribers, and honouring their rights.

### Your platform is a processor

An email service that sends on your instructions is a data processor. It handles the data but only for the purposes you define, which is why a written agreement between you matters.

GDPR is built on a handful of principles: process data lawfully and transparently, only for specified purposes, keep it accurate, collect no more than you need, retain it no longer than necessary, and keep it secure. Every recommendation below is really one of those principles applied to email.

## Lawful Basis and Consent

You cannot process personal data under GDPR without a lawful basis. For email marketing, two bases come up most often: consent and legitimate interest. Choosing the right one, and being able to explain why, is the foundation of a compliant programme.

### Consent (opt-in)

For consumer marketing, consent is usually the cleanest basis, and the ePrivacy Directive that sits alongside GDPR generally requires it for unsolicited marketing email. Valid consent must be freely given, specific, informed, and unambiguous. In plain terms: the subscriber has to take a deliberate action, such as ticking an unticked box or clicking a subscribe button, after being told clearly who you are and what they are signing up for. Pre-ticked boxes, buried terms, and bundled consent ("agree to marketing to access this download") do not count.

### Legitimate interest and the soft opt-in

Legitimate interest can support some business-to-business outreach and closely related communications, but it requires a documented balancing test weighing your interest against the recipient's rights and expectations. Many EU countries also allow a limited "soft opt-in" to existing customers for similar products, provided you gave them a chance to opt out at collection and in every message. These paths are narrower and riskier than consent, so use them deliberately and record your reasoning.

#### Keep proof of consent

Whatever basis you rely on, record the evidence: when and how someone subscribed, the wording they saw, and the source. If a regulator or subscriber ever asks, you should be able to show exactly how you obtained permission to email them.

## Double Opt-In: Proving Consent

GDPR does not literally mandate double opt-in, but it is the most reliable way to demonstrate that consent was genuine. With double opt-in, a new subscriber first submits their address, then receives a confirmation email and only joins your list after clicking the link inside it. That click gives you a timestamped, verifiable record that the person controls the mailbox and actively chose to hear from you.

The compliance benefit comes with a deliverability bonus. Confirmation weeds out typos, fake addresses, and malicious signups before they ever reach your active list, so your engagement rates stay high and your sender reputation stays clean. For a step-by-step setup, see our dedicated [double opt-in guide](/guides/double-opt-in).

## Data Subject Rights

GDPR gives individuals a set of rights over their personal data, and you must be able to act on them without undue delay, generally within one month. For an email programme, two rights come up most frequently.

### Right of access

A subscriber can ask what personal data you hold about them and how you use it. You should be able to export their profile, subscription history, and engagement data in a readable form. Keeping your data in one system rather than scattered across spreadsheets makes this straightforward.

### Right to erasure

Also called the right to be forgotten, this lets a person ask you to delete their data. When you delete, remove them everywhere: your active list, your platform, and any exports or backups within your control. One nuance for email: you may keep a minimal suppression record of an address so you never accidentally re-import and email someone who asked to be removed, which is itself a legitimate purpose.

#### Rights extend to your processor

When a subscriber exercises a right, your email platform (as processor) must be able to support you, for example by deleting the person's data on request. This is exactly the kind of obligation a data processing agreement pins down.

## Make Unsubscribe Effortless

Every marketing email must give recipients a simple, free way to opt out, and you must honour those requests promptly. In practice this means a visible unsubscribe link in the footer of every campaign, plus a list-unsubscribe header so mailbox providers can offer one-tap removal directly in the inbox. Since 2024, major providers such as Gmail and Yahoo require one-click unsubscribe for bulk senders, so this is both a legal and a deliverability expectation.

Do not make people log in, reply, or navigate a multi-step survey to leave. A slow or hidden unsubscribe drives recipients to hit "report spam" instead, which harms your reputation far more than losing one subscriber. If you want to reduce churn, offer a preference centre where people can dial down frequency rather than only choosing all-or-nothing, but always keep a genuine full opt-out available.

## Data Minimization and Retention

GDPR asks you to collect only the data you actually need and to keep it only as long as you need it. Both principles are easy to apply to email.

### Collect less

Keep signup forms short. If you only need an email address to send a newsletter, do not demand a phone number, birth date, or job title. Every extra field is more data to secure and justify.

### Keep it for less time

Set a retention policy for inactive contacts. If someone has not engaged in, say, 12 to 24 months, consider a re-permission campaign and then remove them. Stale data adds risk without adding value.

Retention discipline also improves performance. Pruning unengaged contacts lifts your open and click rates and protects your sender reputation, which is one of the many places where privacy and [email deliverability](/guides/email-deliverability) reinforce each other.

## Processors and Data Processing Agreements

The moment you use an email platform to send on your behalf, that platform becomes a data processor under GDPR. Article 28 requires a written contract, a data processing agreement (DPA), between you as controller and the processor. A solid DPA sets out:

-   •The nature and purpose of the processing, and the categories of data and data subjects involved.
-   •The security measures the processor maintains to protect the data.
-   •Rules for engaging sub-processors and for any international data transfers.
-   •How the processor helps you meet data subject requests and breach notifications.

Before you send a single campaign, review and accept your provider's DPA and check who their sub-processors are. Bitelio publishes its terms so you can review them up front, see our [Data Processing Agreement](/dpa).

## Where Your Data Lives: The EU-Hosting Angle

GDPR restricts sending personal data outside the EU and EEA unless the destination offers adequate protection or you put a transfer mechanism in place, such as Standard Contractual Clauses. Transfers to countries without an adequacy decision have been a persistent source of legal uncertainty for European businesses.

Keeping your email data on infrastructure hosted and processed within the EU sidesteps much of that complexity. There is no cross-border transfer to justify, no reliance on contested legal mechanisms, and a clear, simple story to tell European customers and regulators about where their information sits. For a company serving EU audiences, an EU data footprint is one of the most practical ways to lower compliance risk.

#### Built for EU senders

Bitelio is positioned for European teams, with EU-based data handling and a published DPA, so keeping your email programme inside the EU does not require extra plumbing on your side.

## A Practical GDPR Email Checklist

Pulling it together, here is a short checklist you can run against your current programme:

1

Confirm a lawful basis (usually consent) for every contact on your list.

2

Use clear, unbundled opt-in forms and keep proof of when and how people subscribed.

3

Adopt double opt-in to verify consent and protect deliverability.

4

Include a working one-click unsubscribe in every email and honour opt-outs promptly.

5

Be ready to answer access and erasure requests within one month.

6

Collect only necessary fields and set a retention policy for inactive contacts.

7

Sign a DPA with your email provider and review their sub-processors.

8

Prefer EU-based hosting and processing to minimise international transfer risk.

## Related Guides

- [Double Opt-In Explained](/guides/double-opt-in): Set up confirmed opt-in to prove consent and clean your list.

- [Email Deliverability Guide](/guides/email-deliverability): How consent and list hygiene improve inbox placement.

- [Data Processing Agreement](/dpa): Review the DPA that governs Bitelio as your email processor.

---

> Source: https://dev.bitelio.com/guides/gdpr-email-compliance

---

# https://dev.bitelio.com/guides/reduce-spam-complaints

# How to Reduce Email Spam Complaints

Learn how to reduce spam complaints and protect your sender reputation with clear expectations, easy unsubscribes, segmentation, and list hygiene.

A spam complaint is one of the loudest negative signals in email. Every time a recipient clicks "mark as spam," they tell their mailbox provider that your mail is unwanted, and providers listen closely. Even a small number of complaints can quietly push your messages out of the inbox, including messages to people who genuinely want to hear from you.

The good news is that spam complaints are almost entirely preventable. This guide explains what a complaint actually is, why complaints damage your reputation and deliverability, what causes them, and the concrete habits that keep your complaint rate low. It also covers how to monitor complaints through feedback loops and postmaster tools so problems surface early.

## What Is a Spam Complaint?

A spam complaint happens when a recipient clicks the "Report spam" or "Junk" button inside their email client, such as Gmail, Outlook, or Apple Mail. That single action does two things: it moves your message to the recipient's spam folder, and it reports your sending domain and IP address to the mailbox provider as a source of unwanted mail.

Your **spam complaint rate** is the number of complaints divided by the number of emails delivered, usually expressed as a percentage. If you deliver 10,000 emails and 12 people mark them as spam, your complaint rate is 0.12%. Mailbox providers watch this number continuously, and they compare it against their own thresholds for what a trustworthy sender looks like.

#### A Complaint Is Not the Same as a Spam Filter Block

A spam filter block is an automated decision made by the provider's algorithms. A spam complaint is a deliberate human action by one of your recipients. Complaints carry more weight precisely because a real person chose to report you, and they accumulate against your reputation over time.

## Why Spam Complaints Hurt Your Deliverability

Complaints are damaging because mailbox providers treat them as a direct verdict from the people you are trying to reach. A handful of complaints in a single campaign can lower your [sender reputation](/guides/email-sender-reputation) and change how every future message is filtered, not just the campaign that triggered them.

### Lower Inbox Placement

As your complaint rate climbs, providers route more of your mail to the spam folder, including messages to subscribers who never complained and still want your emails.

### Damaged Domain and IP Reputation

Complaints attach to your sending domain and IP. Once that reputation drops, it takes weeks of clean, low-complaint sending to rebuild the trust you lost.

### Bulk Sender Enforcement

Gmail and Yahoo require bulk senders to keep complaint rates under 0.3% and to aim below 0.1%. Cross those lines and your mail can be throttled or blocked outright.

### Shared Reputation Impact

On shared sending infrastructure, high complaints from one sender can affect neighbors. Providers may also tighten filtering across your entire account.

#### Keep Complaints Below 0.1%

The practical target is a complaint rate under 0.1%, which is one complaint for every 1,000 delivered emails. Treat 0.3% as a hard ceiling you never want to approach. If you routinely see complaint rates above 0.1%, something upstream in how you collect or engage subscribers needs to change.

## Common Causes of Spam Complaints

Almost every complaint traces back to a mismatch between what the recipient expected and what they received. The most frequent causes are:

### They Do Not Remember Signing Up

Purchased lists, addresses scraped from the web, or sign-ups from months ago with no follow-up all produce recipients who see your name and assume it is spam. If they do not recognize you, they will report you.

### You Send Too Often

Frequency fatigue is a leading driver of complaints. Someone who was happy to hear from you weekly may hit the spam button when daily emails start crowding their inbox.

### The Content Is Not Relevant

Sending the same message to your entire list means many recipients get offers and topics that do not apply to them. Irrelevant mail feels like spam even when the recipient opted in.

### Unsubscribing Is Too Hard

When the unsubscribe link is buried, tiny, or forces a multi-step login, people take the faster route and click "mark as spam" instead. That single shortcut costs you far more than an unsubscribe would.

### Misleading Subject Lines or Senders

Clickbait subject lines, a "from" name recipients do not recognize, or content that does not match the subject all break trust and provoke complaints.

## How to Reduce Spam Complaints

Reducing complaints comes down to earning permission, respecting attention, and making it easy for people to leave. Build these six habits into your program.

1

### Set Clear Expectations at Signup

Tell people exactly what they are subscribing to and how often you will email them. Use an explicit opt-in, confirm the subscription, and send a welcome message immediately so your name is fresh when your first campaign lands. Consider double opt-in to confirm intent and filter out mistyped addresses.

2

### Send at a Sensible Frequency

Match your cadence to what recipients agreed to and to what your content can sustain. If you need to send more, offer a preference center where subscribers choose their own frequency rather than forcing it on them. Consistency matters more than volume.

3

### Make Unsubscribing Effortless

Put a clear, visible unsubscribe link in every email and support one-click unsubscribe via the List-Unsubscribe header. When leaving is instant, most people who are done with your mail will unsubscribe instead of complaining, which protects your reputation. This is now required for bulk senders at Gmail and Yahoo.

4

### Send Relevant, Segmented Content

Relevance is the strongest defense against complaints. Use [segmentation](/guides/email-segmentation) to send different messages based on interests, behavior, and lifecycle stage so every recipient gets mail that actually applies to them. Targeted email feels wanted; batch-and-blast feels like spam.

5

### Practice Consistent List Hygiene

Never buy or rent lists, and never email addresses you did not collect yourself. Remove hard bounces immediately, and re-engage or suppress subscribers who have not opened or clicked in a long time. Sending to disengaged contacts increases both complaints and spam-filter placement.

6

### Authenticate Your Email

Set up SPF, DKIM, and DMARC so mailbox providers can verify that your mail is really from you. Authentication does not stop complaints on its own, but it ensures complaints are attributed correctly and prevents spoofers from damaging your domain's reputation on your behalf.

#### Unsubscribes Are Better Than Complaints

Do not fear unsubscribes. A subscriber who opts out cleanly leaves your reputation intact, while a subscriber who reports you as spam damages your inbox placement for everyone else. Make leaving so easy that no one ever needs to reach for the spam button.

## Monitor Complaints with Feedback Loops and Postmaster Tools

You cannot fix what you cannot see. Complaint monitoring turns an invisible reputation problem into a number you can act on, and it lets you suppress complainers before they push your metrics into dangerous territory.

### Feedback Loops (FBLs)

A feedback loop is a service where a mailbox provider forwards you a report every time one of your recipients marks a message as spam. Yahoo, Microsoft, and several other providers offer FBLs. When you enroll, each complaint report identifies the affected address so you can suppress it immediately. Emailing a person who already complained is the fastest way to make things worse, so processing FBL reports promptly is essential.

### Google Postmaster Tools and Microsoft SNDS

Gmail does not offer a per-message FBL, but Google Postmaster Tools shows your aggregate spam complaint rate, domain and IP reputation, and authentication results for mail sent to Gmail. Microsoft's Smart Network Data Services (SNDS) provides similar visibility for Outlook and Hotmail. Check these dashboards regularly and treat any upward trend in the complaint rate as an early warning.

### Act on Every Complaint

When a complaint arrives, suppress the address permanently and never mail it again. Then look for patterns: if complaints spike on a particular campaign, segment, or acquisition source, investigate that source rather than treating each complaint in isolation. Consistent, fast suppression keeps your rate low and signals to providers that you respect recipient choices.

#### Bitelio Handles Complaints Automatically

Bitelio processes feedback-loop reports and complaint notifications for you, automatically suppressing anyone who marks your mail as spam so you never accidentally email them again. It also tracks your complaint rate over time so you can spot and fix problems before they hurt your [deliverability](/guides/email-deliverability).

## Related Deliverability Guides

- [Email Sender Reputation](/guides/email-sender-reputation): Understand the signals that determine whether you reach the inbox.

- [Email Deliverability Guide](/guides/email-deliverability): A complete guide to getting more of your email into the inbox.

- [Email Segmentation](/guides/email-segmentation): Send relevant, targeted content that recipients actually want.

---

> Source: https://dev.bitelio.com/guides/reduce-spam-complaints

---

# https://dev.bitelio.com/guides/transactional-vs-marketing-email

# Transactional vs Marketing Email: What Sets Them Apart

A clear breakdown of transactional vs marketing email—how they differ in purpose, law, infrastructure, and metrics, plus best practices for handling each correctly.

Every email you send falls into one of two very different worlds. Transactional and marketing messages exist for different reasons, answer to different laws, and demand different handling—and mixing them up creates real compliance and deliverability risk.

Below we map out exactly where the line sits, what each category requires legally, and how to run both streams well.

## Quick Comparison

| Aspect | Transactional Email | Marketing Email |
| --- | --- | --- |
| Purpose | Complete a transaction or deliver service information | Promote offerings, content, or the brand itself |
| Trigger | A user action or a system event | A campaign calendar or schedule |
| Consent Required | No (implied by using the service) | Yes (an explicit opt-in) |
| Unsubscribe Link | Optional | Legally mandatory |
| Open Rate | 60-80% (very high) | 15-25% (average) |
| Volume | Modest, driven by events | Large, driven by campaigns |

## What is Transactional Email?

A transactional email fires automatically the moment a user does something or a system event occurs. Its job is to carry information the recipient is actively waiting for—the confirmation, receipt, or credential that keeps their transaction or account moving.

### Common Types of Transactional Emails

#### Account & Authentication

-   • Welcome messages triggered by signup
-   • Address verification and confirmation
-   • Password reset links
-   • New-login alerts
-   • Two-factor authentication codes
-   • Confirmations of account deletion

#### Commerce & Transactions

-   • Order confirmations
-   • Shipping notices
-   • Delivery status updates
-   • Payment receipts
-   • Refund notifications
-   • Invoices

#### Notifications & Alerts

-   • Account activity notifications
-   • Comment and mention alerts
-   • Security warnings
-   • Service status updates
-   • Subscription renewal notices
-   • Trial-ending reminders

#### Account Management

-   • Billing statements
-   • Usage summaries
-   • Profile and account changes
-   • Plan upgrades or downgrades
-   • Subscription confirmations
-   • Deactivation notices

### Transactional Email Best Practices

1

#### Send Immediately

These messages need to land within seconds, minutes at most, of the triggering event. When confirmations lag, users get nervous—and your support queue fills up.

2

#### Prioritize Clarity & Accuracy

Every essential detail belongs in the message: order number, amounts, dates, tracking links. Get any of it wrong and the trust hit is immediate and severe.

3

#### Use Descriptive Subject Lines

The content should be obvious from the subject alone: "Your order #12345 has shipped" beats "Update from YourCompany" every time. No mystery, no guessing.

4

#### Minimize Promotional Content

The transaction is the star; keep it that way. A modest cross-sell block at the foot of the email is fine—converting a receipt into a sales pitch is not.

5

#### Ensure High Deliverability

Run transactional mail on infrastructure of its own. Users literally depend on these messages arriving, so a marketing hiccup must never be able to drag them down.

## What is Marketing Email?

Marketing email is the promotional side of the house: messages designed to nurture relationships, spark engagement, and move recipients toward a purchase. The entry requirement is non-negotiable—people must explicitly opt in first.

### Common Types of Marketing Emails

#### Promotional Campaigns

-   • Product launch announcements
-   • Sales and discount pushes
-   • New feature reveals
-   • Seasonal promotions
-   • Time-limited deals
-   • Flash sales

#### Content Marketing

-   • Newsletters
-   • Blog digest emails
-   • How-to and educational pieces
-   • Industry news and trend reports
-   • Case studies
-   • Webinar invites

#### Nurture & Engagement

-   • Welcome sequences (past the first message)
-   • Onboarding drip campaigns
-   • Re-engagement pushes
-   • Win-back outreach
-   • Customer feedback surveys
-   • Loyalty program news

#### Lifecycle Marketing

-   • Abandoned cart nudges
-   • Personalized product picks
-   • Upsell and cross-sell campaigns
-   • Birthday and anniversary greetings
-   • Renewal reminders (when promotional)
-   • Requests for reviews

### Marketing Email Best Practices

1

#### Always Get Explicit Consent

Collect signups through unambiguous opt-in forms—double opt-in is even better. Adding people without asking, or importing bought lists, is off the table: both GDPR and CAN-SPAM demand real consent.

2

#### Provide Value, Not Just Promotions

Mix genuine usefulness—insight, education, even entertainment—in with the offers. A list fed nothing but sales pitches votes with the unsubscribe link.

3

#### Segment Your Audience

Target sends by behavior, preference, demographic, or engagement level. The difference is stark: segmented campaigns engage 3x better than blanket blasts.

4

#### Make Unsubscribing Easy

A one-click unsubscribe link in every message isn't just the law—it's self-preservation. Readers who can't find the exit reach for the spam button, and that costs you far more.

5

#### Test and Optimize

Subject lines, timing, content, CTAs—put them all through A/B tests. Marketing email is a discipline of iteration; the performance data tells you where to go next.

## Legal Requirements

The law draws a hard line between the two categories, and crossing it carries real consequences—substantial fines plus lasting reputational damage.

### Transactional Email Laws

#### CAN-SPAM (US)

Largely exempt, though deceptive or falsified headers remain prohibited

#### GDPR (EU)

Permitted under "legitimate interest" when needed to deliver the service. Data protection duties still apply, and optional transactional messages should offer an opt-out

#### Key Point

No consent or unsubscribe link is required for genuine transactional mail—but dressing promotional content up as transactional to dodge the rules is itself a legal violation

### Marketing Email Laws

#### CAN-SPAM (US)

-   • A visible opt-out mechanism (unsubscribe link)
-   • Opt-outs honored within 10 business days
-   • A physical mailing address in the message
-   • Advertising identified as such
-   • No deceptive subjects or forged headers

#### GDPR (EU)

-   • Consent via explicit opt-in beforehand
-   • Transparency about how data is used
-   • A simple way to opt out at any moment
-   • Rights to access and erase personal data
-   • Documented proof of consent

#### Don't Abuse the Transactional Category

Passing off marketing content as transactional to sidestep consent rules is both unlawful and a fast way to lose recipient trust. Regulators and mailbox providers watch for exactly this pattern—keep your transactional stream strictly functional.

## Infrastructure & Sending Practices

### Separate Sending Domains

Give each stream its own subdomain:

-   • **Transactional:** transact.yourdomain.com or mail.yourdomain.com
-   • **Marketing:** marketing.yourdomain.com or news.yourdomain.com
-   • **Benefit:** If a marketing campaign runs into deliverability trouble, your mission-critical transactional mail stays unaffected

### Dedicated IP Addresses (High Volume)

Once you're past 100,000 emails/month:

-   • Assign transactional and marketing traffic their own dedicated IPs
-   • Warm each new IP up gradually to establish its reputation
-   • Track the reputation of every IP on its own

### Monitoring & Analytics

Keep the two scorecards apart:

-   • **Transactional:** Delivery rate (target: 99%+), time to delivery, bounce rate
-   • **Marketing:** Opens, CTR, conversions, engagement, unsubscribes

## The Gray Area: What's What?

Not every email sorts itself neatly. Here's how the borderline cases shake out:

### Clearly Transactional

-   ✓ Order confirmations and shipping updates
-   ✓ Password resets and account verification
-   ✓ Billing receipts and invoices
-   ✓ System alerts and security notifications

### Gray Area (Be Careful)

-   • **Cart abandonment:** A plain reminder can pass as transactional; add promotions and it becomes marketing
-   • **Review requests:** Linked to a recent purchase = transactional; sent out of the blue = marketing
-   • **Welcome emails:** The verification message = transactional; the follow-up drip series = marketing
-   • **Renewal reminders:** Pure information = transactional; sprinkled with offers = marketing

### Clearly Marketing

-   ✗ Newsletters and content roundups
-   ✗ Product announcements and promotions
-   ✗ Sales and discount offers
-   ✗ Educational content and webinars
-   ✗ Re-engagement campaigns

#### When in Doubt

Can't decide which bucket an email belongs in? Default to the marketing rules: add the unsubscribe link, secure proper consent, and comply with every marketing regulation. That choice is never wrong.

## Related Email Guides

- [Email API Guide](/guides/email-api-guide): Ship transactional email through an API.

- [Email Marketing Best Practices](/guides/email-marketing-best-practices): The full marketing email playbook.

- [Email Deliverability](/guides/email-deliverability): Get both email streams into the inbox.

---

> Source: https://dev.bitelio.com/guides/transactional-vs-marketing-email

---

# https://dev.bitelio.com/guides/what-is-bimi

# What is BIMI? Brand Indicators for Message Identification

Learn what BIMI is, how it shows your brand logo in the inbox, and how to set it up with DMARC enforcement and a VMC certificate for verified email.

BIMI (Brand Indicators for Message Identification) is an email standard that displays your verified brand logo next to your messages in the recipient's inbox. Instead of a generic gray avatar or an initial, subscribers see your actual logo, the same way they might recognize a familiar shop front on a busy street.

BIMI is not an authentication protocol on its own. It is a visual layer that sits on top of [DMARC](/guides/what-is-dmarc), rewarding domains that have already done the hard work of setting up SPF, DKIM, and DMARC correctly. If your authentication is in order, BIMI turns that behind-the-scenes trust into something your customers can actually see.

## What BIMI Is and Why It Matters

Email is a low-trust medium. Recipients are trained to be suspicious, and rightly so, because spoofing and phishing remain common. BIMI attacks this problem from the recognition side: when your logo appears beside a message, the reader gets an immediate, pre-open signal that the email is genuinely from your brand and has passed authentication. That small visual cue does a lot of work.

### Instant Brand Recognition

Your logo appears in the inbox list and message header before the email is even opened, helping subscribers spot your mail among dozens of competing messages.

### Higher Trust and Engagement

A verified logo signals legitimacy. Brands that adopt BIMI frequently report improved open rates and a stronger sense of authenticity, especially for transactional and receipt emails.

### Anti-Spoofing Reinforcement

Because BIMI only displays when DMARC passes, an impostor cannot borrow your logo. The absence of your usual logo becomes a subtle warning sign for attentive recipients.

### A Reason to Fix Authentication

The prize of a visible logo gives teams a concrete, marketing-friendly reason to finally push DMARC to enforcement, which benefits deliverability across the board.

#### BIMI Is a Reward, Not a Shortcut

You cannot use BIMI to skip the fundamentals. It is designed to surface trust that already exists in your authentication setup. If SPF, DKIM, and DMARC are not solid, no logo will appear.

## How BIMI Works

BIMI ties together DNS, DMARC, and a hosted logo file. Here is what happens from setup to the moment your logo shows up in someone's inbox:

### 1\. You Publish a BIMI DNS Record

You add a TXT record at a special BIMI selector on your domain that points to the URL of your logo and, in most cases, to a verification certificate.

### 2\. You Send an Authenticated Email

You send mail from your domain as usual. That message must pass SPF or DKIM with proper alignment so that DMARC evaluates to a pass.

### 3\. The Receiver Checks DMARC, Then BIMI

The receiving provider first confirms the message passes your DMARC policy at enforcement. Only then does it look up your BIMI record, fetch the logo, and (where required) validate the certificate.

### 4\. Your Logo Is Displayed

If everything checks out, the provider renders your brand logo next to the message. If any step fails, the provider simply falls back to its default avatar and nothing breaks.

The BIMI record itself is a TXT record published at the `default._bimi` selector under your domain. A typical record looks like this:

Example BIMI DNS Record

```
default._bimi.yourdomain.com.  IN TXT  "v=BIMI1; l=https://yourdomain.com/bimi/logo.svg; a=https://yourdomain.com/bimi/vmc.pem"

# Breaking down the components:
# v=BIMI1                          -> BIMI version (always BIMI1)
# l=https://.../logo.svg           -> Location of your SVG Tiny PS logo
# a=https://.../vmc.pem            -> Authority evidence (VMC/CMC certificate)
```

### BIMI Record Tags

| Tag | Meaning |
| --- | --- |
| v=BIMI1 | Version identifier, always BIMI1 |
| l= | HTTPS URL of the SVG Tiny PS logo file |
| a= | HTTPS URL of the VMC or CMC certificate (authority evidence) |

#### The Selector Matters

Most deployments use the `default` selector, so the record lives at `default._bimi.yourdomain.com`. The selector can be changed via the BIMI-Selector header if you need different logos for different mail streams, but the default covers the vast majority of use cases.

## BIMI Requirements

BIMI has three core requirements. Miss any one of them and your logo will not appear, so it is worth understanding each in detail.

### 1\. DMARC at Enforcement

Your domain must have a DMARC record published with a policy of `p=quarantine` or `p=reject`. A policy of `p=none` is monitoring only and does not qualify. Most providers also expect the policy to apply to all mail, so avoid lowering coverage with the `pct` tag. Because DMARC depends on aligned SPF and DKIM, this requirement quietly forces your whole authentication stack to be correct first.

### 2\. A VMC or CMC Certificate

A Verified Mark Certificate (VMC) proves you own the logo, typically by verifying a registered trademark with a certificate authority such as DigiCert or Entrust. A newer Common Mark Certificate (CMC) covers logos that are not trademarked but have been in prior use. Gmail and Apple Mail require one of these; the certificate URL goes in the `a=` tag of your BIMI record.

### 3\. An SVG Tiny PS Logo

The logo must be an SVG file in the restricted SVG Tiny Portable/Secure (SVG Tiny PS) profile. It needs a `<title>` element, a square `viewBox`, a solid background fill, and no scripts, external links, animation, or embedded raster images. Keep the file small (ideally under 32 KB) and host it over HTTPS.

#### p=none Will Not Work

The single most common reason a BIMI logo fails to appear is a DMARC policy of `p=none`. You must move to enforcement. Use the [DMARC checker](/tools/dmarc-checker) to confirm your policy is set to quarantine or reject before you invest in a certificate.

## How to Set Up BIMI

1

### Get DMARC to Enforcement

Confirm SPF and DKIM are aligned, monitor your DMARC reports, then move your policy from `p=none` to `p=quarantine` and eventually `p=reject`. This is the foundation everything else rests on.

2

### Create an SVG Tiny PS Logo

Start from a square version of your logo and convert it to the SVG Tiny PS profile. Add a title, a solid background, and remove any scripts or external references. Validate the file before publishing.

3

### Obtain a VMC or CMC Certificate

Purchase a certificate from an authorized issuer. Expect to provide proof of a registered trademark for a VMC, or evidence of prior use for a CMC. The issuer signs your logo and gives you a PEM file to host.

4

### Host the Logo and Certificate

Upload both the SVG file and the certificate PEM to a location on your own domain, served over HTTPS. Note the two URLs, because you will reference them in the DNS record.

5

### Publish the BIMI DNS Record

Add a TXT record at the `default._bimi` selector pointing to both URLs:

dns

```
default._bimi  IN TXT  "v=BIMI1; l=https://yourdomain.com/bimi/logo.svg; a=https://yourdomain.com/bimi/vmc.pem"
```

6

### Test and Wait

Use a BIMI inspection tool to confirm the record, logo, and certificate all validate. Then send test mail to a supporting provider. Display can take time to appear as providers cache and re-check records.

#### Authentication First, Logo Second

Bitelio walks you through SPF, DKIM, and DMARC setup for your sending domain and verifies each record. Getting those green is the prerequisite for BIMI, so once your domain authenticates cleanly you are ready to add the BIMI record and certificate.

## Benefits of BIMI

BIMI pays off in two ways: the direct effect of a visible logo, and the indirect effect of the authentication you had to fix to earn it.

### Stronger inbox presence

A consistent logo across every message reinforces your brand and makes your mail easier to find and trust at a glance.

### Better protection against impersonation

With DMARC at enforcement, spoofed messages are quarantined or rejected, and your verified logo cannot be copied onto fraudulent mail.

### Improved engagement metrics

Recognizable, trustworthy mail tends to be opened more and reported as spam less, both of which feed back into a healthier sender reputation.

### A cleaner authentication posture

The road to BIMI leaves you with aligned SPF, DKIM, and enforced DMARC, which is the single best thing you can do for long-term deliverability.

## Current Limitations and Mailbox Support

BIMI is worth adopting, but it is still maturing. Set expectations accordingly before you commit budget.

### Uneven Provider Support

Gmail, Apple Mail, Yahoo, AOL, Fastmail, and La Poste display BIMI logos today, with Gmail and Apple requiring a VMC or CMC. Microsoft Outlook has announced support and has been rolling it out gradually. Because behavior varies, treat BIMI as a progressive enhancement rather than a guaranteed, universal feature.

### Certificate Cost and Trademark Barrier

A VMC generally requires a registered trademark and an annual fee that can run from a few hundred to over a thousand US dollars. The CMC lowers the trademark barrier but is newer and less widely supported. For small brands without a trademark, the cost and paperwork can be a real hurdle.

### Strict Logo Rules

The SVG Tiny PS profile is unforgiving. Logos with fine detail, transparency, or non-square proportions often need to be redrawn. What renders crisply as a small circular avatar is not always the same as your full brand mark.

### No Direct Deliverability Boost

Publishing a BIMI record is not a ranking signal. The gains come from the authentication work and the trust the logo conveys, not from the tag itself. Do not expect BIMI to rescue mail that is landing in spam for other reasons.

#### Start With the Foundation

If you are not ready to buy a certificate, still get DMARC to enforcement now. You will capture most of the deliverability and anti-spoofing benefit immediately, and adding the BIMI logo later becomes a quick final step.

## Related Email Authentication Guides

- [What is DMARC?](/guides/what-is-dmarc): The enforcement policy BIMI depends on, explained end to end.

- [Email Authentication Guide](/guides/email-authentication): How SPF, DKIM, and DMARC fit together to secure your domain.

- [DMARC Checker](/tools/dmarc-checker): Verify your DMARC policy is at enforcement and ready for BIMI.

---

> Source: https://dev.bitelio.com/guides/what-is-bimi

---

# https://dev.bitelio.com/guides/what-is-dkim

# What is DKIM? DomainKeys Identified Mail Explained

Understand what DKIM is, how DKIM signatures and keys work, and the steps to configure it—so your domain stays safe from spoofing and your mail reaches the inbox.

DKIM (DomainKeys Identified Mail) is an authentication standard that gives receiving mail servers a way to confirm two things about a message: that the domain in the sender address truly sent it, and that nothing in the message changed between sending and delivery.

A useful way to picture DKIM is as a tamper-evident seal—much like the wax stamp on an old letter, it proves who the message came from and reveals if anyone opened or altered it en route.

## How DKIM Works

Under the hood, DKIM relies on public-key cryptography. The lifecycle of a signed message looks like this:

### 1\. The Sending Server Signs the Email

As your message leaves the server, a DKIM signature is generated and attached to its headers. Only your server can produce this signature, because only it holds the private key.

### 2\. The Signature is Added to Headers

That signature—stored in a header field named "DKIM-Signature"—contains a hash covering selected parts of the message, such as the sender, subject line, and body.

### 3\. The Receiving Server Verifies

On delivery, the recipient's server fetches your domain's public DKIM key from DNS and checks the signature against it. A successful match means the message passes DKIM.

### 4\. Delivery Decision

A passing signature strengthens your reputation and helps the message reach the inbox. A missing or failing one invites suspicion—and often a detour into the spam folder.

#### Technical Detail

The system is built on asymmetric cryptography: a private/public key pair. The private key never leaves your mail server, while the public key sits openly in DNS so any receiver can perform verification.

## What Does a DKIM Record Look Like?

The DNS side of DKIM is a TXT record holding your public key. A sample record:

Example DKIM DNS Record

```
default._domainkey.yourdomain.com  IN  TXT  "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC3QEKyU1fSma0axspqYK5iAj+54lsAg4qRRCnpKK68hawSJfliq9vKD6czJ..."

# Breaking down the components:
# v=DKIM1          -> DKIM version
# k=rsa            -> Key type (RSA encryption)
# p=MIGfMA0...     -> Public key (base64 encoded)
```

#### Selector Names

That "default" prefix in `default._domainkey` is known as a selector. Multiple selectors let you rotate keys safely or keep distinct mail streams (say, transactional versus marketing) on separate keys.

## Why DKIM Matters for Email Deliverability

### Prevents Email Spoofing

Without access to your private key, a spammer simply cannot produce a valid signature—so forging mail that authenticates as your domain becomes practically infeasible.

### Improves Deliverability

Gmail, Outlook, Yahoo, and other major providers treat a valid DKIM signature as a positive trust signal—and reward it with better inbox placement.

### Protects Brand Reputation

Every phishing email that impersonates you chips away at customer trust. DKIM closes off domain spoofing, keeping your brand out of attackers' hands.

### Enables DMARC

You can't run DMARC—the protocol that layers enforcement policies and reporting on top of authentication—without DKIM (or SPF) in place first.

#### Gmail & Yahoo Requirements

Since February 2024, any sender pushing 5,000+ messages a day to Gmail or Yahoo must authenticate with DKIM. Below that threshold it isn't mandatory—but it remains a clear best practice for everyone.

## What Does a DKIM Signature Look Like?

Every signed message carries the signature in its headers. Here's a real-world example of that header field:

DKIM-Signature Header Example

```
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
  d=yourdomain.com; s=default;
  h=from:subject:date:message-id:to;
  bh=frcCV1k9oG9oKj3dpUqdJg1PxRT2RSN/XKdLCPjaYaY=;
  b=GJwP3Qr8KqKKKNT5HL8j3fjXvLEm9KmZs6YdO2KqEqr...

# Key components:
# v=1                -> DKIM version
# d=yourdomain.com   -> Signing domain
# s=default          -> Selector (matches DNS record)
# h=from:subject...  -> Headers included in signature
# bh=frcCV1...       -> Hash of email body
# b=GJwP3Q...        -> The actual signature
```

## How Bitelio Simplifies DKIM

Doing DKIM by hand takes real effort—key generation, DNS wrangling, server configuration. Bitelio collapses all of it into a few clicks:

1

### Automatic Key Generation

The moment you add a domain to your account, Bitelio creates a secure DKIM key pair for it—no manual key management required.

2

### Simple DNS Setup

You get the precise DNS entries to publish, ready to copy straight into your DNS provider's dashboard.

3

### Automatic Signing

From then on, each message sent through Bitelio carries a valid DKIM signature—with zero extra configuration on your side.

4

### Verification & Monitoring

Bitelio confirms your records resolve correctly and keeps watching the authentication status of your outgoing mail over time.

#### Ready in Minutes

The typical Bitelio user finishes their DKIM setup in about 5-10 minutes, with the dashboard walking them through each step along the way.

## DKIM Best Practices

### ✓ Use 2048-bit Keys

1024-bit keys remain functional, but Gmail and other providers now recommend 2048-bit keys for their stronger cryptographic protection.

### ✓ Implement SPF and DMARC Too

On its own, DKIM covers only part of the picture. Pair it with SPF and cap the stack with DMARC to get full authentication coverage.

### ✓ Monitor DKIM Status

Make a habit of confirming your signatures still pass. Authentication reports, available on most sending platforms, make this straightforward.

### ✓ Rotate Keys Periodically

Swapping in fresh keys every 6-12 months limits your exposure if a key is ever compromised. Schedule rotations deliberately so delivery never skips a beat.

### ✗ Don't Share Private Keys

Handle the private key with the same care as a root password—never share it, and never store it anywhere insecure.

### ✗ Don't Use the Same Key Across Domains

Give every domain its own dedicated key pair. Reusing keys weakens security and muddies authentication across domains.

## DKIM vs SPF: What's the Difference?

Both protocols authenticate email, yet their mechanisms—and the questions they answer—are quite different:

| Feature | DKIM | SPF |
| --- | --- | --- |
| What it validates | Integrity of the message content | Whether the sending server is authorized |
| How it works | Cryptographic signature carried in headers | Delivering IP compared to a DNS allowlist |
| Survives forwarding | Yes (as long as content is untouched) | No (the forwarding IP won't match) |
| DNS record type | TXT at selector.\_domainkey.\* | TXT at the root domain |
| Required for DMARC | Yes (at least one of SPF/DKIM) | Yes (at least one of SPF/DKIM) |

#### Use Both for Maximum Protection

The two protocols cover each other's blind spots: SPF catches what DKIM can't (such as forged sending IPs), while DKIM keeps working through forwarding, where SPF falls apart. Run both, add DMARC on top, and your authentication story is complete.

## How to Test Your DKIM Setup

Once DKIM is configured, confirm everything works using one of these approaches:

### 1\. Check the Email Headers

Fire off a test message and inspect its raw headers. You're looking for the `DKIM-Signature` field plus the `Authentication-Results` field, which reports the pass/fail outcome:

Example Authentication-Results Header

```
Authentication-Results: mx.google.com;
  dkim=pass header.i=@yourdomain.com header.s=default header.b=GJwP3Qr8;
  spf=pass (google.com: domain of you@yourdomain.com designates 1.2.3.4 as permitted sender);
  dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=yourdomain.com
```

### 2\. Use DNS Lookup Tools

Query the DKIM TXT record directly to make sure your public key is live in DNS:

DNS Lookup Command

```
# Check your DKIM record via DNS
dig TXT default._domainkey.yourdomain.com

# Or using nslookup
nslookup -type=TXT default._domainkey.yourdomain.com
```

### 3\. Send to Gmail and Check

Deliver a test message to any Gmail inbox, open the three-dot menu, and choose "Show original". The summary panel at the top displays DKIM: PASS or DKIM: FAIL—instant confirmation of your setup.

#### Common DKIM Issues

When DKIM won't pass, verify that: (1) The selector in DNS matches the one your service signs with, (2) Your DNS provider hasn't truncated the record (very long keys sometimes need splitting), (3) Propagation has finished—allow up to 48 hours, and (4) The private key your service signs with corresponds to the published public key.

## Related Email Authentication Guides

- [What is SPF?](/guides/what-is-spf): How SPF records work alongside DKIM to verify senders.

- [What is DMARC?](/guides/what-is-dmarc): Everything about DMARC policies and domain protection.

- [Email Deliverability Guide](/guides/email-deliverability): Practical strategies for consistently reaching the inbox.

---

> Source: https://dev.bitelio.com/guides/what-is-dkim

---

# https://dev.bitelio.com/guides/what-is-dmarc

# What is DMARC? A Guide to Policies, Records & Reports

Discover what DMARC is, how it combines SPF and DKIM to shield your domain, what the none/quarantine/reject policies do, and how to publish a DMARC record and interpret its reports.

DMARC—short for Domain-based Message Authentication, Reporting, and Conformance—is the email authentication standard that sits above SPF and DKIM, shielding your domain from spoofed messages and phishing attacks.

SPF and DKIM perform the actual verification; DMARC's role is different. It defines what should happen to messages that fail those checks, and it delivers ongoing reports so you can see exactly how your domain is being used.

## How DMARC Works

Think of DMARC as the enforcement and visibility layer built on SPF and DKIM. The flow looks like this:

### 1\. Email Authentication

On arrival, the receiving server evaluates the message against SPF and DKIM. DMARC can only pass if at least one of those two checks succeeds.

### 2\. Alignment Check

Next comes "identifier alignment": the server verifies that the domain shown in the visible "From" header matches the domain that actually passed SPF or DKIM.

### 3\. Policy Application

When both authentication and alignment succeed, the message goes through normally. When they don't, the receiver applies whatever policy you published: none (observe only), quarantine (divert to spam), or reject (refuse delivery).

### 4\. Reporting

Participating mailbox providers email you daily summaries covering every message that claimed your domain as its sender, along with how each one fared in authentication.

#### DMARC Requires SPF or DKIM

DMARC has no authentication mechanism of its own—it depends entirely on SPF and/or DKIM being in place. Its contribution is the policy enforcement and reporting built on top of them.

## DMARC Record Syntax

You publish DMARC as a TXT record at `_dmarc.yourdomain.com`. A typical record looks like this:

Example DMARC Record

```
_dmarc.yourdomain.com  IN  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; ruf=mailto:forensic@yourdomain.com; pct=100; adkim=r; aspf=r"

# Breaking down the components:
# v=DMARC1                           -> DMARC version
# p=quarantine                       -> Policy (none, quarantine, or reject)
# rua=mailto:dmarc@yourdomain.com   -> Aggregate report email
# ruf=mailto:forensic@yourdomain.com -> Forensic report email
# pct=100                            -> Percentage of mail to apply policy (100%)
# adkim=r                            -> DKIM alignment mode (r=relaxed, s=strict)
# aspf=r                             -> SPF alignment mode (r=relaxed, s=strict)
```

### DMARC Policy Tags

| Tag | Description | Required |
| --- | --- | --- |
| v | Protocol version (always DMARC1) | Yes |
| p | Enforcement policy: none, quarantine, or reject | Yes |
| rua | Where aggregate reports are delivered | Recommended |
| ruf | Where forensic reports are delivered | Optional |
| pct | Share of mail the policy applies to (0-100) | Optional |
| sp | Separate policy for subdomains | Optional |
| adkim | DKIM alignment mode: r (relaxed) or s (strict) | Optional |
| aspf | SPF alignment mode: r (relaxed) or s (strict) | Optional |

## Understanding DMARC Policies

There are three policy levels, and the safest approach is to move through them in order:

1

### p=none (Monitor Mode)

Failing messages are delivered as usual—nothing is blocked. This mode exists purely to collect reporting data, making it the right starting point while you audit your authentication.

```
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
```

**Best for:** First deployments, data collection, validating your configuration

2

### p=quarantine (Quarantine Failed Mail)

Messages that fail authentication get diverted into recipients' spam or junk folders. It's a sensible intermediate step—your domain gains real protection with limited risk to legitimate delivery.

```
v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; pct=100
```

**Best for:** Once monitoring shows your legitimate mail authenticates reliably

3

### p=reject (Block Failed Mail)

Failing messages are refused at the door and never delivered. Nothing protects your domain more thoroughly—but it demands a flawless authentication setup across every mail stream.

```
v=DMARC1; p=reject; rua=mailto:dmarc@yourdomain.com; pct=100
```

**Best for:** Well-established setups where every sender authenticates correctly

#### Progressive Implementation

Begin every rollout at `p=none` and observe for a minimum of 2-4 weeks. Work through the reports, resolve any authentication gaps, and only then step up to `p=quarantine` and eventually `p=reject`.

## How to Set Up DMARC

1

### Ensure SPF and DKIM are Working

Since DMARC depends on SPF or DKIM (ideally both), confirm those records are published and passing before you go any further.

2

### Create a Mailbox for Reports

Stand up a dedicated address such as dmarc@yourdomain.com to collect the reports—they arrive daily and can pile up quickly, so keep them out of your personal inbox.

3

### Create Your DMARC Record

Begin in observation mode:

dns

```
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com; pct=100
```

4

### Add to DNS

Publish it as a TXT record under `_dmarc.yourdomain.com`

5

### Monitor Reports

Spend 2-4 weeks reading the incoming reports. Hunt for authentication failures and flag any genuine sending sources that still need their SPF or DKIM set up.

6

### Gradually Increase Policy

When the data looks clean, switch to `p=quarantine`, watch the reports again, and finish with `p=reject` if you want maximum protection.

## Related Email Authentication Guides

- [What is DKIM?](/guides/what-is-dkim): How cryptographic signatures verify your email content.

- [What is SPF?](/guides/what-is-spf): How SPF records declare your authorized mail servers.

- [Email Deliverability Guide](/guides/email-deliverability): Everything you need to reliably reach the inbox.

---

> Source: https://dev.bitelio.com/guides/what-is-dmarc

---

# https://dev.bitelio.com/guides/what-is-spf

# What is SPF? A Complete Guide to Sender Policy Framework

Understand what SPF is, how SPF records stop email spoofing, and how to set one up correctly—with syntax examples, common pitfalls, and best practices.

SPF, short for Sender Policy Framework, is an email authentication standard that lets you declare—right in your DNS—exactly which mail servers have permission to send messages using your domain.

A helpful analogy: SPF acts like a bouncer's list at the door. Receiving servers consult it and admit only mail that originates from the servers you've explicitly approved.

## How SPF Works

The mechanism is simple: your DNS advertises the servers allowed to send for you, and receivers verify against it. Step by step, it looks like this:

### 1\. You Publish an SPF Record

A TXT record goes into your domain's DNS containing every IP address and third-party service that is permitted to send mail on your behalf.

### 2\. An Email is Sent

A message arrives at a mailbox provider claiming your domain as its sender. The receiving server records which IP address actually delivered it.

### 3\. The Receiving Server Checks SPF

The receiver queries DNS for your domain's SPF record and compares the delivering IP against the list of approved senders you published.

### 4\. Pass or Fail

A match means the check passes. No match means SPF fails—and depending on the policy you've chosen, the message may be marked as spam or refused entirely.

#### SPF Validates the Server, Not the Content

SPF answers only one question: was this server allowed to send? It says nothing about whether the message was tampered with—that's DKIM's job. Deploying both protocols side by side gives you far stronger protection than either alone.

## SPF Record Syntax

Every SPF record is simply a TXT record that follows a defined structure. A representative example:

Example SPF Record

```
v=spf1 include:_spf.google.com include:sendgrid.net ip4:192.0.2.1 ~all

# Breaking down the components:
# v=spf1                    -> SPF version (always v=spf1)
# include:_spf.google.com   -> Include Google's SPF record
# include:sendgrid.net      -> Include SendGrid's SPF record
# ip4:192.0.2.1            -> Authorize specific IPv4 address
# ~all                     -> Soft fail for all others
```

### Common SPF Mechanisms

| Mechanism | Description |
| --- | --- |
| ip4:192.0.2.1 | Approves a single IPv4 address |
| ip6:2001:db8::1 | Approves a single IPv6 address |
| include:domain.com | Pulls in the SPF record of another domain |
| a | Approves the IP behind the domain's A record |
| mx | Approves the IPs behind the domain's MX records |
| ~all | Soft fail (flag unlisted senders as suspect) |
| \-all | Hard fail (refuse all unlisted senders) |

#### 10 DNS Lookup Limit

The SPF specification caps evaluation at 10 DNS lookups, and every `include:` consumes one. Go past that ceiling and validation fails outright—so keep the record lean and prune includes you no longer need.

## Why SPF Matters

### Prevents Email Spoofing

With SPF in place, forging mail under your domain becomes far more difficult—messages from servers you haven't approved simply won't authenticate.

### Improves Deliverability

Mailbox providers extend more trust to domains that publish a valid SPF record, and that trust translates into more of your mail landing in the inbox.

### Protects Your Domain

Declaring your legitimate senders shields your domain name from being hijacked for phishing schemes and bulk spam operations.

### Required for DMARC

DMARC—the layer that adds enforcement policies and reporting on top of authentication—can't function without SPF or DKIM underneath it.

## How to Set Up SPF

1

### Identify All Email Senders

Take inventory of everything that sends mail as your domain—your inbox provider, marketing platform, helpdesk software, billing system, and any other tools.

2

### Gather SPF Include Values

Every provider documents its own include value. A few common ones:

```
Google Workspace:     include:_spf.google.com
Microsoft 365:        include:spf.protection.outlook.com
Bitelio:                include:spf.bitelio.com
SendGrid:             include:sendgrid.net
```

3

### Create Your SPF Record

Merge every approved sender into a single record:

dns

```
v=spf1 include:_spf.google.com include:spf.bitelio.com ~all
```

4

### Add to DNS

Publish it as a TXT record through your DNS provider, using your root domain as the record name (typically "@" or "yourdomain.com").

5

### Verify SPF

Run the record through an SPF checker to confirm the syntax is valid and you're safely under the 10-lookup ceiling.

#### Bitelio Handles This Automatically

Add a domain in Bitelio and we generate the precise SPF record for you—paste it into your DNS and our verification checks confirm everything resolves correctly.

## Common SPF Mistakes to Avoid

### ✗ Multiple SPF Records

A domain gets exactly ONE SPF record—publishing two or more breaks validation. If you send through several services, fold every include into that single record.

### ✗ Exceeding 10 DNS Lookups

Remember that each `include:` spends one of your 10 permitted lookups. Stack up too many and SPF stops passing—trim and consolidate wherever you can.

### ✗ Forgetting to Update SPF

Onboarded a new sending tool? Add its include value right away. A stale record silently causes perfectly legitimate mail to fail authentication.

### ✗ Using +all

`+all` (pass everything) should never appear in your record—it authorizes the entire internet to send as your domain. Stick with `~all` or `-all`.

## Related Email Authentication Guides

- [What is DKIM?](/guides/what-is-dkim): See how DKIM signatures pair with SPF to authenticate your mail.

- [What is DMARC?](/guides/what-is-dmarc): Build a DMARC policy on top of your SPF and DKIM setup.

- [Email Deliverability Guide](/guides/email-deliverability): Everything you need to reliably reach the inbox.

---

> Source: https://dev.bitelio.com/guides/what-is-spf

---

> Glossary omitted from this corpus (grows continuously). See https://dev.bitelio.com/glossary and https://dev.bitelio.com/llms.txt for the current term list.