# Deliverability best practices

> What Pidgely does for your inbox placement, and the practices on your side that matter most - authentication, list hygiene, separate streams, complaints and warm-up.

Source: https://docs.pidgely.com/guides/deliverability/

Pidgely handles the infrastructure side of deliverability. The rest depends on what you send and to whom. This page lists both, with links to longer articles on the [Pidgely blog](https://pidgely.com/blog/).

## What Pidgely does for you

- **Authentication**: DKIM (RSA-2048) per domain and an SPF-aligned return path, so DMARC passes on both. See [Domains & DNS](https://docs.pidgely.com/guides/domains/).
- **Separate streams**: transactional and broadcast mail use separate IP pools. See [Transactional vs marketing streams](https://pidgely.com/blog/transactional-vs-marketing-streams/).
- **IP warm-up and pacing**: new IPs ramp up gradually, concurrency is capped per destination, and each account sends at its own pace. See [How to warm up a new sending IP](https://pidgely.com/blog/ip-warmup-guide/).
- **Bounce and complaint processing**: VERP return paths, DSN parsing and feedback loops feed the [suppression list](https://docs.pidgely.com/guides/suppressions/) automatically. See [VERP and automated bounce handling](https://pidgely.com/blog/verp-bounce-handling/) and [Feedback loops](https://pidgely.com/blog/feedback-loops-complaint-rate/).
- **One-click unsubscribe** (RFC 8058) on every broadcast. See [One-click unsubscribe](https://pidgely.com/blog/one-click-unsubscribe-rfc-8058/).
- **Reputation guard**: sending pauses automatically above 4% bounces or 0.1% complaints, before the damage spreads ([details](https://docs.pidgely.com/rate-limits/#reputation-guard)).

## Checklist for your side

1. **Publish DMARC** on your domain. Start with `p=none` and a reporting address, then tighten. Gmail and Yahoo require it for bulk senders: [the checklist](https://pidgely.com/blog/gmail-yahoo-bulk-sender-requirements/).
2. **Send only to people who asked.** Use double opt-in for newsletters; never buy lists.
3. **Keep complaints under 0.1%.** Make unsubscribing easy: include `{{{PIDGELY_UNSUBSCRIBE_URL}}}` visibly in every broadcast.
4. **Separate transactional and marketing mail.** Use broadcasts (or `"stream": "broadcast"`) for marketing; consider a subdomain such as `news.acme.com` for it.
5. **Use a consistent From address** with a real name and a monitored `reply_to`.
6. **Send both HTML and text** (Pidgely generates text from HTML if you don't), keep HTML light, and avoid link shorteners.
7. **Remove inactive recipients** from marketing segments after a few months of silence.
8. **Watch webhooks**: track `email.bounced`, `email.complained` and `email.delivery_delayed` per campaign.
9. **Ramp up new volume** gradually instead of sending your whole list on day one.

Going to spam already? Work through [Why your emails go to spam](https://pidgely.com/blog/why-emails-go-to-spam/). Wondering about dedicated IPs? See [Shared vs dedicated IP](https://pidgely.com/blog/shared-vs-dedicated-ip/).