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
Adobe Marketo Engage
Score 8.2 out of 10
N/A
Adobe Marketo Engage (acquired by Adobe in 2018) is a marketing automation platform whose basic features include email marketing, drip nurturing, landing pages, and lead scoring, but other editions offer additional advanced features. Typical customers are B2B firms with complex sales cycles.
Marketo has the best user interface which makes it very simple and powerful. The documentation is very well explained and any new person can read it and use Marketo. Marketo has very rich functionality.
Prior to joining our company, I had previous experience in multiple marketing automation systems, the exception - Marketo. Since joining I have been pleasantly surprised with the Similarities Marketo has to say Pardot and ExactTarget. The deciding factor for us was that the …
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
Adobe Marketo Engage is great for lead gen because of the out of box solutions. We import leads from Google, LinkedIn, Meta, Tradeshows, and web forms. It allows me to track leads from the moment they enter the system to the point where they become customers. I use it to score leads, segment them, and nurture them with targeted content. It's especially useful as a B2B organization.
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
Like I have said Marketo has been very helpful by helping us to connect us with our customers and keeps them coming back, hence saving time, effort and resources.
Let AI build predictive audience and segments easily.
Personalize experience with active listening and triggered content.
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.
Marketo's email editor is basic in comparison to other cheaper alternatives out there.
Marketo doesn't work as well in B2C scenarios as it does in B2B. One of the painpoints of this is it's difficult to showcase a selection of product recommendations based on purchase behaviour without a very time consuming workaround. It's manageable if you're only selling a handful of products, but it's inefficient when dealing with a large catalogue.
Marketo's form and landing page builder are also behind the times. Perhaps not as bad as the Salesforce Marketing Cloud platform, but for an enterprise company the product should be much better.
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.
It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
In some aspects, the tool can feel quite clunky in parts. But with the rich feature set it has, it's understandable. There is a lot of room for improvement for the user interface. The system itself doesn't have a slick or modern feel, so the usability could feel nicer to use with these areas considered.
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).
Marketo provides different way and abilities to connect. If you are having product support or unexplained errors you can get someone on Marketo support 24 hours a day. One of Marketo's greatest assets in my opinion however would be the community. Often times our company is just looking for case success stories from someone else. In the community you can search for problems you are currently facing and see others having the same issue and solutions for those issues. If not, you can pose a question to the whole community and champions of the product and others can chime in to provide suggestions to fix your needs. The community is truly a 24/7 place to get your answers quickly.
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.
There are times when it is slightly slow for us, where we sit on a screen waiting for it to load. This could be our internet since we have had the same issue occasionally with other systems, but it is enough to make you crazy.
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.
On multiple occasions we've had Marketo support (technical and license based) issues. Technical issues were minor and resolved within a day. License based issues (even things encouraged by Marketo for partners, like provisioning another license) took WEEKS. They actually took so long to respond that the client we were working with withdrew from the contract because they were no longer convinced Marketo was capable of supporting their business. As an agency trying to sell the software, you can only explain away so much before they just made us look silly.
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.
Our account rep stopped out in Lincoln, NE to ensure we were properly set up and running. This was very much appreciated. I was very, very new at this point, so I can't comment very much on the extent of what was taught because I was still brand new to the company and the system
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.
I had never used Marketo prior to taking this job so online training was my starting point. I was able to follow along, it was interesting and quickly and efficiently taught me what I needed to know without a lot of fluff. It was far from boring and really helped me get my hands dirty with Marketo.
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%
1. Have a content marketing plan to run in parallel with the marketing automation installation--you'll need a lot of content to make full use of Marketo's capabilities. 2. Work with sales (and ISRs) to define and document a workflow--build your Marketo installation around how you do business--not figure out how to apply your business to the tools 3. Spend time of data cleaning--both an initial project as well as a strategy for ongoing data management. We found some change manaement issues (no more appending ZZZ to the first name to identify contacts who have left the company, for example, or prohibiting the entry of "info@company.com" email addresses). 4. Find some champions in the sales and ISR teams. You'll have both fans and detractors--work with the fans to build some success stories
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
Prior to Marketo, we used SharpSpring. I will say that SharpSpring is more intuitive to use than Marketo, but it has much less functionality. If you have the time to really learn Marketo, it has much more to offer as well as many more options to customize the solution to your exact needs.
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.
We look at scaleability in a few different ways. First, the speed while using Marketo has remained relatively the same as our database has grown. Though I would say Marketo is slow at times, it has not gotten slower over the last few years. If anything, it has improved, and they are working to improve it. Second, the amount of programs we have developed in Marketo has exponentially grown as well. Marketo has allowed us to drastically increase our output without having to drastically increase our headcount.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.
