Constant Contact vs. Netlify CMS

Constant Contact is an excellent tool for sending out flyers and newsletters. However, I feel the content's appearance is typically all the same. When I receive an email from Constant Contact, I can immediately identify it - the templates usually all look the same. When sending out communications with images, it is easy to use Constant Contact and link webpages. However, the email layout is always vertical and can get very lengthy. I prefer a more flip-book approach with options to flip the page.

Incentivized

Netlify CMS is well suited when you have very less frequent updates to your content, maybe once a day and very few people need to access your data. You can connect it to Netlify, GitHub, or any platform and have multiple people access it and do as many updates as you wish, but the process is not well-defined and you need to build your own system for that. It is well suited for projects you need to pull off with very low cost, it is essentially free as the software is open source and free to use, and all you need to do is set up your schema correctly and find a deployment pipeline where you can build your static site/API to redeploy whenever the content changes. I personally used a GitHub Login -> Netlify CMS -> next app consumer of content -> GitHub pipelines to run next SSG -> GitHub Pages to deploy the built static site. It might not be appropriate for large teams where users themselves need no-code tools to modify the schema of the content.

Incentivized

• Market segmentation is great: my main segmentation is by region because that's how our sales team is divided.
• Lists: making customized email lists is easy and intuitive; the custom fields allow some flexibility in case our fields don't exactly line up with Constant Contact's.
• Campaigns: creating campaigns is quick and simple. I especially appreciate the 'resend to non-openers' option. I am constantly using this feature.
• Subject line generator: I like using the recommended subject lines. I'm able to plug in their recommended ideas, or sometimes, this feature helps me generate my own ideas.

• Storing content data in customized schema without a database
• Full control over your content and infrastructure where it is deployed and stored
• Very low-cost way for building your own CMS and CDN

Incentivized

• It would be nice if we had more customizable options for emails - like moving around pictures and text boxes, rather than a set spot for everything to go.
• I would like it if multiple people could work on a document at one time. So if I'm in charge of graphics, I can get those updated while someone else is entering content, etc.

Incentivized

• Linking between different schema types, i.e. having some relations between content
• Better ways to define content schema, like how TinaCMS would handle using a JSON

Incentivized

There is no doubt that we are going to renew Constant Contact. We have not just invested a lot of time in learning and creating a great looking product but we have developed a strong database of information that allows us to track how we are doing for each newsletter. This supports our goals of creating products that residents desire and are excited to receive.

There is always room for improvement. I don't know how they test their systems, but they should invite not-so computer savvy people to test it. If I, as an expert have problems, they need to think like the technophobe. Since I've used Constant Contact in the past as part of my former employment, I have not viewed any of the tutorials and just jumped in to work on my client's newsletter. With that said, I found some areas easy and some a bit cumbersome

No major problems in sending out the email campaigns and accessing the analytics

Incentivized

The system seemed quite slow sometimes. Specifically, there was sometimes a delay in sends if it was during a high traffic period. There were time-outs when uploading new code for an email, and a lag in reporting analytics which was sometimes as long as 72 hours

I think the overall support for Constant Contact has always been incredible; I have nothing negative to say. Our customer support representative was attentive, easy to understand, and very knowledgeable. I never felt like I wasn't a priority of his and my issues, while very small, were fixed in a very short time frame.

Implementation is very easy for someone who wants to send out the “batch and blast” type newsletters. If you want to use their templates with no customizations, the product works fine. However, the more customizations you get into involving link color, etc, that’s where things can get tricky for someone who may not be familiar with coding

Constant Contact is much more intuitive for people who are not tech-savvy. Also, while sendgrid offered more options in it's drag and drop interface, it displayed differently across different email clients, which made it very cumbersome to use. It also took much longer to upload contact lists and it was harder to manage existing contacts. Performance in sendgrid was much slower as well, and the Preview feature was quite buggy. Our team initially chose sendgrid because of the integration options that it's API offered, but we ultimately switched to Constant Contact because it was much easier to build campaigns and better suited our requirements.

We really can't compare it to full-fledged CMS software, like WordPress, which has a lot of community and support with widgets, plugins, and whatnot. It's not built for that, but you can compare it to Contentful, Ghost, Strapi, etc., which provide similar functionality to a headless CMS with custom schema options, but even among them, it still lacks a lot of functionality, ease of use, and support. But Netlify CMS pros would be of the opinion that compared to other platforms where most schemas need to use their own tools and frameworks, it's very cost-effective. Something new called TinaCMS has come up to compete with Netlify CMS by covering most of its shortcomings, but it's something new being built by the same team that built Forestry CMS and comes with many modern features, yet currently only supports NextJS SSG.

Incentivized

Very reliable in sending email campaigns and controlling the recipients so that no contact is sent the same email more than once, even if they are on a resent list

Incentivized

• I have had nothing but positive impacts from using Constant Contact.
• The church is large, and there are many subgroups and axillary groups within the church. Setting up specific groups based on responsibility, interest, member goals, and service needs allows me to send information quickly, saving valuable time for other tasks.
• Constant Contact allows leadership to stay personally engaged with the members I work with, without over-taxing my time. It feels so seamless.

Incentivized

• Helped us inject dynamic content into existing site very quickly
• Wasted a lot of time to implement when something complex, such as querying content, was needed

Incentivized