Adobe Audience Manager is a data management platform (DMP) that is integrated into the Adobe Marketing Cloud.
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.
N/A
Pricing
Adobe Audience Manager
Drupal
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Adobe Audience Manager
Drupal
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Adobe Audience Manager
Drupal
Features
Adobe Audience Manager
Drupal
Data Collection
Comparison of Data Collection features of Product A and Product B
Adobe Audience Manager
8.6
16 Ratings
5% above category average
Drupal
-
Ratings
Collection of first-party data
8.116 Ratings
00 Ratings
Collection of third-party data
8.116 Ratings
00 Ratings
Access to Third-party Data Providers
9.616 Ratings
00 Ratings
Data Classification
Comparison of Data Classification features of Product A and Product B
Adobe Audience Manager
7.3
16 Ratings
12% below category average
Drupal
-
Ratings
Audience taxonomy
7.916 Ratings
00 Ratings
Tag Management
6.215 Ratings
00 Ratings
Data Analysis Dashboard
7.816 Ratings
00 Ratings
Ad Network Integration
Comparison of Ad Network Integration features of Product A and Product B
Adobe Audience Manager
8.9
16 Ratings
11% above category average
Drupal
-
Ratings
Data Transfer
8.916 Ratings
00 Ratings
DSP integration
8.815 Ratings
00 Ratings
DMP Analytics
Comparison of DMP Analytics features of Product A and Product B
Adobe Audience Manager
6.8
16 Ratings
14% below category average
Drupal
-
Ratings
Campaign Analytics
5.516 Ratings
00 Ratings
Audience Analytics
8.116 Ratings
00 Ratings
Security
Comparison of Security features of Product A and Product B
Adobe Audience Manager
-
Ratings
Drupal
8.1
74 Ratings
1% below category average
Role-based user permissions
00 Ratings
8.174 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Adobe Audience Manager
-
Ratings
Drupal
7.6
69 Ratings
2% below category average
API
00 Ratings
7.264 Ratings
Internationalization / multi-language
00 Ratings
8.160 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Adobe Audience Manager
-
Ratings
Drupal
6.5
78 Ratings
18% below category average
WYSIWYG editor
00 Ratings
6.171 Ratings
Code quality / cleanliness
00 Ratings
8.175 Ratings
Admin section
00 Ratings
6.878 Ratings
Page templates
00 Ratings
5.577 Ratings
Library of website themes
00 Ratings
5.468 Ratings
Mobile optimization / responsive design
00 Ratings
6.572 Ratings
Publishing workflow
00 Ratings
6.876 Ratings
Form generator
00 Ratings
6.372 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
If you are already using multiple other pieces of the Adobe Experience Cloud stack, adobe audience manager is an easy choice. It allows for quick and easy data activation for your first and potentially brokered 2nd party data. However this product will likely be absorbed into the adobe experience platform (AEP) soon. In the end I would wait to see where adobe is truly headed with this product before investing heavily without additional heavy adobe investments.
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.
We are able to generate reports that provide valuable insights into potential customer behavior, allowing us to better focus our marketing efforts.
By allowing us to understand who are key audiences are and how they overlap with other brands and products, AAM allows us to get a fuller picture of how we should target our audience.
Reporting in AAM is wonderful in that it is easy to understand and exportable. The use of graphics and updates make it easier to share insights with various team members--even those with minimum experience in marketing and analytics.
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.
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.
Overall usability is great, as are most of Adobe's software. Maybe a UI refresh could make it a bit easier to do advanced functions or reporting but, overall, it works very well. This is something you take for granted with Adobe solutions because when you try another vendor you realize how bad it can be.
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.
AAM has good support, but the support is not as available, due to waiting time and queue. The instructions presented are available, but it navigation is not easy between pages. However, instructions are usually direct and straightforward, but any underlying thoughts or questions won’t be easily answered without support from their service.
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%
I personally like the Adobe Audience Manager interface and it's easier to use for beginners. It also has some features that Google does not, nor do its other competitors. It is worth the money and time spent, overall. I feel like it gives a bigger and more in-depth picture to our company's audience than other programs.
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.