惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

D
DataBreaches.Net
IT之家
IT之家
博客园_首页
博客园 - 【当耐特】
V
V2EX
Apple Machine Learning Research
Apple Machine Learning Research
G
Google Developers Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Recent Announcements
Recent Announcements
F
Fortinet All Blogs
GbyAI
GbyAI
腾讯CDC
H
Hackread – Cybersecurity News, Data Breaches, AI and More
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
I
InfoQ
H
Help Net Security
T
Tailwind CSS Blog
B
Blog RSS Feed
Martin Fowler
Martin Fowler
人人都是产品经理
人人都是产品经理
The Cloudflare Blog
博客园 - 叶小钗
雷峰网
雷峰网
量子位

Buttondown's blog

Email could have been X.400 times better The physicists who convinced Fermilab to send Brazil's emails Better in-app previews Analytics 3.0 Subscriber ID variables Comments! Send latest premium action Automation filtering Free API subscribers Surveys in automations Reply to replies Labels for RSS feeds How Jeremy Singer-Vine curates curious datasets for readers 2023 (and what's next) Email vs web content Sort by engagement Better gift subscriptions How Andy Dehnart built a career reviewing television New email template Email-based automations Opt-in reply tracking Automatic alt text More social network integrations Sort by metadata Overlarge image warnings Automation tag actions Pause emails mid-flight Search tags and automations Gift via automations Subscriber-driving emails
Filter subscribers by bounce date and reason
Justin Duke · 2026-04-28 · via Buttondown's blog

When your emails get "bounced" — meaning that your subscriber's inbox politely says to try again later, due to low storage or rate limiting — we've tracked and surfaced that for a while in the various email analytics views. Now, that data is surfaced on the subscribers page too: you can filter and view your subscribers by bounce_date and bounce_reason directly, both as filter options and as table columns.

"What's the difference between bouncing and undeliverability?", you ask. Oh, my sweet summer child.

Buttondown only marks a subscriber as undeliverable after we've seen enough deliverability problems to be confident the address is dead. A single bounce isn't enough — sometimes inboxes are full, sometimes a server is misbehaving, and the subscriber's perfectly fine the next day. Tracking bounces separately means you can see those soft signals long before we make the call to stop sending.

A couple of ways this comes in handy:

  • Catch trouble early. Filter for subscribers who bounced in the last week to see who's wobbling. If the same address keeps showing up there, you can decide to remove them yourself rather than waiting on us.
  • Combine with engagement filters. Layer the bounce filter on top of open and click rate filters to find the subscribers who are technically reachable but not really engaging — the kind of audit that's worth running once or twice a year.
  • Resend or tag problematic cohorts. Want to resend yesterday's time-sensitive missive to folks who didn't get it? We won't do that for you — for obvious reasons — but you can, now more easily than ever!

Both filters live in the existing filter menu on the subscribers page, and you can flip them on as columns via the table customization menu. Reach out if anything's confusing.