Outbound Wiki

Article

How to enable one-click unsubscribe email with Amazon Pinpoint

aws.amazon.com

Open at publisher

Quoted on this wiki

Every place a page here uses this source, in the order the words come in it.

  1. Conclusion. Following this guidance, in conjunction with properly authenticating your email sending domains and monitoring / keeping spam complaints below prescribed thresholds will help ensure high rates of Pinpoint email deliverability. We welcome your comments on this post below. For additional information, refer to these resources, or contact your AWS account team.

    In Inbox placement and spam filters

  2. Fully authenticate their email sending domains with SPF, DKIM and DMARC. See this blog. Provide a clearly visible unsubscribe link in the body &/or footer of each message. Enable the “List-Unsubscribe” and “List-Unsubscribe-Post” one-click unsubscribe (the subject of this blog post). You can learn more about these headers and how they are used in SES in this related blog post.

    In Opt-out handling

  3. Pinpoint now supports the inclusion of the “List-Unsubscribe” and “List-Unsubscribe-Post” email headers that enable compatible email client apps to render a one-click unsubscribe button when displaying emails from a subscription list. When you include these headers in the emails you send by Pinpoint, those end-users who want to unsubscribe from your emails can do so by simply clicking the unsubscribe button in their email app (see image). Once pressed, the unsubscribe button fires off a POST request to the URL you have defined in the “List-Unsubscribe” header. Your system or process must, when activated by the unsubscribe action, update that end-user’s preferences accordingly so that within 48 hours, any end-user who unsubscribes will no longer receive unwanted emails. If you only use Pinpoint’s campaigns and journeys, you may elect to use the Pinpoint endpoint’s OptOut attribute to store the user’s unsubscribe preferences. Possible values for OptOut are: ALL, the user has opted out and doesn’t want to receive any messages; and, NONE, the user hasn’t opted out and wants to receive all messages. It is important to note, however, that the SendMessages API ignores the Pinpoint endpoint’s OptOut attribute.

    In Opt-out processing workflows