Skip to content
Pidgely Docs

Guides

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.

View as Markdown

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.

What Pidgely does for you

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.
  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. Wondering about dedicated IPs? See Shared vs dedicated IP.