Beehiiv newsletter deliverability: are your seeds hitting inbox?

Beehiiv is the fastest-growing newsletter platform of the last few years. It was built by ex-Morning Brew operators who understood that newsletter writers did not want to manage IPs, DKIM signing, or feedback loops. They wanted to hit publish. In exchange for that simplicity, every Beehiiv publisher shares a sending pool with thousands of other publishers — and that pool's reputation is what decides whether your Tuesday issue lands in the Gmail Inbox or in Promotions.

The uncomfortable truth is that pool reputation is not static. When a new wave of publishers joins and one of them runs a cold-ish campaign, complaint rates on the pool tick up. When a big publisher ramps volume, engagement metrics on the pool shift. You do not see any of this from your Beehiiv dashboard. You only see your own open rate — which is already downstream of Gmail's decision.

Seed addresses close that loop. You subscribe a handful of real mailboxes (Gmail, Outlook, Yahoo, Mail.ru, Yandex, ProtonMail) to your Beehiiv publication, send your issue as normal, and then check the folder each seed saw. That is ground-truth placement — not an open rate filtered through Gmail image-caching and clipped previews.

Why Beehiiv pool drift matters for your open rate

Every shared-IP platform has this problem. Mailchimp, ConvertKit, Substack and Beehiiv all route millions of daily emails through a small number of IP ranges. To the receiving side — Gmail, Outlook, Yahoo — those IPs have one aggregate reputation score. If any large publisher on the same IP posts a bad week, your reputation moves with theirs.

Beehiiv mitigates this with automated warming, reputation tiers, and per-publisher segmentation. It works most of the time. The times it does not work are exactly the times you need to know about, because those are the issues that quietly land in Promotions while your open rate drops six points and you have no idea why.

How to subscribe seed addresses to your Beehiiv publication

Beehiiv treats seeds exactly like real subscribers. There is no dedicated seed-list feature — and you do not need one. The flow is simple:

1. Generate a batch of seed addresses across major providers. Use our free tool, a GlockApps-style paid service, or a hand-rolled list of inboxes you own.
2. In Beehiiv, open Audience → Subscribers → Import. Paste the addresses or upload a CSV.
3. Tag them seed or segment them into a "Seeds" audience so you can exclude them from paid-subscription metrics later.
4. Confirm any double-opt-in emails. Beehiiv sends confirmation by default — make sure your seeds actually confirm, or they will not receive the issue.

After that, every send goes to your seeds automatically. You do not have to remember to include them, which matters because the issue you forget to test is the one that will land in spam.

Segmenting so seeds do not pollute your numbers

Seeds will open the email (or not), click links (or not), and that artificial engagement blends into your dashboard. Keep the damage bounded:

• Put seeds in a distinct segment; exclude that segment from subscriber counts in any exported reports.
• Do not include seeds in audience-facing totals shown to sponsors.
• If you run referral programs, exclude seeds from referral-eligible segments.

Reading the results: placement trend, not single-issue scores

A single seed test tells you where this issue landed. The real value is the trend across twenty issues. Track three numbers per provider:

• Inbox rate: percentage of seeds on that provider that landed in the primary Inbox (or Updates for Gmail, which is usually fine).
• Promotions rate: Gmail-specific. Promotions is survivable but costs open rate.
• Spam rate: any time this is non-zero on a given provider, something shifted.

beehiiv placement trend — my-newsletter.beehiiv.com (last 8 issues)
                 gmail   outlook  yahoo   mail.ru  proton
  issue 41       Inbox    Inbox   Inbox   Inbox    Inbox
  issue 42       Promo    Inbox   Inbox   Inbox    Inbox
  issue 43       Promo    Inbox   Inbox   Inbox    Inbox
  issue 44       Promo    Junk    Inbox   Inbox    Inbox   <- Outlook drift
  issue 45       Promo    Junk    Inbox   Inbox    Inbox
  issue 46       Inbox    Inbox   Inbox   Inbox    Inbox   <- pool recovered
  issue 47       Inbox    Inbox   Inbox   Inbox    Inbox
  issue 48       Inbox    Inbox   Inbox   Inbox    Inbox

That Outlook dip around issues 44–45 is classic pool drift. You did not change anything. Beehiiv did not tell you anything changed. But your Outlook subscribers saw two issues in Junk before things recovered. Without seeds you would never know.

Calibrating expectations for a Beehiiv account

Expect some steady-state Promotions placement in Gmail for newsletter content. That is normal — newsletters live in Promotions and opens still happen there. Do not treat Promotions as failure. Treat Spam as failure. Treat a sudden drop from Inbox to Promotions across multiple providers as pool drift worth noting.

Also expect provider-specific quirks. Mail.ru and Yandex are stricter on SPF alignment and on From-name patterns. ProtonMail rarely junks a Beehiiv send but will silently trim trackers. Outlook is the one most likely to flip to Junk on a pool-reputation swing — keep an eye on it.

Recommended seed-test cadence

For a weekly publisher: test every issue. It is one extra subscriber batch and the cost is zero. For a daily publisher: test one per week at minimum, plus any issue that materially changes your template or your subject-line style. For a less-than-weekly publisher: test every issue, because with low cadence a single spam placement costs you a full week of reader attention.

Frequently asked questions