Adobe Analytics

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

I shared this in an Adobe webinar presentation a couple years ago and thought I'd add my slides in blog form for the Experience League Community.  Hopefully this is helpful!      

 IntroductionThe Adobe Customer Journey Analytics (CJA) Experimentation Panel is an Analysis Workspace template that empowers organizations to analyze and interpret their A/B tests and multivariate experiments within the CJA ecosystem. This specialized Analysis Workspace panel serves as a gateway to deep experimentation insights, enabling organizations to comprehensively understand how various iterations of their digital experiences influence user behavior patterns and drive business outcomes. Through its template framework for experimentation analysis, the panel enables businesses to make data-informed decisions with confidence and precision, leveraging advanced statistical methodologies and intuitive visualizations. To maximize the value of these experimental insights across your organization, it becomes paramount to establish strong alignment within your analytics and measurement teams regarding the specific experimentation approaches and methodologies being employed, ensuring these

Introduction Adobe Customer Journey Analytics (CJA) has introduced a new dataset type: Summary data. This feature significantly enhances CJA's data model and expands its potential use cases, offering users improved capabilities for data analysis and insight generation. Summary data consists of time-series information from a summary dataset, based on a schema using the XDM Summary Metrics class. Currently, only hourly or daily time-series data are supported. By incorporating Summary data, CJA builds upon its existing foundation of Event, Lookup, and Profile datasets, creating a more comprehensive and versatile toolkit for practitioners. The introduction of Summary data unlocks exciting new possibilities for exploring and interpreting data within CJA. This powerful dataset type complements existing options by enabling users to work with pre-aggregated information, providing a high-level perspective that's particularly valuable for certain analyses. By integrating Summary data alongsid

By : Prachi Jain & Luc Forgeron Introduction  Adobe Journey Optimizer (AJO) is a one-stop solution for managing all marketing campaigns, messages, offers and personalization automation. Through this blog, we are delving into the concepts of how and when to trigger in-app messages in your mobile application through Journey Optimizer. We are also going to explore using the in-app messaging channel to effectively engage with your audiences and direct them to key features of your application.  One of the most frequently asked questions is about the differences between in-app messages and push notifications.  In-app messages are inbound notifications that appear within the app while a user is actively engaged with it, and the decision to show the message is made based on app usage.   Push messages are outbound notifications, meaning the decision to deliver the message to a client is based on a decision made at the server. The end user may or may

What is UTM Parameter? Tagging URLs is a simple and effective way to capture data about your digital marketing efforts. It is the process of adding parameters to the end of URLs that gather and record data. The most used parameters are Urchin Tracking Modules (UTMs), which are supported by Google. There are five main UTMs parameters available: Medium, Source, Campaign, Content, and Term. UTM parameters can be added manually to URLs or appended through auto-tagging with certain platforms, such as AdWords. Auto-tagging automates the process of appending parameters to URLs. There is also the option of URL builders to speed up tagging URLs manually. With a URL builder, we can simply specify the values to be used for each parameter and the builder formats the URL for you.   How UTM Parameters work?  Let’s look at a typical URL without UTMs: https://www.adobe.com Now, let’s check out a URL with UTMs: http://www.adobe.com?utm_medium=organic&utm_source=linkedin&utm_camp

In our last Edge Data Collection Concepts blog, we introduced the basics of an Experience Data Model (XDM) schema. Recall that the schema is the foundational structure of Adobe Experience Platform (AEP) data collection made up of field groups that label the data being collected. The schema class, on the other hand, is a way to define the characteristics of the schema, such as whether it represents a profile or an event. In this post, we’ll take a deeper dive into schema creation and best practices that you can follow as you create your first schema.  Why do I need a schema?  You need a schema whenever you want to send data to AEP. For example, if you want to create audiences in Real-Time CDP (RTCDP) or execute campaigns in Adobe Journey Optimizer (AJO), that requires datasets in AEP that are structured using schemas. Schemas are a tool to support consistent data collection across sources with proper data types.  When You Don’t Need a Schema  While schemas are essent

Watch Now Join Adobe Analytics Champion Mandy George for an exclusive webinar where they will dive into one of the most powerful tools at your disposal: Calculated Metrics. Discover how you can elevate your analytics game by leveraging over 78 advanced functions available in Adobe's metric builder. From basic descriptors like mean and median to sophisticated statistical techniques such as t-tests and regressions, this session is designed to enhance your skill set.What you'll learn:Introduction to Calculated Metrics: Understand the basics and importance of calculated metrics in Adobe Analytics.Advanced Functions: Learn how to apply advanced functions to make your metrics even more insightful.The Calculated Metrics Playbook: Get an in-depth look at the ultimate guide for mastering these functions. 

Struggling with constant guilt of not having removed former colleagues access to Adobe Analytics. Though you know you should be doing it, you're dreading getting started. Or is it the list of old Workspaces that's been on your todo forever, for you to go through and delete any unused workspaces? We'll here's something that will ensure you will spent less than half the time it usually would take you. Like everyone else, I'm constantly looking into how to better use AI both personally and in my client deliverables. So, last week, I decided to see how far I could push AI as a developer on something I had yet to gain exposure to. I thought it would be a good project to see if I could integrate the Adobe APIs into Microsoft Excel.  I am by no means a developer. Javascript I can read, but I used to Google it if I needed to write. Nowadays, I GPT it— if that's even a thing?  My initial thought was to have chatGPT support me in building an Excel add-on, but after explaining my requir

Welcome to our new blog series on Edge Data Collection Concepts, where we’ll explore key elements of Edge Data Collection and their role in your implementation! To kick things off, we're diving into Experience Events – an essential component of Edge Data Collection, designed to capturing real-time user interactions and transform them into actionable insights. What are Experience Events? Experience Events in Adobe Experience Platform (AEP) are records representing user interactions, such as an add to cart or purchase event. These records can be ingested in real-time or batched and are used to enrich data around user behaviors.   Experience Data Model (XDM) Schema: AEP data is structured using an Experience Data Model (XDM) schema. Each XDM schema consists of two parts:   Class: Defines the type of data. The two primary classes are Experience Event (for event records like interactions) and Individual Profile (for customer attributes like names and loyalty details).&

Introduction Imagine embarking on a treasure hunt. However, in this unique adventure, the treasure you seek isn't gold or precious jewels. Instead, it's valuable insights into your customer's journey. Your strategic compass and detailed map for this quest is Adobe Customer Journey Analytics (CJA), a solution equipped with everything you need to decode the intricate clues scattered along your path and help you reach your ultimate goal. As an analyst within your organization, the treasure you're pursuing is a deep understanding of your customer's journey. CJA is your guide, offering the tools necessary to navigate the complex layers of customer journey data. This specialized solution is purposely designed to assist organizations in converting raw data into a comprehensible narrative, providing clear insights. It enables you to analyze and visualize data in a meaningful way, ultimately enhancing your understanding of the customer journey. However, like any adventure, successfully navig

Thank you for joining us in the session! I hope you find these additional resources helpful!Debugger documentation:https://experienceleague.adobe.com/en/docs/experience-platform/debugger/home Chrome store extension link:https://chromewebstore.google.com/detail/adobe-experience-platform/bfnnokhpnncpkdmbokanobigaccjkpob _satellite functions:https://experienceleague.adobe.com/en/docs/experience-platform/tags/client-side/satellite-object Experience Identity Service Opt-in Reference:https://experienceleague.adobe.com/en/docs/id-service/using/implementation/opt-in-service/api Alloy commands:https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/commands/appendidentitytourl#commands Mobile Verbose logs:https://developer.adobe.com/client-sdks/home/getting-started/enable-debug-logging/ Assurance Logs:https://experienceleague.adobe.com/en/docs/platform-learn/implement-mobile-sdk/app-implementation/assurance Mobile Luma tutorial:https://experienc

We are officially open for business for Adobe Analytics Rockstar tip submissions! Join me on stage at Summit while you present your best TWO Adobe Analytics/Customer Journey Analytics/Adobe Product Analytics tips and the audience votes on their favorites for huge prizes!     You have until December 15, 2024 to submit your ideas here: adobe.ly/aarockstar  (and if you'd like, watch 2024's Summit session here) (and if you'd like to see some tips from previous years: adobe.ly/aarockstartips - 2024 tips now live!)   IMPORTANT REMINDERS:🤘 These tips are meant to be unique ways that you utilize Adobe Analytics, Customer Journey Analytics, and Adobe Product Analytics to advance your analyses. We want to see the powerful ways in which you are using the products today. 🎸 If selected, you'll be sharing these two tips in just 8 minutes! So make sure you have a plan for sharing them succinctly and impactfully!🎤 If you have mo

SEO and Adobe Analytics can work together synergistically to enhance a website's performance, visibility, and overall online presence. Here's how they can be integrated for more effective digital marketing strategies:1. Keyword Insights:- Adobe Analytics can provide valuable insights into the keywords that drive traffic to a website. SEO professionals can use this information to optimize content and target relevant keywords more effectively.2. Content Optimization:- By analyzing user behavior through Adobe Analytics, SEO practitioners can identify high-performing content and optimize other pages based on successful patterns. This includes adjusting content, improving user experience, and enhancing engagement.3. Traffic Source Analysis:- Adobe Analytics can help identify the various sources of traffic, including organic search. SEO specialists can leverage this data to understand the effectiveness of their organic search efforts and allocate resources accordingly.4. Conversion Tracking:

Watch now Join us for an exclusive webinar where Adobe Analytics Champion Anita Mummert will share powerful insights to elevate your data analysis skills. In this session, you’ll learn the simplest ways to enhance your data using component settings and derived fields—all without the need to update any tags!What You'll Learn:Effortless data refinement techniquesAdvanced strategies with component settingsUnlocking the full potential of derived fields

This is just a word of fair warning to all who may currently be using the Key Metric Summary component in their Adobe Analytics or CJA workspaces at this time. Currently, the Summary Difference portion of the metric is calculating incorrectly.  I have already submitted a ticket to Adobe, but this is an error happening production-wide across ALL report suites, from what I can see.  Anyone using this specific metric will likely experience what I'm seeing.   The screenshot is from a sandbox environment; so, neither is the data real, nor does it compromise any privacy issues. As soon as I have an update about this being fixed, I will come back and update this post.  Happy measuring everyone!  

Introduction Even with a perfect operating model, transformation programs can fail. Through our years of consulting, we've watched brilliant teams invest months—even years—analyzing their current state, envisioning their future, and meticulously designing roles and interactions, yet still fall short of success. Why? Because people are not numbers in a spreadsheet. Building on our previous exploration of Adobe Customer Journey Analytics (CJA) team models for various organization sizes, we now focus on the most critical aspect of CJA implementation: your people. This article examines Adobe's perspective on Digital Experience dimensions that help organizations move from readiness to results. Traditional change management alone won't suffice—it can create false confidence and blind spots for leaders. Instead, we'll share Adobe's proven approach to helping organizations of all sizes navigate the changes needed to implement and scale CJA effectively. While this article provides valuable in

IntroIn part one of this series, I provided the reason why you would want to prevent collecting data from bot traffic and described the basic process on how to do so.   This article gives two different solutions on how to identify the traffic you would want to block in the first place.Excluding Hits Based on the User AgentAn external party – the IAB - provides to Adobe the list of user agents contained in the default IAB Bot List; and thus, Adobe cannot provide this list to you as a client.  As a consolation, Adobe Workspace does provide a “Bot Name” dimension that provides a list of “friendly names” tied to the bot-based user agents.  For example:But having just the friendly names of these bots does not necessarily inform us of the exact criteria the IAB list uses when it identifies bots.  And so, as much as we'd like to stop collecting data from every single bot in that list, reality shows that it’s not a simple task. That being said, we can still deploy

Introduction Understanding the core concepts of Adobe Customer Journey Analytics (CJA) can help you utilize its potential and make informed decisions for your organization. This post will explore five key ideas at the heart of CJA: Person Identity Handling, Connections, Data Views, Report-Time Processing, and Projects & Analysis Workspace. These concepts aren't just theoretical; they significantly influence how your organization's CJA operates and how to maximize its benefits. Let's delve into these five crucial concepts: Person Identity Handling: This is how CJA identifies and tracks individual persons across different touch points in their customer journey. It integrates varied dataset sources and ensures all data is accurately attributed to the correct person. Connections: Connections in CJA integrate and consolidate various datasets, thereby supporting and enabling a more comprehensive understanding of the customer journey. Data Views: This container interprets data fro

  Introduction Organizational readiness is top of mind for strategic leaders, especially those investing in Adobe Customer Journey Analytics (CJA) . How can they maximize value not just from CJA, but from their people? How can they transform while safeguarding data integrity and promoting sustainable, scalable analytics practices across the organization—all with the right mindset? In this two-part series, we'll explore insights from Brian Au, a CJA subject matter expert, and Shaaz Nasir, the head of Adoption for Adobe Consulting Services. As organizations of all sizes implement Adobe Customer Journey Analytics (CJA), it's vital to grasp the complex interplay of ownership, roles, skills, responsibilities, and mindset within teams. The approach to managing and leveraging CJA varies significantly based on team size, requiring a nuanced understanding of different operational models. This first installment delves into diverse team structures for CJA operations, tailored for smal

  Introduction The process of making Adobe Analytics (AA) Analysis Workspace projects available in Customer Journey Analytics (CJA) requires careful AA administrative planning, preparation, and execution. It's crucial to understand that this isn't a one-way migration where AA projects are deprecated, but rather an admin-driven "porting" of AA projects to CJA at a specific point in time for a given Analysis Workspace project. Be mindful of the prerequisites for this process, including supported ingestion pathways, CJA-side Connection and Data View setup requirements, and CJA Data Views user permission provisioning. Adobe Experience League outlines the porting workflow, covering the steps to take within Adobe Analytics, instructions on how to retry a failed migration, and guidance on monitoring the porting progress of AA projects to CJA using the Admin component migration page. This diagram illustrates the key steps in the porting process, from initial organizational alignment to

By: @kopeti & @jacob-dddev  In the first of this 2-part series, we will go over some of the reasons to consider using server-side data collection. In the next part, we’ll discuss in more detail some of the options available.  If any of the following concerns are on your mind, it's a good idea to explore server-side data collection as an alternative strategy. Consider when the following may apply Page Performance - If your organization prioritizes delivering an optimal user experience, focusing on improving page load times and JavaScript event handling, while simultaneously undertaking significant marketing efforts to send data to diverse destinations for enhanced user acquisition and tailored content to boost customer engagement. Avoid Browser Restrictions - If you're struggling with evolving browser restrictions, such as third-party cookie limits on Safari, Chrome, and Firefox, and seek persistent visitor identification, opting for