Adobe Audience Manager is a data management platform (DMP) that is integrated into the Adobe Marketing Cloud.
N/A
Apache Kafka
Score 8.6 out of 10
N/A
Apache Kafka is an open-source stream processing platform developed by the Apache Software Foundation written in Scala and Java. The Kafka event streaming platform is used by thousands of companies for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications.
N/A
Pricing
Adobe Audience Manager
Apache Kafka
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Adobe Audience Manager
Apache Kafka
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
Apache Kafka
Features
Adobe Audience Manager
Apache Kafka
Data Collection
Comparison of Data Collection features of Product A and Product B
Adobe Audience Manager
8.6
16 Ratings
5% above category average
Apache Kafka
-
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
Apache Kafka
-
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
Apache Kafka
-
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
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.
Apache Kafka is well-suited for most data-streaming use cases. Amazon Kinesis and Azure EventHubs, unless you have a specific use case where using those cloud PaAS for your data lakes, once set up well, Apache Kafka will take care of everything else in the background. Azure EventHubs, is good for cross-cloud use cases, and Amazon Kinesis - I have no real-world experience. But I believe it is the same.
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.
Really easy to configure. I've used other message brokers such as RabbitMQ and compared to them, Kafka's configurations are very easy to understand and tweak.
Very scalable: easily configured to run on multiple nodes allowing for ease of parallelism (assuming your queues/topics don't have to be consumed in the exact same order the messages were delivered)
Not exactly a feature, but I trust Kafka will be around for at least another decade because active development has continued to be strong and there's a lot of financial backing from Confluent and LinkedIn, and probably many other companies who are using it (which, anecdotally, is many).
Sometimes it becomes difficult to monitor our Kafka deployments. We've been able to overcome it largely using AWS MSK, a managed service for Apache Kafka, but a separate monitoring dashboard would have been great.
Simplify the process for local deployment of Kafka and provide a user interface to get visibility into the different topics and the messages being processed.
Learning curve around creation of broker and topics could be simplified
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.
Apache Kafka is highly recommended to develop loosely coupled, real-time processing applications. Also, Apache Kafka provides property based configuration. Producer, Consumer and broker contain their own separate property file
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.
Support for Apache Kafka (if willing to pay) is available from Confluent that includes the same time that created Kafka at Linkedin so they know this software in and out. Moreover, Apache Kafka is well known and best practices documents and deployment scenarios are easily available for download. For example, from eBay, Linkedin, Uber, and NYTimes.
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.
I used other messaging/queue solutions that are a lot more basic than Confluent Kafka, as well as another solution that is no longer in the market called Xively, which was bought and "buried" by Google. In comparison, these solutions offer way fewer functionalities and respond to other needs.
Positive: Get a quick and reliable pub/sub model implemented - data across components flows easily.
Positive: it's scalable so we can develop small and scale for real-world scenarios
Negative: it's easy to get into a confusing situation if you are not experienced yet or something strange has happened (rare, but it does). Troubleshooting such situations can take time and effort.