One Click Unsubscribe for non google or yahoo domains

[RebeccaWozniak]

We recently implemented a One Click Unsubscribe web app and email header to comply with the June 1 deadline for google/yahoo.  After the first few days we have received several one click unsubscribe records in our process from google/yahoo but also from domains outside of google/yahoo. Ranging from aol.com, b2b email domains and others.  

Are others experiencing similar results at this time? Or are you modifying approach to only include header for specific email domains?

Is there a way to determine what companies are choosing to also implement similar one click requirements?  It seems that this method could easily start being adopted by email domains moving forward to provide easy unsubscribe functions to their clients.

One particular domain seems to be displaying the one click for the email recipient because we are receiving records but also sending an "unreachable" email bounce response back.  

Has anyone found references to how we will know if our header/web app is compliant with google/yahoo or other non google/yahoo email domains?

Any assistance is greatly appreciated.  Thank you

[DavidKangni]

Anti-spam applications may perform GET requests on links within emails.

To Prevent unintended unsubscriptions, add an additional step so that the GET request to that link does not unsubscribe someone. As an example, you could make the GET request to the link present a landing page to the user containing a link or button to confirm the unsubscribe.

David

[ALangridge]

Hey David - doesn't this sort of defeat the purpose of the one click unsubscribe when you add in more clicks? 

If there is a certain level of attrition due to these security checks, it may need to be simply accepted as the cost of doing business to maintain the ability to contact gmail or yahoo users. 

[_Manoj_Kumar_]

Hello @RebeccaWozniak 

Google and Yahoo are enforcing these rules but some other clients also supports this functionality so this is expected.

One thing that I would also look at is the way one click unsubscribe is handled. Are you using GET method or POST method?

Like @DavidKangni  mentioned, a lot of ISPs uses spam filtering technologies and these technologies also try to clicks on the links to block suspicious email with phishing links.

The chances of an accidental unsubscribes by these spam filtering technologies are high when you are using GET method for Unsubscribe URL.

I hope this is helpful.

[RebeccaWozniak]

We are using the POST method. In our experience when the email is received and the header is populated there is engagement with the link, then the recipient has to CONFIRM they want to stop receiving emails from that sender so the bot clicks wouldn't get to that 2nd confirmation.

[DavidKangni]

Hi @RebeccaWozniak 
you should keep the header unsub as a POST call.

GET approach is just an additional layer to avoid false unsub.

GET requests are intended to retrieve data from a server and do not modify the server’s state. On the other hand, POST requests are used to send data to the server for processing and may modify the server’s state.

Spam filtering technologies are using a GET to just make sure the URLs exist vs when the recipients click which are POST.

Hope it helps.

Thanks,

David