List Unsubscribe Headers

As part of the new Yahoo/Google sender requirements, Drip has implemented List Unsubscribe Headers into all of our emails to make sure anything you send is fully compliant with all new rules and regulations. Google’s documentation lists June 1st, 2024 as the required rollout date, but this has been implemented well ahead of that deadline.

As of February 9th, 2024, all emails sent from Drip will include unsubscribe headers embedded into the email. The new unsubscribe header will populate in one of two areas in an email. What determines whether it is more prominent, or more hidden currently has not been disclosed by Google at this time.

Additionally, this does not change or impact how Drip’s normal unsubscribe link works at the bottom of all emails, nor the behavior of the subscription management page itself.

If your reputation is high enough with Google (or they view you as a familiar sender), the unsubscribe header will populate a new clickable Unsubscribe UI element within the inbox shown here:

Clicking Unsubscribe will present a pop-up asking if the recipient would like to unsubscribe. If they click yes, it will send a request to Drip that processes and unsubscribes the recipient from your commercial emails. The good news is that as this is more of a UI element and not a link built into the body of the email, it should avoid accidental unsubscribes from security suites and things of that nature!

If your domain doesn’t meet the undisclosed requirements by Google, then the unsubscribe header lives in the expanded letterhead area, which you can find by clicking on the small dropdown arrow next to the “to me” wording above (*).

This will provide a more detailed view of the sender's information including an unsubscribe section. This Unsubscribe element functions the same as the link shown above, only with one extra click in the UI.

Both unsubscribe header locations are compliant, and there is not currently a documented way to configure your sending to have one version instead of the other. As more information surfaces, we will update this document to reflect any official documentation that is published.