Drupal vs. Pendo.io

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

Pendo.io is useful in generating great dashboards that present user analytics in the best possible view that could be used for analysis & derive key insights on what could be done if there's a feature that's not being recognized by end users or if there are any pain points where users are struggling more around a workflow which is technically not that difficult. Pendo.io also can be used to create impactful guides where intercatoin of a user with the Guide can be created in less steps & have relevant information about that workflow that the user is completing. Pendo.io's resource center can act as a one stop hub to present any sidewide updates which could be information of Prod releases, New KB Articles, Register to any event, & much more. Segments can be created in as many variation as one can. In fact, Segments are the ruling property or feature that works so handy, which reduces a lot of iterative work.

Incentivized

• 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

• NPS Surveys
• Feature usage insights
• Identifying user behaviors using Replay feature
• Clearly segmenting users in a way we want it to be
• Identifying time spent on a feature/product to better understand what customers actually use
• Documentation, in-app guides and help section

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

• Dashboard is sometimes very slow to load
• Preview is problematic if the Pendo.io user doesn't have access to the target environment or application where the guide is going to display
• It would be ideal to have a gallery of thumbnail images of previously used guides to select from, either to pull a screen capture or to use as a template. It's cumbersome to go to the guides, find the one you want, click on Preview, etc.

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.

We have had an excellent experience with Pendo. When we've had questions or concerns, Pendo is very quick to respond and communicate with us. We have experienced top-notch customer support and customer engagement. We have actually modeled some of our implementation and product processes after Pendo's examples.

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

It is intuitive for core tasks like tracking feature usage, building Guides, and viewing dashboards. The interface is clean and well structured, making it easy for product managers and operational teams to get value quickly without heavy technical support. However, there is a noticeable learning curve when setting up advanced custom events, reports, or integrations, which can take some time and internal knowledge-sharing to master.

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

Every time I have logged into Pendo, the service has been available for me to use. The page has never been down when I am trying to get info from there.

Incentivized

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

Everything loads fairly quickly and it's not slow. I don't use an integration, I log in straight in the webpage.

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

They've been great anytime that we have needed help with something. They also have some really great help articles. We're able to figure most things out through their articles, but when we've had to call in they've been very helpful and we haven't had any problems. I'd highly recommend working with them.

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.

The training schedule was well thought out and tailored to meet our needs. Chantelle stayed with us through the whole implementation and made sure that we were good to go.

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

Use Segment to install and cut developers out of the work cycle!

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

I have just very superficial experience with Google Analytics but I do believe that Pendo.io is a much much better tool in pretty much all aspects of it. It has a ton more features and capabilities and even for the capabilities where there is overlap, Pendo seems to come out ahead easily. There are aspects that Pendo could improve for sure such as what metadata it captures from the users; an example of this is screen resolution which Google Analytics captures but Pendo does not.

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

The system is pretty flexible and scalable, I have used it in different browsers and devices without issues.

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

• Reducing development time with in-app guides and resource center, with product management being able to agilely create guides in real time, this could be as much as 1 full time developer in savings.
• Reducing business time scoping "rock fetches" than are proven to be invaluable based on analytics, each time 1 single piece of analtical data saves around ~20 hours across multiple resources.
• Increasing user satisfaction with in-app guides and resource center
• Increasing usage of key features through targetted messaging, those key features either drive costs ou of our business or add value to customers business.

Incentivized