What is the difference between standard and aggregate FBLs?
Still have a question, spotted an error, or have a better explanation or a source we should cite?
You've registered for a feedback loop and now you're staring at two options: standard or aggregate. They both track spam complaints, but they do very different jobs.
Standard FBLs send you an individual notification every time a recipient hits the spam button. You get a report that identifies the specific message and, in most cases, the specific recipient. That means you can suppress them immediately and stop sending to someone who clearly doesn't want your emails. Yahoo Mail and Outlook (via Microsoft's JMRP and SNDS programs) both offer standard FBLs. Most ESPs like Twilio SendGrid have built-in automation to handle this suppression for you the moment a complaint comes in.
Aggregate FBLs bundle complaint data into periodic summaries. Instead of "recipient X complained about message Y," you get something like "your spam rate was 0.12% this week." You can spot trends, but you can't act on individual complaints because the recipients aren't identified. Gmail's Google Postmaster Tools is the most well-known example of this. You'll see your spam rate percentage, but Google won't tell you which Gmail users hit the spam button.
So which one actually matters for your day-to-day? If you're a volume sender, standard FBLs are where the real work happens. A complaint that goes unsuppressed means you keep mailing someone who's annoyed with you, and that chips away at your sender reputation fast. Aggregate data is more of a monitoring layer. It tells you if something is trending in the wrong direction, but it won't tell you who to remove from your list.
The honest take: you want both where you can get them. Use standard FBL data for immediate suppression and list hygiene. Use aggregate data to watch your complaint rate trends and catch problems before they become crises. If you're only getting aggregate data (which is the Gmail reality), pay close attention to the trend line. A rising rate means your list has a problem that standard FBL suppression alone can't fix.
If you're not sure whether your current ESP is processing standard FBL complaints automatically, that's worth checking. Some platforms handle it silently in the background. Others need you to connect the dots yourself.
Contributors
Who worked on this answer
Every name links to their profile. Every company links to their site. Real people, real accountability.