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

• 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.

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

• 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.

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

• It has helped us track our ROI better and see costs versus revenue coming in directly from emails.
• A/B testing is very helpful to ensure the best email is being chosen to get sent out.
• Our deliverability has improved a lot.

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