Adobe Experience Platform

Authors: Matt Kipilevich and Margarita Savova Predictive Audiences was born out of a Garage Week project by the authors of this blog. Once a year, for one week, Adobe grants engineers complete freedom to work on an idea that interests them. Some of the most innovative ideas across Adobe’s Digital Experience business unit were born out of Garage Week projects, such as ours. When we started, we knew that our customers were spending a lot of time manually creating segments to deliver relevant experiences for the personas they had in mind. We also acknowledged that in many cases, they had a very small window to engage with their users and offer them a meaningful personalized experience, since many anonymous third-party cookies have a lifespan of just one session. We aimed to help our customers by leveraging Machine Learning and creating a system that would allow them to offer effective on-click personalization the instant they saw a user on their property, minimizing guesswork and reducin

Author: Pulkit Chadha In the post, we will look at how you can orchestrate real-time customer journeys with Adobe’s Journey Orchestration and deliver these experiences through Adobe Campaign Classic. In today’s digital-first environment, customers expect consistent messages across all digital and physical touchpoints. However, businesses struggle to leverage their existing investment in Marketing Technology solutions to cater to these evolving needs of their customers. Some of these challenges are: Data needs to be transferred for one system to the other, causing latencies and the inability for Marketers to orchestrate Realtime customer journeys. Legacy solutions talk in different languages (JSON, XML, etc.), needing custom integration to be built. Point solutions and in-house built custom integrations increase technical debt and fragility to the Marketing Technology architecture. In the rest of this blog, we will discuss how Adobe solutions can help elevate these challenges. We wil

Author: Deepak Ranjan Kar Adobe PDF Analytics is here to help you uncover unique data and actionable insights. This post attempts to briefly explain the technology and the often-missed nuances of a document analytics implementation while also covering the best practices from successful real-world deployments. If you are part of the professional community who works in the Financial Services sector, you might have sensed your customer’s uneasiness on new digital transformations deployed. Every industry vertical nowadays relies heavily on documents, be it legal documents, software manuals in IT, or educational content — documents are everywhere. Example of customer experiences are: Inability to understand one’s preference from simple downloads. Discover valuable document performance and engagement. Actionable insights from those truckloads of PDF documents. If you ever wondered derived insights on a beautiful PDF to take the next best action? For example, getting insights from question

Authors: Varun Rawat and Ankur Taneja In this Digital Era, we are served with a targeted ad the minute we browse through a website. Therefore, companies are prioritizing to deliver authentic, useful, and personalized experiences for their customers has become a necessity. This experience needs to be seamless, in real-time, and to the customers’ immediate need or preferences for it to be impactful. This is wherein Adobe Experience Platform Decisioning Service can be a great asset as we can base our offers on the entire interaction history spanning from behaviors detected in the past to the latest situational context. Adobe Experience Platform Decisioning Service gives our customers the capability to create personalized, optimized, and orchestrated experiences in applications running on our platform. In this blog post, we’re going to explore how we can leverage Decisioning Service to show personalized content on an AEM website integrated on Adobe Experience Platform. Adobe Experience Pl

Author:Ivan Mironchuk This blog takes a look at how Places Services powered by Adobe Experience Platform can help companies understand and engage with your users in these extraordinary times. Coronavirus is a pandemic that has affected our lives in a profound way. Brick-and-mortar industries that relied on in-person experiences such as retailers, restaurants, live entertainment have had to rapidly change their strategies to keep their customers safe (#stayathome) while staying afloat. Coresight Research showed a drop of nearly 96% of all retail foot traffic in the states. Businesses have been kept alive through e-commerce with many retailers shifting to home deliveries and curbside pickup. The good news is that lockdowns have had a positive effect in reducing the number of potential Coronavirus cases, and many parts of the world are in some phase of reopening. But what will reopening look like? It could be some time before we have good data on consumer behavior trends. Location is the

Authors: Seung Kim and Marco Massenzio The topic of CI (Continuous Integration) and CD (Continuous Deployment) is one of the most hotly debated across organizations and development communities. CI/CDs have many different solutions to, and opinions by, organizations, developers, and communities. By and large, however, everyone agrees that at a minimum, a CI/CD framework should provide: Orchestrated code-to-deployment process Monitoring and alerting Log management Reporting This blog details Adobe Customer Journey Management (CJM) CI/CD discovery, architecture, and our learnings. Adobe Customer Journey Management (CJM) CI/CD Overview Adobe’s Customer Journey Management (CJM) is designed from the ground-up, to be a cloud-native and container-based multi-tenant system. We have chosen Kubernetes as our execution environment, as it is well-supported within Adobe. That decision was motivated by the following considerations: Kubernetes allows developers to focus on logical entities, such a

Authors: Prateek Kejriwal and Abhishek Kumar Technology has evolved quickly, particularly in the last ten years in Customer Experience Management with every company striving to deliver better customer experiences. Cutting new technologies have enabled our customers. It is very important for every tech company to have a knowledge of who is changing what and what is being changed by whom. However, faster deployments and updates have made it difficult for our customers to keep their innovation updates governed and controlled. A better way to manage your experience deployments is by enabling your tag management solution like Adobe Experience Platform Launch to keep you informed of any changes on your preferred touchpoint, be it a Slack Channel or a Push Notification. In this blog, we will discuss how you can use Adobe I/O Runtime to send notifications to configured endpoints as soon as any Adobe Experience Platform Launch build goes to production. Benefits of this type of notification The

Author: Aaron Hardy The implementation of marketing technologies on a website can be complex. Data is coming and going, personalization content is retrieved and rendered, and identities and segments are synchronized. As Adobe has grown its portfolio of marketing technologies, our technical complexity has grown with it. Many of Adobe Experience Cloud offerings were acquisitions. Each product had its own JavaScript library, its own server endpoint, its own database, and its own method for managing a visitor’s identity. We acknowledged that each Adobe product needed to be integrated with other Adobe products. With Adobe Experience Platform, our goal is to reduce the complexity of implementing Adobe’s technologies on your website by creating a more unified experience. Early first steps included a unified JavaScript library, unified data, unified requests, unified server endpoints, and unified cookies. Let’s take a look at some of the specific pain points we’ve heard from our customers and

Authors: Yeshwanth Vijayakumar, Vineet Sharma, and Sandeep Nawathe Adobe Experience Platform enables you to drive coordinated, consistent, and relevant experiences for your customers no matter where or when they interact with your brand. With Adobe Experience Platform Real-time Customer Profile, you can see a holistic view of each individual customer that combines data from multiple channels, including online, offline, CRM, and third party data. It allows you to consolidate your disparate customer data into a unified view offering an actionable, timestamped account of every customer interaction. In this blog post, we will describe our optimization techniques done to scale our throughput using Apache Spark. In particular, we will describe two stages of Unified Profile Processing where we use Apache Spark heavily and discuss techniques we have learned during optimizing these. This blog post is adapted from this Spark Summit 2020 Talk. Architecture Overview Given that the Adobe Experience

Authors: Tina Dilip Soni, Marina Mahtab, and Althaf Kudiyama Kandi In this post, we explore how we can take a business problem to potential business outcomes using Adobe Experience Platform Data Science Workspace to quickly connect to data and build, experiment, validate and deploy machine learning models at scale. While the model building itself has several steps like data cleaning, data preparation, feature engineering, and ultimately, model building, Adobe Experience Platform provides a much broader and wider end-to-end framework to accelerate the data-to-insights process, perform experiments through hyperparameter tuning, and creating a custom, personalized and intelligent publishing service which can be shared in just a few clicks. This service can be monitored, and retrained for continuous optimization of personalized experiences The end-to-end machine learning framework in Adobe Experience Platform can be broken down into five interdependent steps. Model building and recipe cr

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