Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Gainsight PX
Score 7.6 out of 10
N/A
For SaaS products, Gainsight's product experience software enables companies to track every step of their user's journey and fully understand how they're interacting with a product over time.
$0
100 or less MAUs (Monthly Active Users)
Pricing
Drupal
Gainsight PX
Editions & Modules
No answers on this topic
Starter (Free)
$0
100 or less MAUs (Monthly Active Users)
Starter
Starting at $400/M
500+ MAUs (Monthly Active Users)
Growth
Custom
Per MAUs (Monthly Active Users) and more
Offerings
Pricing Offerings
Drupal
Gainsight PX
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Drupal
Gainsight PX
Features
Drupal
Gainsight PX
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
73 Ratings
1% below category average
Gainsight PX
-
Ratings
Role-based user permissions
8.173 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.6
68 Ratings
2% below category average
Gainsight PX
-
Ratings
API
7.063 Ratings
00 Ratings
Internationalization / multi-language
8.159 Ratings
00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
6.4
77 Ratings
20% below category average
Gainsight PX
-
Ratings
WYSIWYG editor
5.970 Ratings
00 Ratings
Code quality / cleanliness
8.074 Ratings
00 Ratings
Admin section
6.577 Ratings
00 Ratings
Page templates
5.776 Ratings
00 Ratings
Library of website themes
5.667 Ratings
00 Ratings
Mobile optimization / responsive design
6.571 Ratings
00 Ratings
Publishing workflow
6.775 Ratings
00 Ratings
Form generator
6.271 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
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.
It’s a robust tool that allows you to easily map and track key features and actions within your products. It also allows for in app communications to help guide the user through the path you want them to follow. The ability to connect with Gainsight CS also allows you to leverage that data to drive actions for the account team, incorporate it in health scoring, and use it to trigger digital programs. You do need a well thought out strategy for management of the platform, the data and how you will use it.
Gainsight PX provides powerful segmentation capabilities to help marketers target the right customers with the right message. Through its segmentation capabilities, Gainsight PX enables marketers to create custom segments based on user behavior, demographics, and other criteria to ensure that the right message is delivered to the right customer.
Gainsight PX offers robust analytics capabilities to help marketers gain insights into customer behavior and engagement. Through its analytics capabilities, Gainsight PX enables marketers to track user engagement, identify customer trends, and gain insights into customer behavior.
Gainsight PX provides an intuitive user interface to help marketers quickly and easily create and manage campaigns. Through its user interface, Gainsight PX enables marketers to create and manage campaigns with ease, allowing them to quickly launch campaigns and track their progress.
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.
Dashboards. There is no way to provide notes to others which would be very beneficial in consuming data across a team. Lacking functionality - no resizing, no organization options, run into bugs when using it frequently, overall hard to design a layout that is easy to follow.
No way to identify what features/elements are being used but aren't tagged. This would be a huge value add.
Retention Analyzer. Default view doesnt allow for filtering and includes test data. In our case this doesnt allow for a true comparison between two segments.
Segments. You can't use segments in areas you should be able to. I shouldnt have to recreate a segment as a saved filter.
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.
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.
It is a good product, but like with every product, there is room for improvement or even just things I, as a user, would prefer, such as the ability to click on a company and have it go to Salesforce instead of Insight. It can also be difficult to find certain reports.
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.
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.
I have not had to contact support frequently but when I have I used the chat and my questions were answered immediately. I've also used their knowledge center, help documentation and training videos which are all very thorough. The support we've received from our Customer Success Manager has been helpful as well.
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%
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.
Heap has a great value proposition and very nice user experience. But it lacks the clear funnel analysis that Gainsight PX provides. Plus Heap also does not have integration with a lot of CRMs and Customer data platforms. Also, Additionally if you go in the market to find Heap implementors or SI vendors, you won't find any.
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.
Allow us to integrate actual product usage with Salesforce.
Too much developer time went into it, especially when the premise was that this was mostly going to be handled by the Product team. This was mostly because the Gainsight PX event editor doesn't support more complex querying on events.