Constant Contact vs. Drupal

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

Overall, I would give my rating of Drupal a 7/10 because there is an easy user experience for those without a website background but there is some technology work required to build more website capabilities that aren't as user-friendly. Drupal is specifically well suited to update content (like changing Relationship Manager cards when there is employee turnover), post announcements (putting up a holiday banner to let our customers know the dates we will be closed over Thanksgiving, Christmas, etc., and creating a sophisticated website hierarchy of pages (for our firm, several dropdowns depending on if you're looking for personal banking, business banking, investment banking, about us, etc.).

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.

• It has excellent security features and consistent updates.
• It allows for extensive customization with the integrated themes and core code, especially when you first install it. This allows our dev team to get creative with marketing initiatives.
• There is a large online community of Drupal users that consistently help answer any questions and issues

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

• Security and new release notifications are a hassle as they happen too often
• Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
• Steep learning curve, but worth it

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.

The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.

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

As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.

Incentivized

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

Incentivized

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

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

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

Incentivized

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.

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

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

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

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.

Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.

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

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

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

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs