Adobe acquired Omniture in 2009 and re-branded the platform as SiteCatalyst. It is now part of Adobe Marketing Cloud along with other products such as social marketing, test and targeting, and tag management.
SiteCatalyst is one of the leading vendors in the web analytics category and is particularly strong in combining web analytics with other digital marketing capabilities like audience management and data management.
Adobe Analytics also includes predictive marketing capabilities that help…
N/A
Oracle Marketing
Score 7.0 out of 10
N/A
Oracle CX Marketing (formerly Oracle Marketing Cloud) is a solution designed to enable marketers to plan and execute automated marketing campaigns via email, display search, video advertising, and mobile while delivering a personalized customer experience for their prospects.
It was quite complex to generate segments with Adobe
analytics and I wasn’t personally satisfied with the overall performance of
Adobe Analytics and wasn’t enough flexible in any way. So we decided to switch
Due to some issues (downtime, being on E9, feature availability, customer support) we ultimately decided to go with Marketo. When we were first looking for automation (2009) we decided on Eloqua over Marketo because we were worried about Marketo's ability to scale with us. At …
Maybe for a small company with small products for their thing, Adobe may be bit of an implementation too much for them, but when it comes to companies like us, like a life sciences or large enterprises and even small enterprises, but with more products, more analysis that they need to make their marketing experience better, maybe Adobe product is the best suitable.
A duration of one and a half years is enough for us to recognize the capabilities of a tool and in my opinion, this one is just a great tool to manage marketing campaigns of even massive-sized firms. Its marketing automation tool and its way of managing campaign and the way it executes digital initiatives is enough to get an inkling of its abilities. Less favorable for the people who want to have something at a cheap price and are more dependent on the reports as its reports have nothing much in detail.
It summarizes large complex data better than any other analytics solution I've dealt with without the need for sampling, gives the right level of detail, does the right level of breakdowns, aggregation. I consistently not only use Adobe Analytics, but I use other data sets and compare against Adobe Analytics. And as I go into Adobe Analytics and compare, as long as I've done the query right and the other systems, they're very, very close. And if anything, with a lot of Adobe's newer products, they've gotten more accurate over time. So that's basically, you asked me what I liked about it. I like that it's accurate. I like that I don't have to do a lot of explaining. There's enough explaining in the world of web analytics to have to go back and explain why data's problematic. And so like I said, provided that the implementation is correct, it's a very easy conversation. Even if people may not like the answer.
Support. I mentioned this earlier and we don't know what we don't know. Researching the massive amounts of documentation isn't realistic with bandwidth constraints, and our rep getting frustrated with us when we go through what we are seeing is disappointing.
Education. More please, and designed more towards the "business side". I get with the many many many different implementations (every company is different!), that it's tough, but even a basic of the basics would be nice for situations that everyone is looking at, like the engagement with the merchandising on the home page (or any certain page).
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.
We've found multiple uses for Adobe Analytics in our organization. Each department analyzes the data they need and creates actionables based off of that data. For E-Commerce, we're constantly using data to analyze user engagement, website performance and evaluate ROI.
We have been able to automate so many marketing processes with Eloqua over the past 5 years that the only direction would be to adopt the latest and greatest features Eloqua adds. The alternative would be to go back to the marketing stone-age and start over again. And we would rather move forward with increased automation and efficiency.
Sometimes the processing times are very long. I have had reports or dashboards time out multiple times during presentations. It could be improved. It is understandable since there is a huge data set that the tool is processing before showing anything, however for a company that large they should invest in optimizing processing times.
Personally, I find it quite easy to use. But for those members of our team who have little or no testing experience, it's been a bit more difficult. There's also training required for development teams in order to have your campaigns coded and set up in the most efficient way. Our developers have been able to do basic and intermediate tests with no difficulty, and they find the interface itself quite intuitive... it's just the extremely complex tests that require a bit more understanding.
I do not ever recall a time when Adobe Analytics was unavailable to me to use in the 8 or so years I have been an end user of the product. My most-used day-to-day analytics tool Parse.ly however, generally has a multiple hours planned offline maintenance every two to four weeks, and sometimes has issues collecting realtime analytics that last anywhere between 15 minutes to an hour, and happen anywhere between 1 to 5 times a month.
Again, no issues here. Performance within the day updates hourly. other reports are updated overnight and available to access by the next morning. Pages load quickly, the site navigates easily and the UX is quite straightforward to get command over. On this front, I give Adobe kudos for building a great experience to work within
There are occasional complaints about slowness to refresh a screen or build a report. However, this is as much a factor of network access speeds as the system itself, since often the complaints occur when someone is accessing on a wireless network.
I barely see any communication from Adobe Analytics. The content on the web is also not that great or easy to read. I would recommend a better communication about the product and the new addons information to come to its user by a better mean.
We found that we often were telling support people how the system worked. Because we were on E9 that created a lot of support issues as well since few people on the support team seemed to know how E9 worked. That was mostly okay except when we had major system issues (like SSO preventing us from logging in after an update), it became really hard to get answers that weren't vague. It was always the issues that had the highest visibility within the organization (like with Sales) that seemed to take forever to resolve and didn't have a clear escalation path. When Oracle switched Eloqua over to the Oracle support portal it just got worse
It was a one-day training several years ago that cost the organization several thousand dollars. There were only about 10 people in the training class. Adobe tried to cram so much information into that one-day class that none of our users felt like they really learned anything helpful from the experience. Follow-up training is too expensive
They offer very basic classes which are required for master certification.
After having been through it, I would not consider anyone with a master certification any more qualified, unlike Salesforce.com certification which is a more difficult thing to acquire. For example, one of the classes towards certification was around social media. I would have expected examples of how to incorporate into campaigns in the product, with a demo and hands-on test. Instead, it was a powerpoint slideshow that went on way too long and covered really basic stuff like “what is Facebook, what is Twitter”
The online training for Adobe SiteCatalyst consists of short product videos. These are ok, but only go so far. For a while Adobe charged a fee for this, but recently made these available for free. There are many great blog posts that help users learn how to apply the product as well.
Ok, so, this sounds like it could be horrible because it was all remote, but we loved it... the Adobe training environment was easy to use, and the trainers were engaging. It was simple to switch back and forth between the meeting and the hands-on exercises in their training instances. We took the fundamentals training early in our implementation-- before the consultants came onsite-- and I know this made a big difference in our implementation, because we were able to ask informed questions throughout
One of the benefits and obstacles to successfully using Adobe Analytics is a great / more accurate implementation, make sure your analytics group is intimate with the details of the implementation and that the requirements are driven by the business.
I give it a 10 because the only issue we had was a result of not following the guidance we were given. Maxymiser provided a customized implementation guide for each site where we were adding the code. On our site implementations when we followed that guide to the letter, it was extremely fast and easy and has worked very well.
Google Analytics comes across more of a reporting tool whereas Adobe Analytics is more of an Enterprise level analytics tool. Contentsquare provides some traffic and flow capabilities but not to the same level as Adobe Analytics. However, Contentsquare's major advantage is its Zoning (Heatmapping), Impact Quantification and Find 'n' Fix modules; none of which are knowingly available in Adobe Analytics.
It was quite complex to generate segments with Adobe analytics and I wasn’t personally satisfied with the overall performance of Adobe Analytics and wasn’t enough flexible in any way. So we decided to switch to something else better than Adobe Analytics and is available in the market at a cheap rate and we ended up doing our research for the most suitable tool at Oracle Infinity and we don’t regret our decision.
Adobe Analytics is relatively affordable compared to other tools, given it provides a range of flexible variables to use that I have not found in any other tools so far. It is worth investing in if your company is medium or large-sized and brings a steady flow of revenue. For small companies, it can be overpriced.
My organization uses Adobe Analytics across a multitude of brand portfolios. Each brand has multiple websites, mobile apps and some even have connected TV apps/channels on Roku and similar devices. Adobe can handle the multitude of properties that have simple, small(ish) websites and the larger brand properties that include web, mobile and connected TVs/OTT devices.
Each of those larger brands has multiple categories and channels to keep track of. We can see the data by channel/device or aggregate all the data together. This gives our executive teams the full picture and the departmental teams the view they need to see their own performance.
Eloqua is definitely good for larger companies that have 100,000+ contacts and complex marketing workflows and data. Personalization is fairly robust with Eloqua for larger campaigns with smart content and features. Scaling across channels is also seamless - as the platform has great options for non-email channels like SMS, Direct Mail, Chat, etc.
The professional services team is one of the best teams for complex adobe analytics implementations, especially for clients having multiple website and mobile applications. However, the cost of professional services is a bit high which makes few clients opt out of it, but for large scale implementations they are very helpful
Adobe Analytics impacts nearly every aspect of a billion plus dollar revenue eCommerce business. From measuring the impact of new build features to marketing campaigns.
We are saving substantial money and resource effort by consolidating all of our properties to Adobe Analytics from alternative solutions, at which point we will finally be able to report on Total Digital, rather than disparate reports.
We support experimentation on every platform and the performance is only known through Adobe Analytics tagging.
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
