To format Feedback-ID for Gmail effectively, use up to four identifiers separated by colons in the format `Feedback-ID: A:B:C:D`, although not all identifiers are always available. Read these in reverse (D to A), with 'D' identifying the ESP/Platform, 'C' the Account, 'B' the Mail Stream/List, and 'A' the Specific Mailing, though A and B often return nothing. Ensure identifiers are relevant, unique, and consistently formatted to enable effective feedback loop analysis, pinpoint issues, and improve deliverability by tracking complaints. Prioritize user privacy by anonymizing or hashing identifiers, avoiding PII. While Feedback-ID aids in troubleshooting, it cannot overcome a bad sender reputation; a solid reputation is crucial for its effectiveness. Google bases identifier importance on the volume of complaint data.
11 marketer opinions
Feedback-ID for Gmail should be formatted using four variable slots (A:B:C:D), typically read in reverse order (D to A). 'D' identifies the sending platform/ESP, 'C' the account, 'B' the mail stream/list, and 'A' the specific mailing. However, 'A' and 'B' often return nothing. Correct formatting improves deliverability by tracking complaint data, pinpointing issues, and enabling corrective actions. Consistent formatting, meaningful identifiers (campaign ID, customer ID, mailing ID), and ensuring no reverse identification of complainers are key. Google bases identifier importance on the volume of complaint data. The IDs can be used to track complaints and the more unique they are the better to track individual responses.
Marketer view
Email marketer from Validity explains that Feedback-ID best practices include using a consistent format across all mailings and ensuring that the identifiers used are meaningful and trackable. They recommend using a combination of identifiers such as campaign ID, customer ID, and mailing ID to maximize the effectiveness of the Feedback-ID.
4 Aug 2021 - Validity
Marketer view
Email marketer from Email Geeks explains that Google seems to base this on the volume of data they have for each identifier in terms of the number of complaints.
13 Jan 2023 - Email Geeks
4 expert opinions
Experts recommend focusing on privacy and sender reputation when formatting Feedback-ID. Not all four identifiers are always available, and unique IDs might be stripped. Alternatives to the standard format exist. Data should be anonymized or hashed to protect user privacy. A solid sender reputation is crucial for Feedback-ID to be effective in troubleshooting delivery issues when Gmail's spam filter misclassifies messages.
Expert view
Expert from Word to the Wise (Laura Atkins) responds that Feedback-ID is a helpful diagnostic tool when the Gmail spam filter is misclassifying messages, but it can't overcome a bad sender reputation. Senders need to establish a solid reputation before Gmail starts actively using it. However, once this is done, feedback from Feedback-ID becomes really important for troubleshooting delivery issues.
25 Jun 2021 - Word to the Wise
Expert view
Expert from Email Geeks explains that they don't usually get all 4 identifiers, maybe 1 or 2 regularly and anything that looks like it could be a unique ID will be stripped.
9 Jan 2025 - Email Geeks
3 technical articles
Documentation emphasizes using up to four identifiers separated by colons in the Feedback-ID header (`Feedback-ID: a:b:c:d`). This provides a structured way to identify specific mailings, track complaints, and troubleshoot deliverability. Consistency and relevance of identifiers are crucial for effective feedback loop analysis. Unique identifiers related to mailing, campaign, or account are recommended.
Technical article
Documentation from SparkPost explains that when implementing Feedback-ID, it is crucial to maintain consistency in the order of identifiers and to ensure that each identifier is relevant and helps in the identification process. They recommend using identifiers that are unique to the mailing, campaign, or account to allow for effective feedback loop analysis.
21 May 2022 - SparkPost
Technical article
Documentation from RFC-8260 describes that the Feedback-ID header field is intended to provide a structured method for feedback loops to identify specific mailings and track complaints. It allows for the inclusion of several identifiers to pinpoint the origin of the email and assist in troubleshooting deliverability issues.
13 Feb 2024 - RFC-8260
Are abuse reports and feedback loops (FBLs) still useful in email marketing, and how do they work with different email clients?
Do ISPs provide 'not spam' feedback data, and how can ESPs use it?
Do spam complaints from different email domains have different weights in deliverability?
How can I accurately monitor complaint rates for email marketing using Google Postmaster Tools, Yahoo FBL, and my ESP?
How can I identify users generating spam complaints using Google Postmaster Tools?
How can I manage Feedback-ID headers when using Amazon SES to send emails, especially with Gmail's upcoming sender requirements?