Adobe Experience Manager vs Oracle CX Marketing (formerly Oracle Marketing Cloud)

• Adobe Experience Manager is great for maintaining large websites with lots of content. It has a comprehensive repository and folder structure which makes it easy to organize and break down your website into sections.
• Although we have not personally used it much yet, Adobe Experience Manager has integrations with the other Adobe Experience Cloud products such as Campaign, Target, and Analytics. The newest version(s) also have integrations with Creative Cloud products like Photoshop, which allows creatives to upload assets directly into the DAM.
• Adobe Experience Manager has powerful live copy/translation tools that allow you to clone and translate webpages into other languages for alternate language versions of your site.

Read full review

• We can look for the behavior of our clients on our website and mobile application using the analytics it provides.
• It is highly customizable.
• It presents data in a form that is easily understandable and reports are highly beneficial for us.
• Analytics in the form of graphs.

Read full review

• Upgrading and applying patches can be hit or miss - I recommend backups because of the potential to damage the existing infrastructure
• Space management is an issue - every change or request takes up space that can be reclaimed, but only through a complicated procedure done through command prompts. There was no documentation for this on their site and we had to use a third party to create the procedure. It has to be run manually.
• There isn't a good backup system, particularly one that can be scheduled to run reliably.

Read full review

• Integration options outside of auto-syncs. I am currently having an issue trying to find an adapter to use with Eloqua to API into our data warehouse but keep the functionality on the Eloqua side.
• To provide more transparency and visual details of the syncs (integrations of outside data) from any other system that is feeding Eloqua, like what is being updated or changed, better explanations of errors, drill down to newly created records.
• Custom Objects - Need to have a way to create CDOs outside of just form submissions and uploading of lists, like if you needed to import a file nightly to feed that CDO data but automate the import and make sure it maps to a contact record.
• Import of data from a file on SFTP - There is no way to filter or create logic to control what is being fed into Eloqua. Currently, that manipulation has to be done by the IT side first. Less flexibility.
• Better auditing capabilities within the canvas. meaning, sometimes if something is changed or not working the problem may not necessarily show up in immediately, the pattern could take a while to present itself. For example, the feeders into the program. If there is a problem, I don't know that maybe contacts are not entering the program until we do reporting that month and realize there was a lull of contacts going through. Then we have a whole month of missed records or other potential data issues. When you get do large and your Eloqua machine is very robust, the harder it is to see everything
• Be able to add more than 250 custom contact records. That definitely inhibits my organization in how we need to use that record.

Read full review

• We can have multiple teams globally and connect anytime we want.
• Finding target audiences for advertisement campaigns became [so] much easier than before.
• One drawback is that the users have to be well trained and [preferably have] more IT knowledge among them to interact with the AEM.

Read full review

• We are able to use it to help our clients scale through testing
• We have been able to measure the impact of our events and sales events so we can determine which events to continue in the future and determine future investment
• Launch a new brand out of Eloqua and measure awareness

Read full review