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
Firebase
Score 8.6 out of 10
N/A
Google offers the Firebase suite of application development tools, available free or at cost for higher degree of usages, priced flexibly accorded to features needed. The suite includes A/B testing and Crashlytics, Cloud Messaging (FCM) and in-app messaging, cloud storage and NoSQL storage (Cloud Firestore and Firestore Realtime Database), and other features supporting developers with flexible mobile application development.
Firebase is a much more comprehensive tool. While Fabric only had user traffic and trends data, it did not have the user communication set of tools. While CleverTap has CRM tools, it does not have tools for developers and product teams. While Adobe Analytics is good with …
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.
Firebase should be your first choice if your platform is mobile first. Firebase's mobile platform support for client-side applications is second to none, and I cannot think of a comparable cross-platform toolkit. Firebase also integrates well with your server-side solution, meaning that you can plug Firebase into your existing app architecture with minimal effort.
Firebase lags behind on the desktop, however. Although macOS support is rapidly catching up, full Windows support is a glaring omission for most Firebase features. This means that if your platform targets Windows, you will need to implement the client functionality manually using Firebase's web APIs and wrappers, or look for another solution.
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.
Analytics wise, retention is extremely important to our app, therefore we take advantage of the cohort analysis to see the impact of our middle funnel (retargeting, push, email) efforts affect the percent of users that come back into the app. Firebase allows us to easily segment these this data and look at a running average based on certain dates.
When it comes to any mobile app, a deep linking strategy is essential to any apps success. With Firebase's Dynamic Links, we are able to share dynamic links (recognize user device) that are able to redirect to in-app content. These deep links allow users to share other deep-linked content with friends, that also have link preview assets.
Firebase allows users to effectively track events, funnels, and MAUs. With this simple event tracking feature, users can put organize these events into funnels of their main user flows (e.g., checkout flows, onboarding flows, etc.), and subsequently be able to understand where the drop-off is in the funnel and then prioritize areas of the funnel to fix. Also, MAU is important to be able to tell if you are bringing in new users and what's the active volume for each platform (Android, iOS).
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.
Attribution and specifically multi-touch attribution could be more robust such as Branch or Appsflyer but understand this isn't Firebases bread and butter.
More parameters. Firebase allows you to track tons of events (believe it's up to 50 or so) but the parameters of the events it only allows you to track 5 which is so messily and unbelievable. So you're able to get good high-level data but if you want to get granular with the events and actions are taken on your app to get real data insight you either have to go with a paid data analytics platform or bring on someone that's an expert in SQL to go through Big Query.
City-specific data instead of just country-specific data would have been a huge plus as well.
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.
It is simple to use overall, the console's main menu is divided into Develop, Quality, Analytics and Grow - which have further subdivisions by their set of features and tools. Develop and Quality are relevant for product and tech. Analytics is relevant for product, analytics and Grow is relevant for marketing. This makes the overall use very easy.
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.
Our analytics folks handled the majority of the communication when it came to customer service, but as far as I was aware, the support we got was pretty good. When we had an issue, we were able to reach out and get support in a timely fashion. Firebase was easy to reach and reasonably available to assist when needed.
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.
Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted database. This simplicity has allowed us to try features that we might not have based on the amount of work they required in the past.
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.
Makes building real-time interfaces easy to do at scale with no backend involvement.
Very low pricing for small companies and green-fields projects.
Lack of support for more complicated queries needs to be managed by users and often forces strange architecture choices for data to enable it to be easily accessed.
