Adobe Experience Platform

Hi, we implemented (because of GDPR) the optin service so that Adobe Analytics tracking is only loaded when the user gives consent. But now we see a higher bounce rate (>15%) on our website. Do you know any reason why this happens and is this because of the optin service? Thanks,Sophie

Hi All,  Currently we use Android mobile sdk on the Device Type - `Television` 'com.adobe.mobile:adobeMobileLibrary:4.18.2' . For some reasons, we see the number of visits are 10x higher compared to page views. We used some dimensions to see where they are coming from and found they are `unspecified` . Could some one please assist here on what situations the number of visits would be higher than page views ? We confirmed with the devs that there are no trackaction is trigerring an extra visit. Happy to provide more information. @andrey_osadchuk @andrey_osadchu1  Could you please assist mate ?Thanks Vijay

In AEP, for DULE (data usage labeling & enforcement), can policies and labels be duplicated from a DEV environment to a PROD environment? For example, can a Data Engineer duplicate a policy and a dataset from a DEV sandbox to a PROD environment, or does it need to be re-created in PROD? I believe it can be duplicated, but if someone could comment and confirm/deny (with an explanation of why if it's not possible), it would be very much appreciated! THANK YOU! 

Meet Alloy.js and Never Tag for an eVar or Mbox Again Over the years, as Adobe has built or acquired new technology, and we've collected lots of JavaScript libraries — AppMeasurement.js, mbox.js, at.js, DIL.js, Visitor.js, just to name a few. Each has its own strengths, features, history, functions, schema, quirks, and interdependencies. Although Adobe Experience Platform Launch makes it as easy as possible to manage all these libraries, customers have been asking us for years why we can’t just have one JavaScript tag and library.  Today is the day. Meet the new Alloy.js. Our team has worked hard all year to take all the best features of our current libraries and build a new one that supports Adobe Experience Platform, Adobe Analytics, Adobe Audience Manager, and Adobe Target. One library and beacon, sent to a single destination, then mapped and sent to all your Adobe solutions server side. And that’s just the beginning. View the session -  https://adobe.ly/39wvntK Let'

I am executing query which should return me results from page and assets. If keyword appears in title of page or asset, it should be listed first. Otherwise, if keyword appears anywhere else in page or asset, it should be listed in end. I have added boost value to title in cqPageLucene and damAssetLucene , so that i get top results with search word appearing in title of page or asset. Problem: I am not getting the required order. The search results always list me pages first and then the list of assets. Ordering within pages or within assets work fine, its just that I don’t get mix of results between page and assets. How can I update my query or index to get the required ordering of pages and assets. Queryfulltext=fly2_group.1_type=cq:Page2_group.2_type=dam:Asset2_group.p.or=true3_group.1_path=/content/we-retail/us3_group.2_path=/content/dam/we-retail3_group.p.or=truep.limit=10p.or=falsep.offset=0 Actual Results        &n

Hello!   Can I get some clarification wrt to how to connect AEP and Target?  From what I gathered, currently AEP has to leverage Audience Manager?  In the absence of Manager, it can work with tag extension as well?  With the beta release, I'm assuming the connection becomes automatic?    Thanks!

Hi Team, I am new to the AEP Web SDK and trying to explore the capabilities of the Web SDK just by creating a static web page in my local desktop. What I had done so far is:Created a XDM (ExperienecEvent) in AEPCreated a dataset for the XDM I had defined in AEPCreated a DataStream in Adobe LaunchEnabled AEP to send data to AEPMapped the dataset (created above)Created a Property under "Tags" in Adobe LaunchInstalled and configured AEP Web SDK, Cloud ID Service as ExtensionsPassed my ORG ID to Web SDK while configuring and mentioned "edge.adobedc.net" as Edge domain.Created some local storage variables as Data ElementsCreated a data element of type XDM object and mapped the data elements to the respective XDM fieldsCreated rules for a particular Page Type to  send Event of type "commerce.productViews"Created a Library and published it to Development environmentIn the static web page, added the script for Development environment along with other local storage elements whose valu

Authors: Frederik Werner, Akintunde Ajayi, and Nikhil Maddirala Frederik Werner is a German Analytics Lead and Data Scientist working in and writing about Web Analytics and Online Marketing Technology. In this fourth post of a four-part series, Frederik will provide the overview and get-started tips on Adobe Experience Platform Query Service. He gives examples of his favorite tricks using Query Service and specifically for customer journey analysis use cases in Customer Journey Analytics. It also includes how to write back data to Adobe Experience Platform. Query Service is a feature of Adobe Experience Platform. Adobe Experience Platform provides SQL analytics and AI/ML capabilities that enable enterprises to generate and operationalize customer intelligence for driving improved personalized customer experiences. Adobe-defined functions: Pathing Next and previous page dimensions One of the things that are still missing from Adobe Analytics Workspace is the next and previous page dime

Authors: Frederik Werner, Akintunde Ajayi, and Nikhil Maddirala Frederik Werner is a German Analytics Lead and Data Scientist working in and writing about Web Analytics and Online Marketing Technology. In this second post of a four-part series, Frederik will provide the overview and get-started tips on Adobe Experience Platform Query Service. He gives examples of his favorite tricks using Query Service and specifically for customer journey analysis use cases in Customer Journey Analytics. It also includes how to write back data to Adobe Experience Platform. Query Service is a feature of Adobe Experience Platform. Adobe Experience Platform provides SQL analytics and AI/ML capabilities that enable enterprises to generate and operationalize customer intelligence for driving improved personalized customer experiences. Adobe-defined functions: Attribution Recreating entry- and exit Dimensions Another thing that is missing from the Analytics Data Connector data is some of my beloved Pr

Authors: Frederik Werner, Akintunde Ajayi, and Nikhil Maddirala Frederik Werner is a German Analytics Lead and Data Scientist working in and writing about Web Analytics and Online Marketing Technology. In this second post of a four-part series, Frederik will provide the overview and get-started tips on Adobe Experience Platform Query Service. He gives examples of his favorite tricks using Query Service and specifically for customer journey analysis use cases in Customer Journey Analytics. It also includes how to write back data to Adobe Experience Platform. Query Service is a feature of Adobe Experience Platform. Adobe Experience Platform provides SQL analytics and AI/ML capabilities that enable enterprises to generate and operationalize customer intelligence for driving improved personalized customer experiences. Adobe-defined functions: Sessionization Recreating Visits using Sessionization One of the surprises I encountered when starting with Adobe Experience Platform is that the Ad

Authors: Frederik Werner, Akintunde Ajayi, and Nikhil Maddirala Frederik Werner is a German Analytics Lead and Data Scientist working in and writing about Web Analytics and Online Marketing Technology. In this first post of a four-part series, Frederik will provide the overview and get-started tips on Adobe Experience Platform Query Service. He gives examples of his favorite tricks using Query Service and specifically for customer journey analysis use cases in Customer Journey Analytics. It also includes how to write back data to Adobe Experience Platform. Query Service is a feature of Adobe Experience Platform. Adobe Experience Platform provides SQL analytics and AI/ML capabilities that enable enterprises to generate and operationalize customer intelligence for driving improved personalized customer experiences. How Query Service works and interacts with Adobe Experience Platform I recently got the chance to dive into Query Service in Adobe Experience Platform and Customer Journey An

Author: Baubak Gandomi This is the second post in a two-part series about the importance of measuring efficient functional tests in platform engineering and in complex products. Baubak Gandomi is a Test Architect with Adobe Customer Journey Management. Code Coverage has been a buzz work in the industry as a means to detect holes in our certainty regarding the testing of our products. This is actually a very good measure since it helps us find lines in the code that are not tested. We also think it is quite misleading if used on its own to represent test gaps, and that the efforts in it could be misplaced. We have covered these problems in more detail in a separate article “Problems with Code Coverage when Assessing Functional Tests”. Instead, we propose “Transactional Coverage” as a new approach to code coverage, which is simpler in its implementation, and which better maps to the business. It will also help you better prepare a harness for an application to which you are new. The mai

Author: Aaron Hardy In our previous post regarding Adobe Experience Platform Web SDK and Edge Network, we discussed customer pain points that Adobe’s new technologies are attempting to solve. One of these pain points was performance. In this post, we dig into performance benchmarks to discover how much improvement you might see on your web pages when migrating to Adobe Experience Platform Web SDK and Edge Network. Performance equals money. In 2018, Google published a report which showed: As page load time goes from one second to three seconds, the probability of bounce increases 32%. As page load time goes from one second to five seconds, the probability of bounce increases 90%. As page load time goes from one second to ten seconds, the probability of bounce increases 123%. Here at Adobe, we’ve been working hard to contribute to your success in this area and have some great news to share: we recently released Adobe Experience Platform Web SDK and Adobe Experience Platform Edge Netwo

Authors: Lavinia Lungu, Calin Dragomir, Costel-Cosmin Ionita, and Alexandru Gabriel Ghergut As part of Adobe Experience Platform, Audience Manager is one of the most powerful data management platforms used by marketers to collect, manage and activate audiences across multiple channels. It is purpose-built to create meaningful real-time customer experiences. Audience Manager collects over 30 billion requests per day from the customer’s websites. This scale cannot be achieved without a globally distributed edge infrastructure that is able to perform data collection and real-time segmentation. The deployment consists of over 700 EC2 instances spread across 8 AWS regions. Marketers can manage their audiences through a web portal, which is backed by a cloud-hosted, non-distributed MySQL datastore. We refer to the data stored in this MySQL instance as metadata because it directly relates to audiences and customers. That metadata needs to reach the edge infrastructure in order to reflect any

Authors: Kevin Cobourn, Nick Hecht, and Jody Arthur In this post, Adobe Experience Platform introduces Digital Experience Blueprints — a whole new way to learn and understand how you can use its technology to build incredible customer experiences. When it comes to analyzing vast amounts of data and simultaneously delivering personalized experiences, knowing how to do that right can be daunting for brands today, especially given the complexity of the data and technologies they are working with and privacy regulations that increase the risk of doing it wrong. It can also be difficult to determine whether a particular solution will work for a given use case and whether that solution will provide a sufficient ROI to warrant the investment. Sorting out these problems doesn’t have to be challenging. Adobe Experience Platform is unveiling a new program we are calling Digital Experience Blueprints built to help our customers improve their digital transformation strategy and implementatio

Authors: Kevin Cobourn, Nick Hecht, and Jody Arthur In the first post of this series, Adobe Experience Platform introduces Digital Experience Blueprints — a whole new way to learn and understand how you can use its technology to build incredible customer experiences. In this post, we introduce our second Blueprint, Web Personalization. Web personalization with Adobe Experience Platform involves the use of Real-time Customer Profile segments enriched with your company’s data, Adobe Analytics data (optional), & Adobe Audience Manager data (optional) to personalize web experiences with Adobe Target. While most brands can offer personalized experiences using behaviors tracked on a single device, it is far more challenging to deliver them across each web-enabled touchpoint a customer may use across devices. This challenge arises from one or more of the following problems: Cross-device behavior is not linked. Offline data is not linked to an online profile, or if it is, the data transf

Authors: Kevin Cobourn, Nick Hecht, Eric Knee, and Jody Arthur In our first post of this series, Adobe Experience Platform introduces Digital Experience Blueprints — a whole new way to learn and understand how you can use its technology to build incredible customer experiences. This post introduces an Adobe Experience Platform Digital Experience Blueprint that brands can use to quickly build a Platform implementation for multi-channel messaging orchestration to drive customer-led engagement at scale across every channel. Today for enterprises, the customer journey is more complex than it has ever been. Customers jump from one channel to another, often multiple times, before they convert in the way a brand wants them to. However, customers value seamless and personalized experiences without understanding the technical architecture and solutions to deliver real-time contextual experiences. Customers want the experiences that will deliver the best value for their lives. Enterprises want

Authors: Kevin Cobourn, Nick Hecht, Kyle Morehouse, and Jody Arthur In the last post, Adobe Experience Platform introduces Digital Experience Blueprints — a whole new way to learn and understand how you can use its technology to build incredible customer experiences. In this post, we introduce our first Blueprint, Audience Activation. Audience-first activation is the key to success in a data-driven marketing world. However, many brands are still focusing their efforts on channel-first activation, which often delivers inconsistent reach and personalization. With a channel-first approach, each channel acts as a silo in which personalization efforts target only the customers interacting with the brand on that channel. The problem with this approach is that it doesn’t reflect the reality that customers interact with brands across many different touchpoints. Channel-first activation cannot connect customers’ behavior through their interactions across multiple channels resulting in lost opp

Author: Dan Popescu This blog detail one of the most common operational procedure Adobe Experience Platform performs with Spinnaker. Please note this scenario may not apply if the environment you’re working with is not dynamic. In our case, there many teams with multiple Kubernetes clusters so there is a constant need for onboarding/removing clusters or adding/removing namespaces from accounts. Spinnaker is one of the most powerful open-source tools available for performing continuous deployments. My team is one of the first at Adobe to use Spinnaker in production at scale and over time we’ve expanded from VM deployments in AWS to Kubernetes and Azure. The whole CD ecosystem is based on Spinnaker and we offer this solution for multiple teams within the company. Currently, more than 20 different engineering teams use our Adobe Experience Platform. When talking about multi-tenant solutions one of the most important aspects to consider is isolation. This implies that teams cannot interac

Author: Gowtami Mohanty In this blog, we will be discussing how to create a ‘Store Entry’ experience for customers by sending the best in-store offers as a mobile push using Adobe Experience Platform Places Service. Adobe Experience Platform Places Service, previously known as Adobe Experience Platform Location Service, is a geolocation service that enables mobile apps with location awareness to understand the location context by using rich and easy-to-use SDK interfaces accompanied by a flexible database of points of interest (POIs). Places Service allows our customers to: Take actions such as push, email, SMS, etc from location signals in real-time, when and where it matters. Deliver the right context provides a more enriching mobile engagement experience. Gain deeper insights into their users by analyzing their physical behavior. All this possible with only four simple steps. Prerequisites Before starting, you should have the below ready: Ensure you are provisioned to use the Pl

Authors: Piyush Gupta, Subrahmanya Giliyaru, and Pratik Panchal With the emergence of the microservice architecture pattern, several organizations build technology solutions involving data distributed across several microservices. Further, the number of such microservices and data stores within the organization continues to grow with the growing number of products, features, and capabilities. Much of this data distributed among isolated data stores is surfaced to the end-users simply as one or more products and capabilities offered by the organization. But the end-user would want to quickly find desired data from across any of these products and capabilities using a centralized search bar or user interface. Given the isolation between such microservices and data stores, building such a unified text search solution poses fundamental problems: Each of the microservices needs to build an index exposing text search capabilities over its data entities, leading to duplication of effort and