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
React (React.js)
Score 8.8 out of 10
N/A
React or React.js is a JavaScript library for building user interfaces. React enables users to create interactive UIs.
Honestly, because Adobe Analytics is so customizable, I found that it is very well-suited for almost any type of web digital experience tracking of behavioral analytics. It has a very robust mech architecture for any type of e-commerce platform. But it is extensible and is easily adaptable to other circumstances. For example, in our university situation, we've been able to use it for student portal experience tracking, how well they are interacting, interfacing with our internal sites, and how well they are working with our task submission processes. But it does a great job of managing all aspects of the key journeys, especially from a marketing perspective. So while it might not be as out-of-the-box for some of those other alternative use cases outside of marketing, it's extensible and customizable enough that it's worked really well and met our needs.
React is a JavaScript user interface construction library that works well for:
Developing web apps with dynamic and complicated user interfaces.
creating reusable UI elements that may be used in other applications.
creating single-page applications with dynamic content updates that don't require a page reload.
The Virtual DOM's effective updating mechanism allows it to handle large volumes of data updates.
React, on the other hand, might be less suitable for:
Websites that are simple, stagnant, and have no interaction. Other libraries or simple HTML, CSS, and JavaScript may be a better fit in such circumstances.
Web sockets may be a better choice for applications that need real-time updates, such as chat or gaming apps.
When creating mobile apps, React Native is a better option.
Server side rendering only, as React is designed to run on the client side.
Within my role of advertising, I can come in, and I can see I'm paying for visitors, paying to drive people to the website. So I can see the differences in my different traffic sources, whether that's a Google search campaign or a Facebook social campaign. I can measure the quality of that traffic and see what they're doing, whether they're bouncing right away and leaving the website, or spending more or less time on the website. And whether they're taking the actions. My ad campaign is focused on filling out forms, and ultimately, that's it. Just measure and see if my campaigns are successful or not.
React is fantastic for building performant user interfaces. Our web app is snappy and great for our customers.
React has the philosophy of doing one thing and doing it well which is the view layer of the application. This makes it incredibly intuitive and flexible for developers to use.
React has lead the way in being able to write modular and structured code. It is a drastic improvement since the days of spaghetti jQuery code.
React has an unmatched community. The amount of tools and libraries available is fantastic, and there plenty of solutions available online for common problems.
I think the biggest room for improvement is performance. When I go in certain times of the day or for certain clients, it's slow and it won't load the reports that I need. And as a result, needing to answer a question where you normally have the expectation of it being a near real-time answer that you get when you have to wait for reports to load or you have to wait because the reports can't load at all. It's a really unfortunate thing. It's a big problem actually. So I'd say that's one area of improvement. It's just improving the performance of the reports so that they'll load consistently all the time quickly and effectively.
Debugging React is challenging. Bugs in react code generate stack traces internal to React and it is often totally unclear how it relates to the code you actually wrote.
Relating your React elements to corresponding DOM elements is difficult. The intentional separation of virtual and actual DOM also makes it difficult to map the elements to the structures in the DOM. This is partially ameliorated by the use of the React dev tool, which provides a DOM-like view of the React elements, but the tool still does not provide a direct correspondence with the DOM that is often necessary to figure out why something isn't right.
Because JSX is React-specific and not a language feature, a special compilation process is necessary to convert JSX code to normal JS. Coming from a C++ background, compiling things doesn't bother me, but many JS developers are used to a less structured development.
We need it to discover threats long before they become a loophole in the security ecosystem. Also, it is very much compliant with customer standards and expectations. It provides marketing intelligence through in-depth analysis. Overall, a very good product to gain customer attention and thereby improve market
It is necessary to have a minimum knowledge on tracking tools so you can use the tool on full performance. It is not an introduction tool, so please bear that in mind. Once you got the knowledge you just need a small training on how to create your custom reports, where to find the components you need and how to add them to your dashboard. Then you share your report or create a rule for periodic sharing and it's done. Finally, if you have a lot of data stored the tool might be a little slower but that's ok.
React is just a bit of a different animal. I was avoiding it for the longest time. I thought for sure I would land on Vue or something else with a more approachable and familiar appearance. But after taking an online course in React, I started realize what people were raving about (and complaining about) and decided to implement it at our office for one of our products.
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
Support for Adobe Analytics is ok, it used to be worse years ago. Now, the technology team at Adobe is way more knowledgeable on the product itself as well as the implementation. They also study your custom implementation and have good knowledge of where your company stands. Dedicated support is something worth considering.
Since it's open-source and very popular, the community support for React and related tools and libraries is excellent. There are a lot of people using the same tools, and so issues tend to get fixed quickly and "recipes" are easy to come by. And since it's backed by Facebook, they have a dedicated engineering team working on the progression of React.
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.
We evaluated and we currently use Mixpanel and we have Google Analytics on a couple of our properties. And honestly, once you get the hang of the Adobe Analytics workspace, the other products really don't stack up against it because the segmentation and the ability to create reports pretty rapidly are invaluable.
While this is a widely contested debate with various blog posts and benchmarks all over the place, its really a personal choice to determine what works for the team. Coming from a Angular 1.x background, I decided to try a new framework when Angular 2.x was announced and at that time React is gaining popularity and Vue hasn't taken off yet. Compared to Angular 1.x and Vue (hybrid of React and Angular) that split the logic from the html templates, I loved the way React breaks code into components using the jsx syntax. In my mind, this allows for cleaner components and easier maintenance
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
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.
