Category: Adobe Customer Journey Analytics

Adobe Customer Journey Analytics’ Summarize Function is Awesome

Just last week, I was celebrating Customer Journey Analytics’ new “Next or Previous” and Math features in Derived Fields. While I originally intended to update that post once the new Summarize function is released, I found this feature so useful and versatile that I decided to write an entire post about it. If you want a longer introduction, feel free to check out last week’s post. If not, just enjoy this one! Summarize Derived Fields function The Summarize function does pretty much what the name says: It reduces a larger set of values, like a user’s entire website journey, into a (for now) single value. For example, a user may view a bunch of pages during their session but you might only be interested in the very first page. The Summarize function can return that for you with ease! Now, you may think that this example sounds somewhat familiar. And […]

Adobe Customer Journey Analytics keeps getting better with Derived Fields

You won’t be too surprised when I tell you: I’m a big fan of Adobe’s Customer Journey Analytics. Ever since I got the pleasure of using it for the first time four years ago, I am excited for every new release and its many new features. Sure, there are some things that Adobe Analytics is still better at, but the way CJA innovates on familiar concepts clearly shows how it will one day surpass AA’s features. The most recent release is no exception to that trend. As you know, Customer Journey Analytics works fundamentally different from Adobe Analytics. Where Adobe Analytics relies on the Visitor Profile to keep data about a Unique Visitor’s history and provide information like Entry Pages, Exit Pages, etc., Customer Journey Analytics does those things in real-time when we query the data. While this brings challenges for a couple of use cases (like deriving the Visit […]

Exploring Forms Tracking with Custom Data Types in Adobe Customer Journey Analytics

I can’t think of any analytics tool that got me quite as excited this year as Adobe’s Customer Journey Analytics, especially with the recent addition of Derived Fields. While there are some features still missing from Adobe Analytics, it should become more and more clear that CJA is already superior to the vast majority of the market. While I’ve already done an extensive series of posts on how to get started with CJA for a website and exploring the mobile AEP SDK, the new tool brings up many, many questions around setup, admin, and implementation. While the interface for business users is the familiar Analysis Workspace-democratization-paradise, all of the new and shiny capabilities invite us to re-think how we provide analytics capabilities to our companies. In this post, I want to take a look at an evergreen of digital analytics: Form tracking! Unperturbed by any recent trends, websites like to […]

Marketing Channels just got so much better in Adobe Customer Journey Analytics

Like it or not, but analyzing marketing performance is a key requirement for any digital analytics solution. Even solutions that try to find a niche by self-branding themselves as “product analytics” tools have some more-or-less developed feature to analyze marketing performance. In Adobe Analytics, we can use the Marketing Channels feature to analyze where the traffic on our website is coming from. So far, so neat! However, Marketing Channels in Adobe Analytics have one big drawback: They rely on comparatively simple Processing Rules. In those Processing Rules, we have to find a way to identify traffic for a given channel only by using what is available during data collection. Many customers use the Tracking Code dimension to achieve that, forcing them to use campaign codes like “searchads-123” to identify traffic from paid search ads. In the Processing Rules, they would then configure a rule like this to identify SEA traffic: […]

It’s finally time to migrate to Adobe Customer Journey Analytics

The market for digital analytics solutions is going through some big changes. Google continues to annoy customers by removing features from the universally hated GA4, which helps companies like Amplitude, Piano, or Piwik Pro to gain traction in a diversifying market. On the receiving end, vendors are eagerly trying to differentiate themselves by claiming that “product analytics” or “marketing analytics” could only really be done with their tools. Adobe has been quite busy defending their market leadership with their own new tool, Customer Journey Analytics. While I’ve been one of the very first customers of this next-gen Adobe Analytics, my general recommendation has been to stay with (or buy) Adobe Analytics instead, as CJA was still missing some important features for anyone wanting to replace AA. However, this recommendation has now finally changed. As you can see in my comparison post, my general recommendation is now to buy Customer Journey […]

Should you buy Adobe Analytics or Customer Journey Analytics for Web Analytics use cases today?

The market for web analytics tools is going through some big changes right now. On one hand, Google has officially announced to sunset Universal Analytics (also known as “the ‘good’ Google Analytics”) next year in favor of the universally hated GA 4. On the other hand, Adobe is heavily promoting their new tool Customer Journey Analytics, both to new and existing Adobe customers. There is no doubt that, at some unannounced point in the future, Customer Journey Analytics will become Adobe’s only analytics tool. However, there is one important detail about Customer Journey Analytics that we need to keep in mind: It is not a dedicated web analytics tool like good old Adobe Analytics. Customer Journey Analytics is built to handle data from all sources you can think of, not just websites and apps. Because of that, Adobe Analytics still has some unique features, like the Visitor Profile, that are […]

Cookie-less Server Side Tracking with Adobe Customer Journey Analytics

If there is one big hot topic in digital analytics right now (besides the unfortunate sunset of Google Analytics 3 and GDPR news) it quite possibly is the recent trend of what many call server side tracking. Currently, server side tracking is an obligatory agenda item at every analytics conference and virtually every vendor of analytics or tag management systems is working on a way to serve the rising demand. However, while there is a lot of talk around the topic, there is no shared definition in our industry of what server side tracking actually is. Jim Gordon has assembled a nice overview of what people might mean when they talk about any of the underlying concepts. In my personal experience, people usually refer to a form of server side tag management, often using Google’s server side tag manager, that still uses some logic in the client’s browser. Adobe has […]

Web Analytics with Adobe’s Customer Journey Analytics, Part 8: A new home

This post is the eight and last post of the eight-part-series Web Analytics with Adobe’s Customer Journey Analytics, showing how web sites can be analyzed better using Adobe’s next evolution of Adobe Analytics. In the previous post, we were creating the connection from Experience Platform to Customer Journey Analytics. In this post, we are going to take a look at our web analytics data and explore some use cases. Believe it or not, but this series of posts is almost finished! Starting with nothing, we have created a sophisticated schema for our data in Experience Platform, created a tracking implementation using the new Web SDK, enriched our data in Query Service, and pulled all that data into Customer Journey Analytics. If you have been following since the start of the series, I want to say: Thank you, hope you enjoyed the ride! Now it is time for the finale, where […]

Web Analytics with Adobe’s Customer Journey Analytics, Part 7: Customer Journey Analytics Backend Configuration

This post is the seventh post of the eight-part-series Web Analytics with Adobe’s Customer Journey Analytics, showing how web sites can be analyzed better using Adobe’s next evolution of Adobe Analytics. In the previous post, we were enriching our basic web analytics data with some advanced fields in Query Service. In this post, we are creating the connection from Customer Journey Analytics to Experience Platform. At this point in this series, we have a world-class dataset of web analytics data in Experience Platform, ready to be analyzed. I’m personally very proud of the things we were able to achieve in Query Service, especially with the pathing dimensions. With all of that, we have even more than what normal Adobe Analytics would give us! With all the data enriched, we now have only one step left before we can start analyzing our digital user’s behavior. First, we need to pull data […]

Web Analytics with Adobe’s Customer Journey Analytics, Part 6: Advanced Data Processing in Query Service

This post is the sixth post of the eight-part-series Web Analytics with Adobe’s Customer Journey Analytics, showing how web sites can be analyzed better using Adobe’s next evolution of Adobe Analytics. In the previous post, we took a look at processing some basic data we need for our web analytics use case utilizing Query Service in Experience Platform. In this post, we are creating some advanced fields to our data in Query Service. I think it’s fair to say that even with just the information from the previous part, we could have a very useful web analytics tool already. But if you know me, you know that I like to take things to the next level wherever I can, especially if it involves writing code. And is SQL not some sort of code too? Entry and exit page were a nice start last time, but we have some fields still […]

Web Analytics with Adobe’s Customer Journey Analytics, Part 5: Basic Data Processing in Query Service

This post is the fifth post of the eight-part-series Web Analytics with Adobe’s Customer Journey Analytics, showing how web sites can be analyzed better using Adobe’s next evolution of Adobe Analytics. In the previous post, we took a look at doing the implementation using Adobe Launch, the Adobe Web SDK, and Client Data Layer. In this post, we are going to processing some basic data we need for our web analytics use case utilizing Query Service in Experience Platform. This series of posts is coming along quite nicely. If you followed all the previous posts until now, you will now have a functioning Web SDK implementation that tracks your data into Experience Platform following the Experience Data Schema we have tailor-made for our use case. Nice! Now we are ready to feed our data into Customer Journey Analytics, right? Well, we could. If we are just interested in the plain […]

Web Analytics with Adobe’s Customer Journey Analytics, Part 4: Capturing Data with Web SDK (Alloy)

This post is the fourth post of the eight-part-series Web Analytics with Adobe’s Customer Journey Analytics, showing how web sites can be analyzed better using Adobe’s next evolution of Adobe Analytics. In the previous post, we took a look at our business questions and how we can structure our data most effectively. In this post, we are doing the actual implementation using Adobe Launch, the Adobe Web SDK, and Client Data Layer. On our way to creating a full-scope, front-to-back implementation of Customer Journey Analytics to track a web site, we are now ready to think about our actual implementation. Since we have the data structure in place and already have an awesome Experience Event Schema, we just need some actual data. The logical choice to feed data to the Adobe stack is, of course, by utilizing their client-side tools as well. Specifically, we are going to use Adobe Launch […]

Web Analytics with Adobe’s Customer Journey Analytics, Part 3: Data Structure in Experience Platform

This post is the third post of the eight-part-series Web Analytics with Adobe’s Customer Journey Analytics, showing how web sites can be analyzed better using Adobe’s next evolution of Adobe Analytics. In the previous post, we took a look at the different possible solution architectures we can use to bring data into Customer Journey Analytics and decided on the best one. In this post, we will take a look at our actual business questions and how we can structure our data most effectively. From the last post we already know that we want to track data using only the new Adobe Web SDK going forward. To make that work, we need to create a schema in Experience Platform first, which defines the structure of the data that we want to capture. While some people (sometimes me included) see schema management as one of the more tedious tasks in Platform, I […]

Web Analytics with Adobe’s Customer Journey Analytics, Part 2: System Architecture in Experience Platform

This post is the second post of the eight-part-series Web Analytics with Adobe’s Customer Journey Analytics, showing how web sites can be analyzed better using Adobe’s next evolution of Adobe Analytics. In the previous post, we discussed the motivation and scope of this project and why, eventually, existing Adobe Analytics customers will start moving to Adobe’s Customer Journey Analytics. In this post, we will take a look at the different possible solution designs we can use to bring data into Customer Journey Analytics and decide on the best one. Adobe’s Customer Journey Analytics is built on Adobe’s brand new Experience Platform. With that, it is very flexible in terms of how data can be brought into the tool. Depending on the setup it may seem very easy to bring data in quickly. However, all that flexibility also means we have many ways to deviate from the ideal path, so we […]

Web Analytics with Adobe’s Customer Journey Analytics, Part 1: Goodbye Adobe Analytics, my Old Friend

This post is the first post of the eight-part-series Web Analytics with Adobe’s Customer Journey Analytics, showing how web sites can be analyzed better using Adobe’s next evolution of Adobe Analytics. In this part, we discuss the motivation and scope of this project and why, eventually, existing Adobe Analytics and new customers will start moving to Adobe’s Customer Journey Analytics. If you found this article, chances are high you work in or adjacent to the field of digital analytics or web analytics. It doesn’t really matter if you are an existing Adobe Analytics user, on the Google stack, or just looking for your very first web analytics tool. If you have been following the trends and discussions in our industry in the recent time, you will likely already have caught on the massive changes that both our industry and Adobe’s products go through. With changes to privacy requirements and cookie […]

Calculated Metrics in Segments are finally here… Sort of, in Adobe’s Customer Journey Analytics

If you have been following this blog for a while (thank you!), it shouldn’t surprise you if I claim: Adobe Analytics is the best web analytics solution available today. But if we’re honest, it has been around for a long time, which has been leading to a situation very familiar to anyone working in the tech industry: The things that we build today might limit us in the future when new technology becomes available. This is also true for Adobe Analytics. When Adobe Analytics was created, it was necessary to build features like the Visitor Profile or Props in a certain way with what was available at that time. Back then, it was necessary to store Visitor Profile information in a database and add it to the data as it was processed (something I also used in a previous series of posts). The database engine on top of that data […]

Privacy-centered Analytics with Matomo and Adobe’s Customer Journey Analytics

Legal Disclaimer: Data Privacy is a diverse and ever-changing topic. This makes it nearly impossible to give reliable recommendations to a broad audience. Please consult your company’s legal department on whether those ideas described here are feasible under your jurisdiction. If there has been one predominant topic in the web analytics space for the last couple of years, it surely is data privacy. GDPR is a thing in Europa, COPPA in the US, ITP on planet Apple, and cookie consent banners on every website. Conducting a safe data collection practice as a global business has become more and more challenging, pushing businesses to be more and more careful. Because of this landscape, a lot of businesses are looking for a “bullet-proof” way to analyze website users’s behavior. While Google Analytics is a data privacy nightmare, tools like Piwik Matomo try to justify their existence by claiming to be more privacy […]