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
Amazon CloudWatch
Score 8.5 out of 10
N/A
Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.
$0
per canary run
Pricing
Adobe Analytics
Amazon CloudWatch
Editions & Modules
No answers on this topic
Canaries
$0.0012
per canary run
Logs - Analyze (Logs Insights queries)
$0.005
per GB of data scanned
Over 1,000,000 Metrics
$0.02
per month
Contributor Insights - Matched Log Events
$0.02
per month per one million log events that match the rule
Logs - Store (Archival)
$0.03
per GB
Next 750,000 Metrics
$0.05
per month
Next 240,000 Metrics
$0.10
per month
Alarm - Standard Resolution (60 Sec)
$0.10
per month per alarm metric
First 10,000 Metrics
$0.30
per month
Alarm - High Resolution (10 Sec)
$0.30
per month per alarm metric
Alarm - Composite
$0.50
per month per alarm
Logs - Collect (Data Ingestion)
$0.50
per GB
Contributor Insights
$0.50
per month per rule
Events - Custom
$1.00
per million events
Events - Cross-account
$1.00
per million events
CloudWatch RUM
$1
per 100k events
Dashboard
$3.00
per month per dashboard
CloudWatch Evidently - Events
$5
per 1 million events
CloudWatch Evidently - Analysis Units
$7.50
per 1 million analysis units
Offerings
Pricing Offerings
Adobe Analytics
Amazon CloudWatch
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
With Amazon CloudWatch, there is no up-front commitment or minimum fee; you simply pay for what you use. You will be charged at the end of the month for your usage.
Adobe Analytics is better than some other tools as it feels better set up for actual "analysis", rather than simply "reporting". The power of Workspace allows you to drag 'n' drop at ease which makes you are far more in control of your own analysis/discovery/exploration. However, regards the final reports and dashboards' look 'n' feel the Workspace PDF output is lacking visually compared to other products like Google's Looker. To engage with less technical end users sometimes Looker feels the better, more polished option.
Cloud watch is great and essential if you decide to invest in AWS and have any need to monitor the health of all aspects of your VPC resources, or at the organizational level (multiple accounts). Another benefit of the service is constant upgrades at no additional costs; the software evolves to develop modules and interface improvements. For first-time users in AWS, this is going to take a bit to understand, so the learning curve to this metrics environment can seem overwhelming at first glance/use.
They've been really an industry standard tool in analytics for a long, long time. They've got the trusted brand and the reputation, a wonderful community behind it. It is always nice, having that level of support where you can meet other practitioners. It's a great benefit because I can meet other people who have already pushed the tool a lot farther than I have. And it's a great place to get ideas in that way. We came from a world where we were running on a homegrown system that we'd use to do click tracking. You get some advantages on that of the customization, but losing out on community of support was one of the big reasons why we decided to move beyond that and implement Adobe Analytics instead.
It provides lot many out of the box dashboard to observe the health and usage of your cloud deployments. Few examples are CPU usage, Disk read/write, Network in/out etc.
It is possible to stream CloudWatch log data to Amazon Elasticsearch to process them almost real time.
If you have setup your code pipeline and wants to see the status, CloudWatch really helps. It can trigger lambda function when certain cloudWatch event happens and lambda can store the data to S3 or Athena which Quicksight can represent.
Most of the problems that Adobe Analytics as of now is having, it is getting addressed in a newer tool called Web Desk DK from implementation. They are already addressing that issue with the new tool and also the time data with the customer general analytics. So there is something not in workspace analysis and this is what they're addressing in customer general analytics. Which is good.
Memory metrics on EC2 are not available on CloudWatch. Depending on workloads if we need visibility on memory metrics we use Solarwinds Orion with the agent installed. For scalable workloads, this involves customization of images being used.
Visualization out of the box. But this can easily be addressed with other solutions such as Grafana.
By design, this is only used for AWS workloads so depending on your environment cannot be used as an all in one solution for your monitoring.
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.
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.
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
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.
Support is effective, and we were able to get any problems that we couldn't get solved through community discussion forums solved for us by the AWS support team. For example, we were assisted in one instance where we were not sure about the best metrics to use in order to optimize an auto-scaling group on EC2. The support team was able to look at our metrics and give a useful recommendation on which metrics to use.
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 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.
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 think Adobe's been around longer as a product but Tealium, from when I did research, it has auto-tagging. So one of my biggest pet peeves is when I'm rolling out new features, and whether it's an app or a website, is that I have to go speak with our metrics team or tagging team and we have to come up with these different strategies. Okay, how are we gonna tag it? What are we going to name it? It just seems like a lot of wasted time in my opinion. I want to track everything. I want to know every single thing these people are doing. We shouldn't have to have this conversation if we tag this, you might not have time to tag this right away for MVP. It's like that to me right now. That shouldn't even be a conversation. I should be able to release a feature, I should be able to just automatically go pull reports on that. And just figure out exactly what they were doing.
I believe that CloudWatch is a better solution to use with AWS services and resources in terms of cost and ease of integration with AWS infrastructure services. But keep in mind that Elasticsearch is better at aggregating application-level metrics. We chose CloudWatch because of its capabilities to integrate and monitor AWS services in almost real-time.
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.
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
I like to think it's positive. It's a very steep learning curve, so we do face a lot of challenges with adoption inside of the companies. My team and I evangelize this and also who's in charge of data and advanced analytics, but it's very hard to leverage that with typical business analysis people. These are people who live their life in Excel and SQL and Power BI. They just use this very occasionally and by only looking at that sort of aggregate data, they miss out on behavior and what actually happens in execution. And because it's such a steep learning curve, we do have a challenge pushing it in there.
We were able to set up log streaming, retention, and simple downtime alerts within a few hours, having no prior experience with CloudWatch, freeing up our engineers to focus on more important business goals.
CloudWatch log groups have made it relatively easy to detect and diagnose issues in production by allowing us to aggregate logs across servers, correlate failures, isolate misbehaving servers, etc. Thanks to CloudWatch, we are generally able to identify, understand and mitigate most production fires within 10-15 minutes.
Choosing CloudWatch to manage log aggregation has saved us quite a bit of time and money over the past year. Generally, 3rd-party log aggregation solutions tend to get quite expensive unless you self-host, in which case you typically need to spend a fair amount of time setting up, maintaining, and monitoring these services.
