Drupal vs. Quantum Metric

If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.

Incentivized

Quantum Metric is a true professional, and I love the level of insight and industry knowledge they bring to the table. We use it at the departmental level, including marketing, customer service, and IT. Session replay allows our data consumers to derive insights faster and easier than digging through data. It lets us see or understand how users feel and work to enhance those feelings. The quality of support and the time to respond are also noteworthy. They have great coverage, but the learning curve is very steep and requires a lot of technical support and hand-holding.

Incentivized

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• Identifying user pain points and frustrations. Quantum Metrics has a data point called Rage Click which shows when a customer has clicked multiple times back to back on a particular section of the website.
• Replaying a session to see everything that is loading on the front end to the customer, as well as the backed end of the website, has been critical in troubleshooting the experience.
• Heatmaps are a awesome tool we have found very useful in showing engagement with different content on the page, how far user scroll & drop off and to see a split side by side view of the same page in an a/b test.

• This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
• Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
• The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.

Incentivized

• Quantum could share some use cases implemented by similar industries in accordance with the key problems as inputs.
• We should be able to see some of the most common solutions that could be integrated within our product based on the step of the user journey I am at.
• Expanding capabilities to integrate with high-level tools integrated.

Incentivized

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.

Quantum is a nice tool and is user friendly however I believe there always room for improvement. We have experienced minor issues with a few sessions which were solved by Quantum support reps in a timely manner and some of the dashboards are not as robust as other tools we use

Incentivized

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

For a new user, it's pretty intuitive to onboard and start doing the basic functionalities. But QM has a lot of functionalities which can be leveraged by more team members (especially when you don't have analysts dedicatedly using this) if further enhancements to usability are made.

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).

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

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've been very impressed with the support Quantum Metric has provided. Our amazing Customer Success team has provided excellent service and has gone above and beyond in helping us use and understand the tool. We hold weekly calls with multiple teams and QM has been proactive in bringing things to our team's attention and making suggestions. The support has been one of the most important aspects of having QM and has allowed us to make great strides in improving how we use data and user research in our work.

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.

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

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

We have used - as an organization - multiple products that each fill a roll or task Quantum Metric provides...however I think there are very few tools or SaaS solutions out there that bundle so much into one solution. QM was better than the replay tool another group was utilizing (Mouseflow) because with our contract we could capture and review way more replays as well as have those replays married to actual, quantifiable data. From an analytics point, is so much easier to install event tracking as opposed to our basic Google Analytics implementation. However, I would still use GA as a primary record for measuring overall site performance since QM doesn't have robust product sales tracking. At one point we did review a competitor called Content Square. They seemed very focused on heat mapping.

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

• 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

• The service is not cheap, so don't commit unless you're going to use it.
• Really improved our tech support process by allowing us to identify problems much sooner.
• Helped identify potential frustrations, which could be eliminated to reduce friction at checkout.

Incentivized