Adobe Analytics

Hello All,I'm currently working as Adobe Analytics Architect in the banking domain using Tealium iQ for tag management. I have dealt with challenges like login flow tracking, secure data layer usage and mobile app analyticsCurious to hear how other handle:Tracking insecure/authenticated environmentsAvoiding PII data collectionsAligning mobile + web analytics strategiesLet's share ideas!

Originally airing on May 28, 2025, our experts discussed the transformative world of content analytics, powered by Adobe's cutting-edge AI technology. Content Analytics revolutionizes the way you measure, understand, and optimize content performance.  You can view the replay from the episode page and find additional recourse commented on during the live event: Content Analytics - Optimize performance with AI insights Use this thread to ask our experts additional questions related to the Experience League LIVE session. Thanks and we hope to hear from you!

  Introduction When working with Customer Journey Analytics (CJA), encountering "No Value" entries in reports and dashboards prompts important questions about data quality, collection methods, and reporting accuracy. These instances need careful monitoring as they may reveal hidden gaps in data collection. The main challenge lies in distinguishing between two scenarios: when "No Value" entries need investigation by data source providers, and when they simply reflect the natural flow of data into CJA. Understanding this distinction is crucial for maintaining efficient analytics operations. This guide will help you make informed decisions about "No Value" appearances in your CJA implementation. Understanding "No Value" in CJA "No Value" appears in CJA reports when a dimension has no corresponding metric value during the reporting period, regardless of the report type.  Seeing "No Value" in your reports isn't always a sign of an error or data collection issue. It's often an e

Introduction Mobile scorecards in Adobe Customer Journey Analytics (CJA) offer a streamlined way to monitor key performance metrics on mobile devices, giving stakeholders access to data insights anywhere. These mobile-optimized dashboards let users track, analyze, and act on key performance indicators while on the move. This guide explores how to create effective mobile scorecards for CJA, share them with stakeholders, and maximize their value within the CJA solution ecosystem. CJA mobile scorecards display data through simple, mobile-optimized tiles. Users access key metrics and insights via the Adobe Analytics mobile app, which serves both CJA and Adobe Analytics (iOS link, Android link). The scorecards simplify complex data into digestible formats, displaying key performance indicators and strategic metrics in a mobile-friendly interface. They're designed specifically for executives, managers, and business users who need quick, on-the-go access to key performance metrics data. B

  Introduction Event Depth is a new standard dimension component introduced to Customer Journey Analytics (CJA) in May 2025. It gives CJA practitioners new ways to measure and better understand how events are positioned within bounded experience sessions. The Event Depth dimension enables detailed tracking and analysis of where specific events occur in the sequential flow of user interactions within a session. By revealing the precise positioning of events within the sequence of customer event interactions, this dimension empowers analysts to make clear distinctions between sessions demonstrating high levels of engagement and those showing minimal interaction patterns against collected events activity. Through this enhanced visibility into user behavior, analysts can effectively identify opportunities for optimization and leverage data-informed insights to make strategic improvements to the overall customer journey. What is Event Depth? Event Depth (component ID= adobe_event_de

Watch now Join Adobe CJA champions and Experience Maker award winners Katie Klein and Lokesh Alluri as they dive deep into customer journey analytics (CJA) and explore its transformative potential for your business.What you'll learn:Understanding CJA: Learn what CJA is and how it differs from AA.Strategic framework: Discover the steps for data ingestion, enablement, and adoption to maximize ROI.Web SDK insights: Find out if Web SDK is necessary for CJA and explore alternatives.CJA vs. AA: Understand the relationship between CJA and AA, and explore options for integration.Profile data importance: Learn about the significance of profile data and how to overcome related challenges.Implementation best practices: Get tips on use case-driven approaches, scalable data ingestion, and establishing governance practices.Examples of CJA capabilities: See real-world examples of what CJA can achieve.What if I don’t have CJA? No worries! Whether you're interested in what CJA implementation looks

If you are planning for Edge Data Collection and want to migrate existing Experience Cloud solutions to Web SDK, you have a few options when it comes to structuring the data you send. As discussed in a previous blog, data you send to Adobe Experience Platform (AEP) must be sent as XDM and aligned with a dedicated XDM schema. But what if you want to send data to Analytics or Target, but NOT to AEP? For that, you can use the data object, a sibling to XDM in your network call payloads. As described below, the data object has properties that allow for a smooth migration of existing Experience Cloud solutions without requiring that it be associated with an XDM schema.  The data object can be passed with the Web SDK sendEvent and maps data directly to Adobe Experience Cloud services. This allows you to continue sending Adobe Analytics, Target, and Audience Manager parameters with their original values, maintaining continuity during migration. It also eliminates the need for an XDM schem

I'm looking for an Adobe Analytics UTM builder (similar to the Google Analytics campaign builders) that will enable me to control naming conventions, store my UTM links built, and help me with insights. I've set up my classifications but too many people are writing links differently and it's creating a mess.Is there a proven / available UTM form that I can use to deploy proper link-building operations across my company (something better than Google's URL builder which has no naming convention controls)? We've noticed that we're only tracking about 30% of our marketing spend effectively through Adobe Analytics and this is probably the biggest reason why (too many agencies, marketers, and vendors building links for GA when it should be Adobe structure).

  Introduction Adobe Customer Journey Analytics (CJA) offers three standard visualization methods designed to analyze and understand customer pathways across touchpoints. These visualization options - Journey Canvas, Fallout, and Flow visualizations - each bring their own specialized capabilities to the analysis process. Journey Canvas provides a flexible and customizable interface for mapping complex customer interactions, while the Fallout visualization excels at tracking sequential progression through predefined touchpoints, and the Flow visualization enables exploration of non-linear customer movement patterns. Each of these visualization methods has been crafted to serve specific analytical needs, providing unique features and functionalities that help organizations gain deeper insights into customer behavior patterns and journey progressions. Comparing Customer Journey Visualization Methods To better understand how these powerful visualization methods complement each othe

I wanted to share a new small tool I developed for Adobe Analytics users around an efficient way to extract the Pagename variables. Its great in instances where a datalayer is used and I hope will save people some time and effort in their day to day work! It also can extract other datalayer variables so I hope you find it useful! This is ideally suited when tasked at finding info on multiple URLs all at once!Link to tool:https://deploi.ca/tools/adobeLink to blog:https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-blogs/new-tool-to-assist-adobe-analytics-professionals-the-adobe/ba-p/744433 I hope you enjoy and find the tool useful!  

In previous posts, we covered migrating Adobe Analytics and Target to Edge Data Collection using the data object. Migrating Adobe Audience Manager (AAM) to Web SDK ensures you maintain alignment between audience management and your updated Analytics and Target set ups. In this blog, we’ll discuss some important considerations to keep in mind when migrating AAM to Web SDK. You can find a complete Web SDK migration tutorial here. Comparing Web SDK and Server-Side Forwarding First, let's take a look at AAM with server-side forwarding compared to Web SDK. Most legacy AAM implementations leverage Adobe Analytics data by enabling server-side forwarding (SSF) through the Analytics report suite. When migrating to Web SDK, AAM must be enabled in the datastream. Enabling the AAM service allows data to be sent to AAM and services such as ID syncs, cookie destinations, or URL destinations, to be returned back to the page on the Web SDK interact call response. While SSF is still available

So my first tool I would like to share is what I call the Adobe Analytics pagename extractor. This is a quick and easy way for a user to get the pagename variable when using a datalayer based implementation method. The main thing here where its really efficient is when having many multiple URLs you need to get the pagename for each.  Here is a link: https://deploi.ca/tools/adobe A quick user guide:- In top section enter the pagename datalayer object you want to find.- Then in field below enter all the URLs(max 500 at a time).- A progress list will appear and once completed a .csv text file is generated.- If results are good then just click and download the file.(if tweaks required just update datalayer object and re-run.)   This also can work with other datalayer objects so I encourage you to try and experiment! Please also feel free to contact me if any issues or refinements you feel can help to make this tool even better!   Thanks and I hope this helps you!

Use this thread to ask any questions related to the Freeform Tables, the Foundation of Analysis course/playlist on Experience League. Experts are monitoring this thread to ensure your questions are answered.

Introduction Are you looking to enhance your understanding and broaden your knowledge of Adobe Customer Journey Analytics (CJA)? In this blog post, updated as of September 2023, I will guide you on a comprehensive learning journey to introduce you to Customer Journey Analytics (CJA). My goal is to familiarize you with the platform's features and capabilities and provide valuable insights and knowledge to help you fully utilize this powerful tool. To support your learning experience, I have curated a variety of essential resources, educational materials, and diverse learning content. These resources will serve as your guide, helping you develop a deeper understanding and mastery of the CJA platform. With access to these resources, you will gain the confidence and proficiency needed to become a skilled user of CJA. The guide is divided into two main sections: CJA Learning Path Approach: This section provides a step-by-step guide on how to approach the learning path for CJA. It include

Mobile Core is one of the fundamental extensions in a Mobile SDK implementation and is pre-configured when creating a new mobile tags property. Within Mobile Core lives the Lifecycle extension enabling collection of installs, upgrades, launches, and crashes, along with app-centric dimensions including the app ID and device information. This mobile reporting can be used to understand your mobile app usage, popularity in various operating systems, version adoption, and crash rates. This post will explain the significance of how Lifecycle metrics, when implemented properly, gives valuable insight into app usage, and potential pitfalls that can wreak havoc in your reporting.   Installing Lifecycle Metrics The first step of implementing Lifecycle metrics is to add and import the necessary extensions for calling the Lifecycle APIs, integrating lifecycle start and pause calls into the data collection functionality. Start with the Lifecycle API within the Mobile Core extension.

Hi everyone! Discover a goldmine of Analytics insights and resources at Adobe Summit 2025 with our comprehensive guide to all Adobe Analytics sessions and labs. Whether you're a seasoned user or exploring Adobe Analytics, this post is your key to navigating Summit's content.   Session/Labs Speakers Date & Time Solutions Amplify Your Customer Analytics: From Chess with Pawns to Power Plays [S112] Jordan Ison, Managing Principal, Adobe Tuesday, Mar 18 | 1:00 PM - 2:00 PM PDT  Adobe Analytics, Adobe Customer Journey Analytics Adobe Analytics: Using Advanced Metrics to Level Up Your Reporting [OS115] Mandy George, Sr. eCommerce Analyst, Staples Canada Tuesday, Mar 18 | 2:00 PM - 2:30 PM PDT Adobe Analytics Building Personalized Connections at Scale: T-Mobile’s Adobe Journey [S733] T-Mobile Tuesday, Mar 18 | 2:30 PM - 3:30 PM PDT Adobe Analytics, Adobe Audience Manager, Adobe Campaign, Adobe Target, Adobe Real-Time CDP Collaboration, Adobe Experien

The Adobe Digital Experience Certification Program is offering a new certification: Adobe Customer Journey Analytics Developer Professional. If you have 3-6 months' experience with Adobe Customer Journey Analytics as a developer, this new professional-level certification is a great opportunity to demonstrate the knowledge and value you bring to your role. What abilities are candidates expected to have? Critically analyze data to identify anomalies in the data ingestion process (troubleshooting) U/A Analyze data prior to ingestion into CJA Differentiate between dimensions vs metrics Create calculated metrics or filters using data from multiple data sources Troubleshoot defects in data quality Configure dimensions and metrics in data view for reporting Retrieve the required dimensions and metrics on the business questions Demonstrate proficiency in specific semantics and taxonomy of CJA: Data Views, etc Data validation using query services Derived fields Configuration of connection and

Introduction The Journey Canvas visualization in Adobe Customer Journey Analytics (CJA) helps analysts map and understand how users move through different touchpoints in their journey. It allows dynamic exploration of customer behavior patterns, interaction sequences, and engagement flows across channels and platforms. In this blog post, we'll explore strategies for using this visualization to gain meaningful insights into your customers' journeys. Think of Journey Canvas as a GPS for your customers' experience. Just as GPS tracks routes from start to finish, Journey Canvas shows how customers navigate through your touchpoints. The tool connects various touchpoints (called nodes) along the customer's path, like pins on a map. You can spot popular routes, identify where users leave, and discover which paths lead to successful outcomes like purchases. These insights help businesses improve their customer experiences and boost customer satisfaction. Similar to how a traffic analyst stu

Do you know how sequential segmentation works in Adobe Analytics (AA) and in Customer Journey Analytics (CJA)? Not something basic (left) but something more interesting (right). Do you know what happens in this segment using Only After Sequence, plus Exclude, with multiple checkpoints, out-of-order container levels, and an After modifier? Do you know why this is valuable? That sample belongs to a use case to explore a visitor’s next visit after some key event, like an application submission. It returns exactly one visit for everyone who has applied - their next, consecutive visit. It works for the whole dataset, though qualified visitors applied on different days and engaged again at completely different times! There is so much I want to tell you and unlock for you regarding sequential segmentation in AA and CJA! This is the first post of my series Mastering Sequential Logic in Adobe Analytics and Customer Journey Analytics. I’ve specialized in this subject for many years at Adobe. My

Going back to what I said in my first post of this series, I'm a big fan of Web SDK but 'the elephant in the room' is that Web SDK was not primarily designed for Adobe Analytics.  This means there are a few unexpected things that can cause you to slip up.  I'm here to help you avoid those banana peels! This article is going to cover six potential issues relating to: Automated Click Data Collection using Adobe Target with Adobe Analytics Market Channels on Single Page Application (SPA) Websites Automated Click Data Collection As an Adobe Analytics expert you are probably used to your Adobe Analytics implementation automatically tracking Exit Links and Download Links.  Within the Web SDK Extension you can enable 'Click Data Collection' and on first glance this appears to be the same capability. It is true that 'Click Data Collection' provides automatic Exit Link and Download Link tracking. However, there are some big differences that you need to be aware of! Banana Peel

Introduction Adobe Customer Journey Analytics (CJA) offers numerous advancements, providing a more comprehensive and nuanced approach than standalone web and mobile analytics point-solutions. While conventional analytics tools typically follow a standardized, defined path to implementation and value realization, CJA necessitates a more strategic, purpose-driven methodology. This shift in approach is crucial for organizations to fully harness the power of CJA and extract meaningful insights from their data. CJA's implementation requires a defined use case-oriented strategy, demanding a deeper level of organizational introspection and planning. This blog post delves into the reasons why organizations need to adopt a more reflective and targeted approach when implementing CJA. We'll explore how this shift in perspective unlocks CJA's full potential, allowing organizations to gain a complete view of customer journeys across all touchpoints, platforms, and channels. By examining the uniqu

By: Luc Forgeron & Prachi Jain The Landscape  You love your Mobile Adobe Analytics (AA) implementation! You have worked hard to get your app data to match that of your web properties. You are enjoying the fruits of your labor in deriving key insights into your digital business and understanding how your customers use your apps. Now you need to activate upon this data in a platform setting to satisfy your “personalization-at-scale” objectives, so what do you do next? In other words, if the "what" that you collect from your mobile Adobe Analytics implementation is in a great spot, but you are not sure “how” to get that data into Platform, this is the blog for you.   Edge Data Collection via the Web SDK or AEP Mobile SDK is the backbone, heart, and future of the new Adobe ecosystem for streaming data. While many organizations have already migrated their web analytics to AEP Web SDK, pivoting to a new native application data architecture is an important next step to

By @amandadeasy  and @chrismdavis  Migrating Adobe Analytics and Target implementations to Edge Data Collection simultaneously is key to streamlining your setup and ensuring consistency across your Experience Cloud solutions. In previous blogs, we discussed the value of using the data object when implementing Edge Data Collection for Experience Cloud solutions, including Adobe Analytics. In this post, we’ll dive into using the data object to migrate mbox parameters for Adobe Target. For a complete step-by-step guide, check out this Web SDK migration tutorial for Target.  Recall that the data object allows you to implement Web SDK without using an XDM schema. For Target, this approach also provides a flexible way to configure and pass mbox parameters without additional mapping, making implementation and validation even easier!  Creating the Data Object  Before you begin, ensure that your datastream is enabled for Target. If you haven’t already set

Hi Team, Recently I have faced a issue regarding cross domain tracking when user click on login which is added as button without anchor tag href.  I have implemented appendVisitorIDsTo method and it will works fine when you link is having href but when user click on button which will not have anchor tag and href in this case Implement a robust cross-domain tracking solution using Adobe Analytics (AppMeasurement.js) where tracking parameters are appended to button URLs through the backend system.This ensures consistent visitor identification across multiple domains. I have worked with back-end developer and added the AppMeasurement.js and VisitorAPI.js script on head section so that when user click on button it will appendVisitorID and set it on next redirection URL so that when user lands on page it will add the visitors id in landing page and visitor it will not get changed.With this solution visitor identity is maintained seamlessly across domains, improving attri

False alerts are bad news.  Apart from being very annoying, they can cause you to lose trust in your alerts, leading you to ignore real problems. Out of the box Adobe does not offer a way to turn off hourly alerts overnight. This can lead to false alerts being sent as volumes drop and the data becomes more volatile.  However, there is an easy method to disable hourly alerts during specific hours... Imagine a scenario where you wanted to create an alert when 'orders' are below or equal to 1000, but you didn't want this alert to operate between 1:00am and 6:59am. Set up: 1) Create a 'hit' level segment called 'non-core hours' where 'hour of day' is greater than or equal to '1:00am' AND 'hour of day' is less than or equal to '6:00am' 2) Create a calculated metric called 'Metric for core hours order alert' using an 'if' function: Within 'logic_test' place your 'non-core hours' segment with the 'occurrences' metric nested inside it Within 'value_if_true' add a 'Static Number' wi