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
Adobe Target
Score 8.9 out of 10
N/A
Adobe Test and Target is an A/B, multi-variate testing platform which Adobe acquired as part of the Omniture platform in 2009. It is now part of the Adobe Marketing Cloud. It offers tight integration with Adobe analytics and content management products.
N/A
Pricing
Adobe Analytics
Adobe Target
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Adobe Analytics
Adobe Target
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Adobe Analytics
Adobe Target
Features
Adobe Analytics
Adobe Target
Web Analytics
Comparison of Web Analytics features of Product A and Product B
Adobe Analytics
8.6
Ratings
7% above category average
Adobe Target
-
Ratings
Lead Conversion Tracking
8.30 Ratings
00 Ratings
Bounce Rate Measurement
8.20 Ratings
00 Ratings
Device and Browser Reporting
8.70 Ratings
00 Ratings
Pageview Tracking
8.90 Ratings
00 Ratings
Event Tracking
8.90 Ratings
00 Ratings
Reporting in real-time
9.30 Ratings
00 Ratings
Referral Source Tracking
8.10 Ratings
00 Ratings
Customizable Dashboards
8.20 Ratings
00 Ratings
Testing and Experimentation
Comparison of Testing and Experimentation features of Product A and Product B
Adobe Analytics
-
Ratings
Adobe Target
8.6
Ratings
5% above category average
a/b experiment testing
00 Ratings
10.00 Ratings
Split URL testing
00 Ratings
8.50 Ratings
Multivariate testing
00 Ratings
9.50 Ratings
Multi-page/funnel testing
00 Ratings
8.00 Ratings
Cross-browser testing
00 Ratings
8.60 Ratings
Mobile app testing
00 Ratings
8.60 Ratings
Test significance
00 Ratings
7.40 Ratings
Visual / WYSIWYG editor
00 Ratings
8.50 Ratings
Advanced code editor
00 Ratings
8.00 Ratings
Page surveys
00 Ratings
9.00 Ratings
Visitor recordings
00 Ratings
8.50 Ratings
Preview mode
00 Ratings
9.50 Ratings
Test duration calculator
00 Ratings
9.50 Ratings
Experiment scheduler
00 Ratings
9.00 Ratings
Experiment workflow and approval
00 Ratings
7.90 Ratings
Dynamic experiment activation
00 Ratings
8.00 Ratings
Client-side tests
00 Ratings
9.50 Ratings
Server-side tests
00 Ratings
8.00 Ratings
Mutually exclusive tests
00 Ratings
7.50 Ratings
Audience Segmentation & Targeting
Comparison of Audience Segmentation & Targeting features of Product A and Product B
Adobe Analytics
-
Ratings
Adobe Target
8.5
Ratings
0% below category average
Standard visitor segmentation
00 Ratings
8.50 Ratings
Behavioral visitor segmentation
00 Ratings
8.00 Ratings
Traffic allocation control
00 Ratings
8.50 Ratings
Website personalization
00 Ratings
9.00 Ratings
Results and Analysis
Comparison of Results and Analysis features of Product A and Product B
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.
We recommend this application because it allows us to segment and track the traffic of our domain under an analysis of their behavior, ranging from counting the number of clicks they make on a single element to the most complete action within our page in real time.
eVars (love, wish there was more but I heard they are unlimited in AJA)
Projects. The transition from Reports to Projects was easier for me to navigate than I thought it was going to be.
Adobe Templates. Again with the love. Nothing helps me more than copying a template and then deconstructing it to see how it works and reconstruct to how I want it to be.
Our site has about 250,000 definitions pages on dictionary.com. We've got about 150,000 synonym pages across the source.com. So very high volume of pages. As you can imagine, most of these are pretty low traffic. You've got maybe that top 5%, 10% are really driving a huge amount of traffic, but then you have all these really obscure things out there. There's still a lot of important information you can get there and oftentimes in our Adobe Analytics reporting suite, it'll kind of bundle things at low traffic at a pretty low threshold for us to get to. So that can be a limitation when we're trying to do some really detailed keyword analysis. The way we've gotten around that is we make use of the data feed and the export. So we make the data available to our analyst in more of that raw state. So when they really do need to truly get into that weeds data, we don't run into that low traffic limitation.
There should be some more clarity around what makes a test significant. While this can be decided by the client themselves, some direction from the tool would be helpful.
Also, if there was an easier way to organize campaigns and search for them it would be helpful. Right now there is just a long list of campaigns and you have to rely on search to find a specific campaign. What if you don't know the name of the test?
New pricing models are very expensive compared to old pricing model, even though it includes several additional tools, most of which seem to be beneficial
Horrible support experience despite working with escalation teams to try and resolve
Several bugs in recent releases which remain unresolved for many months at a time
Once you get started with your testing program, you realize that it is necessary to continue. You must keep optimizing in order to remain a vital competitor in today's marketing world. Even if you're not using Test & Target or any other user experience testing software, you ought to be performing comparison tests on your own, simply by routing your audience to different experiences and quantifying the aggregate of the results.
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.
The recent UI update is a complete mess. It is difficult to navigate and find features that previously existed. The reactiveness of the page depending on window size is also ridiculous and it is absurd that depending on how large your window is, entire columns of functions will disappear with no indication that they are missing. The usability of the tool has fallen off a cliff.
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.
Overall, Adobe's servers seem responsive. Like any large-scale SAS provider, they can have occasional slowdowns where, I presume, a node is not available and other servers get bogged down with the user load. I have noticed this with both large and small data sets and reports.
On that note, Adobe Analytics can take a long time to run reports and pull various data points, depending on the period of time, number of metrics and segments applied. As you create reports, particularly in Workspace, the data are pulled in real-time while you're creating the report. This can often cause issues while trying to drag more metrics into the interface when certain elements of a table are grayed out because data is being pulled in.The more data points and segments involved, the longer it takes to update. When you look at larger windows of time, it takes even longer. If one were to compare to Google Analytics or one of the open source products like Piwik or Motomo, Adobe seems much slower. However, Adobe also supports far more variables than other web analytics products.
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.
On several occasions, we have had the need to ask for help from the Adobe Target support team, and I must say that they have provided us with an excellent experience, as they take care of solving the problems quickly and with high precision
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
The instructor that came to train us was awesome and this training was very useful. I would recommend it for anyone who is going to be using this software. I only mark it lower because it is an added expense to an already expensive product, and a lot of the training covered the "Target" portion of the software (which again, we didn't use)
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.
The training was very easy to understand, however it would have been more useful to my development team than me. It was also primarily over-the-phone, which is never as easy to follow as in-person. We ended up scheduling and paying for an in-person training session to supplement the online/phone training because it wasn't helpful enough.
It is a large effort to implement. Throwing a developer with zero experience with Adobe Analytics with no support is a REALLY BAD IDEA!!! Having experienced developers working as a team is crucial to a strong implementation. I say this because I have experienced both scenarios. I was the only developer on an implementation project and I had no experience with Adobe Analytics. As a result I made many architecturally bad decisions which lead to a rigid fragile implementation that eventually was scraped. It took some hard lessons to learn that Adobe Analytics was not as simple as their sales reps make it sound. Using the Adobe Dynamic Tag Manager made sequential implementations incredibly STRONG. Having a DTM to manage the code was a miracle and a life saver!!! If you plan on doing a big enterprise level implementation, please seriously consider using the Adobe Dynamic Tag Manager!!! it made code maintenance super slick and easy which is super important for a developer!!!
Implement using a global mBox on the page so you can change any and everything over the traditional method. Traditional method is good if you do not have technical web dev resources, do not know Javascript/jQuery, or you have money to blow on mBox calls. Global deployment reduces mBox calls and allows you to touch many parts of the page easily. A lot more customizable
Historically I've looked at a lot of different products. More recently I'd say Mamo and Google Analytics. Those are probably the two big ones that I've seen around, so yeah. It's more feature rich. It provides more dimensions, more breakdowns, and it also scales data better
For us, the decision was very straightforward. We chose to invest in the Adobe stack and utilize tools that are developed to integrate together and complement each other. Ex: Adobe Target 'A4T' integration within Adobe Analytics. Optimizely appears to be a great tool, but for us aligning with the Adobe suite, ensuring that future product enhancements and tools would work well together was a very important key factor in our decision
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.
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.
This is something we've been working to improve on, as far as how we're calculating and tracking this, but Target has had a substantial ROI on our business.
I will say specific to our efforts, we could have probably done similar work if not the same work using a different testing tool (Optimizely for example), but Target has been good for us.