SendGrid Reviews

Portability to whatever programming language you are using. RESTful API that can be invoked really easy. We use SendGrid from .NET and JavaScript.
Don't have to think of HTMLs anymore.

Our UX Designers create the templates at SendGrid web, and they give us (development team) the GUID of the new template so we can use them in our applications.

If any modification is needed, we do not have to make a deploy. The UX Designers make the necessary modifications at SendGrid Web and it's done!
The excellent dashboard and information that SendGrid provides at their web of the emails that were sent is a very useful plus.

Basically, we have replaced our SMTP server with this solution. (We had three SMTP servers, for development, testing, and production environments).

In the past, every time that there was a bug reported from users telling that the notifications weren't triggered, it was because of an SMTP server or configuration problem (our team does not have any responsibilities on it, it's a matter of infrastructure team).

With SendGrid, we have found a perfect solution to that scenario, and we don't have to involve infrastructure team anymore.

• Development
• Design
• Marketing

For about two years now.

No. Never had a connection problem with SendGrid API or Web.

Not really a scalability issue, but some kind of limitations. We have encountered some problems in order to make some dynamic templates (for example, we needed a grid with dynamic columns, and we had to make some magic to get it done).

So, don't think that you could do anything with SendGrid on email matters. The templates limit you a lot sometimes!

Honestly, we have not had to contact technical support yet, so I don't really know.

Yes, but as I said, it was a bunch of things that were replaced by SendGrid. HTMLs, SMTP Server, and a lot of repeated code (MailHelpers) in some applications are doing exactly the same thing (send emails).

No setup needed. You don't have to install anything, just use a very well documented API. Also, with .NET framework, there is an official Nuget package that makes the use of SendGrid even easier.

But on the other hand, it could be very complex if you decide to move all the emails that your applications generate to SendGrid. You will have to make a lot of code changes.

We decided to start by using SendGrid only on new notifications. And if we had to alter an old email template, we take advantage of that and make it through SendGrid also.

I think that also the GUI for creating the templates is very simple. I only have used it a couple of times so not really a review on that function here.

Sorry, but I don't know how much it costs, or the licensing matter. I asked for it and it was approved and also paid for by the company.

Yes. MailChimp and others. But they were more designated for marketing emails. The majority of the emails that we send are for internal and external notifications only. And SendGrid satisfies the two worlds.

Go ahead! It is pretty simple to use.

It is not that it does much, but what it does, it does well.

Their REST API feature is the most amazing and easy API I have used. It's very secure and probably the best API.

I liked almost everything about Sendgrid, but I would prefer an easy plugin for Linux mail installation.

They has a service to use Sendgrid as linux/unix default email.
https://sendgrid.com/docs/Integrate/Mail_Servers/sendmail.html

It would nice if they had an installer.

2 years

SendGrid provides the best analytics a competent postmaster needs. This is not an easy challenge, but if you are really serious about a well-executed mail plan, then SendGrid should be your prime choice.

Other than that, its pricing is fair and you get quality support with the high volume plans.

Sendgrid has enabled us deeper visibility to our email performance that simply wasn't there with our previous ESP. with it, we could avoid making pitfalls and tune our practices, so deliverability, open and click rates rose significantly.

They are backlogged on feature requests, which is a bit of a shame really. There are easy fixes here and there that can make workflows smoother.

White-listed mail which avoids spam on mail services like Gmail and Yahoo.

It gives detailed stats of each newsletter, which has helped to improve the mail content. Mass mailing is instantaneous, while keeps the from address white-listed on most public mail services.

I've been using the SMTP API and Newsletter modules for one year and five months.

No issues encountered.

No issues encountered.

No issues encountered.

4/5.

3/5.

We used the SMTP of AWS but our email address was blacklisted on mail services such as Gmail and Yahoo.

It was easy for me as I'm a software developer and Unix system administrator.

It was implemented in-house.

We pay for their silver package. Day to day, our usage is on pre-defined templates, so there are no major costs in running with this product.

We tried own SMTP on AWS, which caused our mail to be blacklisted.

This is simple and fits to our mass mailing needs. It's good for e-mail marketing.