Adobe Journey Optimizer is a customer engagement solution, enabling brands to orchestrate and deliver personalized customer engagement across all channels — including email, web, app, mobile, and more — in the moments that matter to customers.
N/A
Drupal
Score 7.0 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.
AJO is best suited for advanced Martech teams who are already bought into the Adobe ecosystem through the use of RTCDP, AA, AAM, etc. Organizations that are starting their Martech journey are good candidates, as well as those who are reevaluating all of their marketing channel vendors near the same time. Success in AJO is highly dependent on the number of marketing channels added. Close coordination with database teams is essential for success. Many of the offline data requirements benefit from modeling of the data. Having dedicated resources developing AJO (RTCDP)-specific views will reduce the amount of QA required to bring the solutions to market
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.
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.
It has been working very well, and actually it is a reliable tool for audience segmentation and everything that needs to be done for a campaign to deploy correctly
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.
At times, Adobe Journey Optimizer offers too many options, making things less user-friendly than I would personally prefer. As mentioned earlier, there is a tendency to encounter decision paralysis with the increase in available options. While having options is excellent, in typical Adobe fashion, too many can be overwhelming for users
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.
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.
Sometimes when the manager connects to a support representative, even though the response is very immediate, they are not always able to provide a solution and we end up resolving the issue other ways
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.
The only thing I wanted to mention is that when going into the email edition, when adding labels, I was able to copy and paste the labels before, and now it has changed and I am no longer able to do it without editing the label itself
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%
They both have their pros and cons, I feel it depends on the users that the products are targetting, SFMC is has more specialized customizations, Adobe does offer similar but require a higher technical knowledge which is not something that is provided bt the other product
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.
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.
Multichannel onboarding journey improving the engagement of freshmen in the business, resulting in a decrease in the dropout rate.
Separate business of anticipation of receivables from suppliers that used to be manual and now I have connected this entire operation via the S3 connector, less manual work and significant gains in conversions and payments
