Feedback-ID Header Guide

Why Add the Feedback-ID Header to Your Email Senders?

You’re sending transactional emails, and suddenly your inbox placement drops. A few spam complaints come in—but you can’t tell which campaign triggered them. Your sender reputation suffers, and you’re left guessing.

The Feedback-ID header isn’t flashy, but it’s one of the most overlooked tools for keeping your domain and IP reputation intact. It’s a standardized way to tag each email campaign so ISPs can link spam complaints directly to the right message, not just your domain or IP.

Without it, every complaint gets tied to the whole sender identity. With it, you can isolate the problem—say, a mislabeled promotional email or a flawed template—and fix just that one campaign. That’s why adding Feedback-ID to your SendGrid, Mailgun, and Amazon SES workflows isn’t optional—it’s essential for precision in reputation management.

Key takeaways

Feedback-ID links spam complaints directly to individual campaigns, enabling precise troubleshooting.
Without Feedback-ID, ISP feedback gets tied to your domain or IP, making it harder to identify root causes.
Implementing Feedback-ID helps protect sender reputation by isolating and resolving issues at the campaign level.

What Is the Feedback-ID Header and How Does It Work?

Feedback-ID is an email header defined in RFC 8098 that uniquely identifies a specific email campaign or message for spam feedback collection. When a recipient reports your email as spam, Internet Service Providers (ISPs) use this ID to link the complaint directly to the source send, so you can see exactly which email triggered the complaint—without penalizing unrelated campaigns.

How It Enables Precise Complaint Tracking

Without Feedback-ID, a spam complaint might only show up as a general sender-level report, making it hard to know which email—among dozens—was the problem. With Feedback-ID, each message is tagged uniquely, so you can track complaints down to a specific subject line, sender, segment, or content variation.

Let’s say you sent a promo to three customer groups: last month’s buyers, inactive users, and those who opened your last email. If the inactive group generates complaints, Feedback-ID will show you exactly that. You can then adjust messaging for them without affecting the reputation of your active user campaigns.

Why This Matters for Deliverability

Deliverability isn't just about avoiding spam filters—it's about maintaining sender reputation, which is influenced by complaint rates. If you don’t pinpoint the source of complaints, you might mistakenly overhaul successful campaigns or miss real problems. Feedback-ID gives you the data to act precisely.

Major ISPs like Gmail and Yahoo use Feedback-ID to feed their spam reporting systems. While they don’t publish specific thresholds, industry practice confirms that consistent spam complaints from a single source degrade sender health over time. Feedback-ID helps you detect and fix spikes earlier.

You can use it across platforms like SendGrid, Mailgun, and Amazon SES by adding it in your email headers during send. It’s a lightweight, standards-compliant way to gain visibility into user behavior that most senders overlook.

While Feedback-ID doesn’t prevent complaints, it makes responding to them effective. The more granular your feedback, the better you can protect your deliverability.

Verify your email list’s health before sending, so you’re not just chasing complaints—preventing them. Use MailTester’s bulk verification to clean high-risk addresses and reduce the chance of complaints from invalid or compromised inboxes.

Which Email Services Support Feedback-ID? (SendGrid, Mailgun, Amazon SES)

You can add the Feedback-ID header to outbound emails in SendGrid, Mailgun, and Amazon SES—each supports it via API or SMTP. SendGrid uses the X-Feedback-ID header in SMTP or via its API. Mailgun enables it through the 'feedback-id' parameter in the API or the X-Feedback-ID header in SMTP. Amazon SES supports Feedback-ID using the Feedback-ID header when sending through its API, but not through SMTP.

SendGrid and Feedback-ID

You can include Feedback-ID in SendGrid emails by adding the X-Feedback-ID header when sending via SMTP or using the API. This header must contain a unique identifier for the message, usually tied to your internal tracking system. The Feedback-ID is essential if you're sending transactional or bulk emails and want to collect feedback from receiving mail servers. According to RFC 6521, the Feedback-ID header is used to correlate feedback reports back to the originating message, which helps with deliverability monitoring and debugging. You can use MailTester’s bulk verification tool to ensure your email list is clean and avoid sender reputation issues that might trigger feedback loops.

Mailgun and Amazon SES

Mailgun supports Feedback-ID both in its API (using the feedback-id parameter) and via the X-Feedback-ID header in SMTP. This gives you flexibility when integrating with different systems. Amazon SES allows Feedback-ID only through the SES API—SMTP doesn’t support it. If you're using Amazon SES, you must add the Feedback-ID header in the API call, typically as part of the email metadata. The feedback is then used to identify which message triggered a complaint or feedback report from a mailbox provider. This is especially useful in regulated industries where you must track every complaint related to a specific email. For better control, consider using MailTester’s API to validate your recipient list before sending.

None of these services require Feedback-ID to send emails, but enabling it improves your ability to respond to feedback reports. It’s an industry-standard practice and helps maintain sender reputation over time. The header doesn’t affect delivery but provides critical data for long-term email strategy. Always test your implementation using inbox placement testing to confirm headers are being sent correctly.

Adding Feedback-ID in SendGrid: Step-by-Step

You can add a Feedback-ID header in SendGrid by including the X-Feedback-ID header in your email via the SendGrid API or SMTP. Set it to a unique campaign identifier like newsletter-q1-2026 and keep it consistent across all messages in the same campaign and A/B test variants. This allows you to track complaint rates at the campaign level and maintain reliable feedback loops with mailbox providers. The header must be included per message to be effective.

Why It Matters: The Feedback-ID Purpose

Without a Feedback-ID, complaint data from ISPs like Gmail or Yahoo cannot be tied back to specific campaigns. This makes it hard to track why a message was reported. The Feedback-ID enables senders to identify exactly which email triggered a complaint — a key step for improving deliverability and reducing spam complaints.

The Feedback-ID is part of the RFC 5965 standard, which defines how ISPs report unwanted messages to senders. While not every provider implements it fully, major email services including Gmail and Outlook do respect it when properly used. Using it consistently helps you understand sender reputation risk by campaign, not just by IP or domain.

Choose a unique, consistent identifier for your campaign, such as campaign-912345 or newsletter-q1-2026. This ID must stay the same for all variations and send attempts in the campaign.
Set the header via API or SMTP. In the API, include "headers" : {"X-Feedback-ID": "newsletter-q1-2026"}. In SMTP, add X-Feedback-ID: newsletter-q1-2026 in the header section.
Include the same ID across all A/B test variants if you want to measure performance as a unified campaign. If you’re testing different content, use separate IDs only if you need isolation.
Verify your header is sent correctly using a tool like MailTester’s inbox placement test. It checks for headers, content, and delivery signals — including proper Feedback-ID inclusion. See how your email appears in real inboxes: inbox placement test.
Monitor feedback reports through your ESP's dashboard or via the Feedback Loop (FBL) service. Use the ID to correlate complaints to specific campaigns and adjust your lists or content accordingly.

Best Practices for Accuracy & Compliance

Use short, descriptive, and predictable IDs. Avoid random strings. If you automate sending, ensure the API or integration script includes the header in every request. Misconfigured headers can cause complaint data to be misattributed or lost.

For larger lists, use the bulk verification feature to eliminate invalid addresses before sending, reducing the risk of complaints. You can also test sender reputation and inbox placement before sending with the inbox tester.

Adding Feedback-ID in Mailgun: API and SMTP Setup

You can add a Feedback-ID in Mailgun by including the feedback-id field in your API request or adding the X-Feedback-ID header when sending via SMTP. Use a descriptive, consistent value—avoid random strings or timestamps unless you need per-send tracking. Mailgun passes this data to complaint reporting services like feedback loops, helping you track user complaints and improve sender reputation.

API Setup with Feedback-ID

When sending via the Mailgun API, include the feedback-id parameter in the request body.
Set its value to a unique, meaningful identifier—like a campaign ID, transaction ID, or customer reference.
Mailgun automatically forwards this value to the complaint reporting service when a user marks your email as spam.
Using consistent Feedback-ID values makes it easier to correlate complaints with specific campaigns or user segments.

SMTP Setup with Feedback-ID

When sending via SMTP, include the header X-Feedback-ID: unique-id in your message headers.
Place this header within the email’s header section, just like any other custom header (before the body).
Ensure the ID is static or logically tied to the message context—avoid generating random IDs unless you’re tracking per-send feedback.
Mailgun forwards the value to feedback loop providers, enabling you to identify sources of user complaints.

Feedback-ID is part of the broader effort to maintain sender reputation. According to the RFC 6650, complaint feedback mechanisms help senders understand and respond to user behavior, which impacts deliverability. It’s not just about avoiding blocklists—it’s about knowing when users disengage so you can act.

The 4 steps described in “API Setup with Feedback-ID”, in order.

Let’s say you send a newsletter using a campaign ID like newsletter-q3-2024. If a user reports it as spam, the feedback loop will return that same ID. You now know exactly which send triggered the complaint and can assess content, timing, or segmentation.

For better compliance and inbox placement, make sure your Feedback-ID values are predictable and tied to real events. Avoid timestamps unless you’re doing real-time analysis—random IDs make it impossible to correlate complaints.

If you're testing your email’s delivery performance, use MailTester’s inbox placement tool to see how your messages land across providers, including how feedback loops may affect delivery.

Adding Feedback-ID in Amazon SES: Configuration Guide

You add the Feedback-ID header in Amazon SES by including it in the email headers object when sending via the AWS SDK or API, using a key like Feedback-ID: campaign-202603. This header is preserved in the delivered email and appears in spam feedback reports. When present, Amazon SES forwards complaint data to Feedback Loop subscribers, enabling you to track and act on user-reported spam. This helps maintain sender reputation and reduces inbox placement issues over time.

Step-by-step process

Identify the message you want to track. Assign a unique, meaningful identifier—like campaign-202603—to categorize feedback by campaign, send, or content type.
When constructing your email using the AWS SDK or SES API, include the Feedback-ID in the Headers object as a key-value pair. Example: { "Feedback-ID": "campaign-202603" }.
Ensure your message includes the full Feedback-ID header in the email's raw headers. SES preserves this header as part of the email’s envelope metadata.
Verify your sender domain is authenticated via SPF, DKIM, and DMARC. Without proper authentication, SES may reject the message or reduce delivery quality.
Monitor feedback loops through programs like the Feedback Loop (FBL) from major email providers. The Feedback-ID ensures complaints are attributed correctly and delivered to the right endpoint.

Why this matters for deliverability

Without Feedback-ID, complaint data from users is not actionable. You won’t know which message triggered a report, making it harder to adjust content or lists. Including Feedback-ID helps track engagement trends and prevents reputation damage from unmonitored spam signals.

The 5 steps described in “Step-by-step process”, in order.

As outlined in the RFC 6654 standard, feedback from end users is a critical signal for email service providers. Using Feedback-ID aligns your sending practices with industry standards for accountability and transparency.

While Feedback-ID improves complaint tracking, it doesn’t stop bounces or blocklists. To catch invalid or risky addresses before sending, consider verifying your list with tools like MailTester’s bulk verification or testing inbox placement via MailTester’s inbox tester. These checks reduce the risk of triggering complaints in the first place.

For automated workflows, integrate directly using the MailTester API or set up connections through MailTester integrations with SendGrid, Mailgun, or other platforms. This ensures only valid, well-behaved addresses are sent to SES. Your sending history remains clean, and your reputation stays strong.

Feedback-ID Best Practices: Avoiding Common Pitfalls

You must use consistent, unique Feedback-ID values per campaign—never reuse them—so you can isolate complaints and track engagement accurately. Sending a test ID in production or using vague, overlapping IDs undermines the entire feedback loop. Keep IDs short (8+ characters), descriptive, and tied directly to the campaign or audience segment. This makes triage faster and compliance reporting clearer. You're not just labeling emails; you're building a traceable audit trail.

What to Do: Actions That Actually Work

Use a consistent naming pattern like campaign-name-date-audience (e.g., newsletter-march-loyalty) so ID structure remains predictable across teams.
Never reuse a Feedback-ID across campaigns—even similar ones. A single ID tied to multiple senders creates data noise and invalidates complaint tracking.
Verify IDs match actual campaign contexts. Don’t send a test-newsletter-2024 ID to a live audience—this triggers false alerts and confuses inbox providers.
Keep IDs above 8 characters to reduce collision risk. Shorter IDs increase ambiguity, especially with high-volume senders.

Pitfalls That Damage Reputation

Common mistakes here aren’t just inefficiencies—they degrade sender reputation. According to RFC 7888, feedback loops are only useful when tied to specific content and sender identities. If your IDs don’t reflect real campaigns, abuse detection systems can misclassify complaints, leading to higher blocklist risk.

Using blank, generic, or auto-generated IDs (like id12345) prevents effective triage and makes compliance audits nearly impossible.
Overloading a single ID across different audiences or message types hides which segment is driving complaints. This erodes trust with mailbox providers.
Forgetting to update IDs when testing or iterating on content leads to inconsistent reporting—even on retry campaigns.

Think of Feedback-ID as a fingerprint for each email campaign. You wouldn’t use the same fingerprint for every transaction—so don’t reuse them. With tools like MailTester's bulk verification or real-time API, you can validate lists before sending, reducing the risk of sending emails with bad or inconsistent IDs.

When you send, every header matters. Feedback-ID is not a nice-to-have—it’s a compliance requirement for serious senders. Use it right, and it becomes a direct line to inbox health.

How Feedback-ID Improves Sender Reputation and Inbox Placement

Feedback-ID lets you track spam complaints at the campaign level, so you detect issues early—without dragging your domain or IP reputation down. When a complaint spikes, you identify the exact message, audience segment, or design flaw in minutes. ISPs reward this transparency, which boosts long-term inbox placement. Pair it with clean lists and proper authentication, and you reduce the risk of being flagged or blocked altogether.

Pinpointing Problems Without Wasting Reputation

Without Feedback-ID, a single bad campaign can trigger a broad ISP alert, even if 99% of your messages are well-received. With it, you isolate the offender immediately. Let’s say your "New Product Launch" email gets flagged. Feedback-ID links that complaint directly to that campaign, not your whole sender account. You can pause the campaign, fix the subject line or content, and resume—without affecting your sender reputation.

Spam complaints are one of the top signals ISPs use to judge sender trust. When you send Feedback-ID, you show ISPs you’re self-monitoring. Major providers like Gmail and Yahoo look at this as a sign of accountability. This isn’t just about avoiding fines—it impacts filtering decisions in real time.

How It Fits Into a Bigger Deliverability Strategy

Feedback-ID doesn’t work in isolation. It’s most effective when layered over a solid foundation: verified email lists, strong authentication (SPF, DKIM, DMARC), and consistent sending patterns. MailTester’s bulk verification helps you clean lists before sending—removing invalid or risky addresses that could trigger complaints.

Use the inbox placement tool to simulate what real inboxes see. If your Feedback-ID is set up correctly, you’ll know exactly when a test campaign lands in spam. Combine that with real-time API verification for new signups, and you’re building a closed-loop system: verify, send, monitor, act.

While Feedback-ID is supported by platforms like SendGrid, Mailgun, and Amazon SES, not all senders use it—and that’s where you gain an edge. The RFC 8098 defines Feedback-ID as a standard for complaint tracking. Its adoption is growing, especially among regulated industries. A lack of Feedback-ID may signal opacity, especially if you're sending at scale.

When you make every campaign traceable, you aren’t just reacting to issues—you’re preventing them. That transparency, proven across major inbox providers’ policies, strengthens your reputation over time. It’s a small setup with outsized impact on inbox placement.

Integrating Feedback-ID with List Hygiene Tools Like MailTester

You can’t trust Feedback-ID data until your list is clean. Invalid, catch-all, or disposable addresses inflate complaint rates and corrupt feedback signals. Before enabling Feedback-ID in SendGrid, Mailgun, or Amazon SES, run your list through a tool like MailTester to flag and remove problematic addresses. This ensures that only real inbox interactions feed your feedback loop, making the data actionable.

Start with list hygiene — the foundation of accurate Feedback-ID

Feedback-ID relies on real user behavior to signal spam complaints. If your list contains catch-all or disposable email addresses, those accounts may accept mail but never engage, leading to false complaints. A catch-all domain will accept any email, even if it’s not intended for that user — which means a single misaddressed message can trigger a complaint that's not the sender’s fault. That skews your feedback data and makes it harder to identify real deliverability issues.

MailTester’s bulk verification API identifies these risks before they impact your metrics. It checks for invalid domains, catch-all detection, disposable email providers, and role-based addresses that often don't open emails or report spam. This filtering cuts noise from your feedback loop. You’re left with only addresses that are likely to interact with your content — which means Feedback-ID data reflects actual user intent, not spam trap activity or system errors.

Real complaints, meaningful insight

When you send to a list that’s been cleaned with tools like MailTester, the complaints you receive through Feedback-ID are more likely to represent genuine disengagement. That data becomes a reliable signal for email health. You can now track patterns — for example, if one segment consistently triggers complaints — and adjust your content, frequency, or targeting accordingly.

Without cleanup, Feedback-ID may tell you there’s a problem, but you can’t tell if it’s with the list, the content, or a systemic flaw in how you’re sending. Clean data leads to accurate attribution, which drives better decisions. Industry-standard practices, like those outlined in RFC 8098 (which defines Feedback-ID), assume you’re sending to engaged recipients. That assumption only holds when your list is verified and maintained.

For a fully automated workflow, integrate MailTester’s API into your sender stack. Use the email verification API to validate new signups or purge stale addresses before every campaign. This keeps your list healthy and makes Feedback-ID data trustworthy over time. Learn more about how this fits into your infrastructure at MailTester integrations.

Understanding the Limits of Feedback-ID: What It Doesn’t Do

Feedback-ID doesn’t stop spam complaints or improve deliverability on its own. It only gives you a way to track when a user reports your message as spam. It doesn’t affect how fast emails arrive, whether they bounce, or if filters block them. It complements SPF, DKIM, and DMARC but doesn’t replace them. Think of it as a diagnostic tool, not a fix.

What Feedback-ID does not fix

It won’t prevent spam complaints — you still need clear opt-in practices and easy unsubscribe links.
No impact on delivery speed. Your message will arrive at the same speed whether Feedback-ID is present or not.
It does not reduce bounce rates. Bounces are caused by invalid emails, server issues, or blacklists — Feedback-ID doesn’t fix these.
It won’t help you bypass content filters. Email content still gets scanned by ISPs for spam triggers — Feedback-ID doesn’t alter that.
It doesn’t substitute for authentication protocols like SPF, DKIM, or DMARC. Without these, your email may not be accepted at all.

How Feedback-ID fits into your deliverability toolkit

The real value of Feedback-ID is visibility. When a user marks your email as spam, you can use the ID to trace the complaint back to the specific message and sender. This helps identify trends — is one campaign triggering more complaints? Is a poorly designed template causing issues?

Major ISPs like Gmail and Outlook use this data to refine how they evaluate sender reputation. While Feedback-ID isn’t required, its presence signals transparency, which builds trust over time. According to the RFC 6522 (which defines the Feedback-ID mechanism), its purpose is to "enable the reporting of feedback to the originator of a message," not to alter delivery behavior.

Use it with tools that help you analyze complaints: inbox placement testing can show where your emails land in real inboxes, while bulk email verification ensures your list quality is high to begin with. A clean list reduces complaints — and that’s where Feedback-ID gives you insight, not a silver bullet.

Let’s be clear: Feedback-ID is not a substitute for good sending practices. It’s a recordkeeping tool for complaints. But in combination with strong authentication, list hygiene, and responsive design, it adds meaningful context to the deliverability picture.

A Final Note on Testing and Monitoring Feedback-ID Effectiveness

Deploying Feedback-ID headers is only effective if you verify they’re preserved across delivery paths and used correctly in complaint reporting.

Send test emails with Feedback-ID headers enabled and check your ESP’s analytics dashboard for complaint data. Confirm the header appears in feedback reports from providers like AOL, Yahoo, and Outlook. This ensures your systems are correctly transmitting the identifier when users mark messages as spam.

Use MailTester’s inbox-placement testing tool to simulate delivery to major providers. It checks whether Feedback-ID headers survive transit and are properly reflected in reported spam feedback. Regularly review metrics—quarterly or after major campaign shifts—to ensure header usage aligns with your reporting workflows and audience engagement goals.

Sources

Adding a single follow-up email to a cold outreach sequence generates roughly 40–50% more replies than sending the initial email alone. — Instantly Cold Email Reply Rate Benchmarks (2026)
The platform-wide average cold email reply rate is 3.43%, while the top 25% of senders achieve 5.5%+ and the top 10% reach 10.7%+, based on billions of emails sent in 2025. — Instantly Cold Email Benchmark Report 2026 (via Satellyte) (2026)

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

What happens if I don’t add Feedback-ID to my emails?

You'll still receive spam complaints, but they’ll be tied to your domain or IP instead of a specific campaign. This makes troubleshooting harder and increases reputation risk.

Can Feedback-ID be reused across different campaigns?

No. Reusing Feedback-ID undermines the purpose of granular tracking. Each campaign should have a unique ID to ensure accurate attribution.

Is Feedback-ID required by email providers?

No, it is not mandatory. However, it's strongly recommended for senders with high-volume or complex email programs to improve compliance and reputation.

How is Feedback-ID different from Message-ID?

Message-ID is used to identify a message across systems. Feedback-ID specifically ties spam feedback to a campaign, enabling targeted response.

Does Feedback-ID increase email deliverability?

It doesn’t directly improve inbox placement, but it helps you maintain reputation by enabling faster, targeted fixes for issues.

Can I use Feedback-ID with transactional emails?

Yes. Use consistent Feedback-ID values for each type of transactional message (e.g., 'password-reset-2026') to track complaints accurately.

How long does it take for Feedback-ID data to appear in reports?

Feedback data is typically shared within 24 to 48 hours after a complaint is filed, depending on the ISP’s reporting schedule.

What should I name my Feedback-ID values?

Use clear, unique names like 'campaign-name-month-year' or 'email-segment-type'. Avoid random strings or timestamps unless needed for per-send tracking.

Can I detect Feedback-ID issues using MailTester?

Yes. MailTester’s inbox-placement testing checks whether headers like Feedback-ID are preserved in delivery, helping validate your setup.

Do different ESPs use Feedback-ID differently?

The header format is standardized, but implementation varies slightly. The core function remains consistent across SendGrid, Mailgun, and Amazon SES.

Is Feedback-ID supported in all mail servers?

It is supported by major ESPs and ISPs. Your infrastructure must preserve the header during sending; most modern systems do.

Can Feedback-ID help avoid being blacklisted?

Indirectly. By identifying and fixing campaign-specific issues quickly, you reduce the risk of reputation damage that leads to blacklisting.