{"id":14217,"date":"2020-11-13T07:03:34","date_gmt":"2020-11-13T07:03:34","guid":{"rendered":"https:\/\/www.gmass.co\/blog\/?p=14217"},"modified":"2020-11-19T08:27:32","modified_gmt":"2020-11-19T08:27:32","slug":"gmail-vs-api-deliverability","status":"publish","type":"post","link":"https:\/\/www.gmass.co\/blog\/gmail-vs-api-deliverability\/","title":{"rendered":"Does sending from Gmail directly vs using the Gmail API affect deliverability?"},"content":{"rendered":"

Recently, two email industry colleagues independently reported something odd to me. Each composed an email in Gmail, sent it, and it landed in the recipient’s Inbox. Each then sent the exact same email using the Gmail API, only to find that the email was going to the recipient’s Spam folder. They swore up and down that everything from the Subject to the individual MIME parts were equivalent in both scenarios. How then, would sending directly from Gmail cause one deliverability outcome while sending from the Gmail API cause another?<\/p>\n

First, let me explain what the Gmail API is. It’s a programmatic way of sending an email via your Gmail account. My tool, GMass, and any of our competitors like Mailshake, Lemlist, SalesHandy, Woodpecker.io, and others, all send email via the Gmail API.<\/p>\n

Additionally, even we have had users report that sometimes, sending an email via GMass lands in the Spam folder, but sending it directly in Gmail (using Gmail’s normal blue “Send” button) results in Inbox placement.<\/p>\n

Could it be that Gmail treats emails sent via its API differently, or with a lower priority, than emails sent directly inside the Gmail interface?<\/p>\n

I’ll do a deep dive and compare the various attributes of emails sent by Gmail directly versus a third party app that sends via the Gmail API. We’ll examine:<\/p>\n