Adobe Marketing Cloud is a suite of products including analytics, social, advertising, targeting and web experience management. It comprises foremost the popular integrated web content management and digital asset management (WCMS / DAM) solution Adobe Experience Manager, Adobe Campaign's cross-channel campaign management and marketing resource management capabilities (based on technology acquired with Neolane in 2013), the Adobe Audience Manager data management platform, analytics, and other…
N/A
Drupal
Score 8.2 out of 10
N/A
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.
If you have a rather large budget and/or several clients to take advantage of the AMC, you would likely benefit from its all-in-one solutions. There are a myriad of excellent tools for digital marketing professionals to take advantage of within the suite, and creating a campaign becomes much more manageable for collaboration and execution through to reporting thanks to the suite's vertically integrated nature.
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
Content Analysis - Between the Pages report and the participation metrics which show what percentage of conversions a page was involved with, you get an excellent analysis of what content is important and effective, and what is not. With the ability to add up to ten metrics side by side, drill downs, and power tools like Ad Hoc Analysis, you will know exactly where you need better content.
Pathing - Adobe Analytics captures every single path of every single visit of every single visitor and puts it at your fingertips. There are tools to aggregate common paths so you find out how frequent they are, lots of good page flow reports, and tools to pick out specific paths that will keep you from being overwhelmed. This has been absolutely invaluable to us as we have learned about how our customers are using our sites and which paths are leading to exits rather than converions.
Customization - There are so many custom metrics and dimensions you can add and you can create segments based on all of them, along with the out of the box metrics and dimensions. You truly get an implementation that is specific to your company, your needs, your strategy, and your site.
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.
Customer services could be improved for smaller clients. Adobe Marketing Cloud provides great support for most of its customers, however, it may not work well enough for smaller engagements.
Adobe could offer multiple price options based on the usage, which is missing at the moment.
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.
Although a powerful tool, Google Analytics has been catching up in capabilities and is much simpler to use. As analytics move to the spotlight, more sections in a company want to have access to it. However, creating straightforward reports/dashboards and sharing them with different groups is not a strength of Adobe Marketing Cloud.
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.
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 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%
In comparison to other services, Adobe is particularly robust, and the platform is better suited to customers with a high level of maturity in the digital environment, who need a platform to overcome and solve day-to-day problems.
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.
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.
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.
