Adobe Experience Platform

Hi Team, I am looking for best practices tom construct the XDM for Individual profile with many custom classes which will have additional details about the individual profile. I am trying to understand which approach will be better and on which aspect:Defining custom classes and refer those classes from the Individual profile as shown in Define a Relationship Between Two Schemas Using the Schema Editor | Adobe Experience PlatformEmbed the custom classes as field groups (as we have homeAddress under Person) within the individual profile What aspects should we consider to decide when to choose which option? For example: If I go with a model following Option 1, then can I create a segment rule based on the attributes which belongs to the reference entity? Is there any restriction(s) on these 2 options?  Thanks in advance.

Hey Guys,   We’ve improved the left navigation for Experience Platform, so you can now interact with it from the top left of the header to show/hide the navigation panel and you will now see only the capabilities you have access to. We’re looking to preview the new experience with any regular/active users before it’s publicly available to all, targeting late October.    How this would work:  We’ll give you early access by enabling the new left navigation for you on 1st October 2021, and would love for you to share your thoughts with the product team on how it feels when you use it or provide any other feedback you may have.    Leave a comment if you would like early access and are open to participating. Thanks!   In case of any queries, reach out to @nimashajain    Thanks Nimasha 

Hi,I have created several same buttons on a page (same cssClass, different attribute). I create an event rule using the css selector. What I want to do is track which one the customer click and then set its value as an eVar or Props.  I know I can create event rule for each of them but it is stupid. I find an answer for dtm and try to imitate it. However in Launch, the keyword "this" point to a null object in Launch.Any solution to this problem? Thanks!How to track the click url through data element and pass to Adobe Analytics?

Hi all,We are wondering how everyone is implementing the Google Global site tag in Adobe Launch.We have tried to use the "Google Global site tag" extension from acronym, which is available in the extension list, without any succes (some of the problems we are having are double pageviews, pageviews not fired at all for Floodlight).Wondering if any of you are having the same issues, of have you implemented this tag using custom code?Would love to hear your experiences,Thanks!

Author: Ankur Ahlawat Adobe Experience Manager is the recognized leader for digital experience management, and now, it's strengthening this position even further. Adobe is moving Adobe Experience Manager (AEM) to the cloud. AEM Cloud Service introduces the next generation of the AEM product line, moving away from versioned releases like AEM 6.4, AEM 6.5, etc. to version-less, fully continual releases of "AEM as a Cloud Service." Below, we'll cover: The advantages of making AEM a Cloud Service offering What changes/challenges this move to AEM as a Cloud Service brings Features Not Supported in AEM Cloud Service. The advantages of AEM as a Cloud Service AEM Cloud Service adopts all the benefits of modern cloud-based services: High availability: One of the key benefits of moving to AEM Cloud Service is the ability for all services to be always on, so that our customers never experience downtime. In the past, especially on the author side, there was a need to periodically stop the serv

Author: Erin Davis What information can I gain from reading this article? Apple changed how cookies are persisted in Safari Browsers so that some cookies expire after 7 days. Despite the change to Safari, data sets from Adobe Experience Cloud cookies are still being collected. Lookback windows and return visitor counts may be reduced for Safari traffic until an Adobe update is made available, targeting end of April to May 2019. Along with everyone in the industry, Adobe is developing both short and long-term mitigations. The details in this post can change at any time. What does not change is our commitment to our customers and consumer privacy and choice. What is ITP 2.1? On Feb. 21, 2019, Apple announced its latest update to ITP (Intelligent Tracking Prevention). Unlike previous versions focused on third party cookies, this version details new tracking prevention measures for first party cookies. In upcoming releases of iOS 12.2 and Safari 12.1 browsers, first party persistent coo

Author: Nils Meder The first time most people hear about chaos engineering their instinctive response is "Be careful," "Be safe," "Keep buffers up." But when they say that, they're missing the point. With chaos engineering, we are making our environments stronger and more useful by purposefully trying to destroy them. To ensure a working platform even under the most inconceivable circumstances, you have to move beyond planning for the "known" scenarios. We began our chaos engineering journey a few years back, starting with small experiments and tools such as Chaos Monkey, used by Netflix, Amazon, and others. With these first smaller experiments, we mostly confined our chaos to a very limited non-production environment. One where you probably already know beforehand what the consequences are. Often we'd even disconnect the system from other services, to mitigate damage. Each of those experiments produced results that were improving the system, and we grew from there. But the recent add

Author: Chetan Prasad We're pleased to announce the general availability of the Adobe Experience Platform Mobile SDK, initially released in the fall of 2018. This new major version has been re-architected from the ground up and replaces the existing 4x Mobile SDK. This new Adobe Experience Platform SDK is easily configured and managed via Adobe Experience Platform Launch, and provides a wide variety of new features in addition to the existing functionality from the 4x Mobile SDK. Watch a short clip to see how we’ve brought Adobe Experience Cloud Mobile Activation to Launch The Adobe Experience Platform SDK is available today for Android and iOS and also includes support for React Native. In addition to server-side and programmatic configuration options, the SDK also supports third-party vendor extensions, and a robust client-side rules and actions engine. The Adobe Experience Platform SDK also introduces support for new Adobe solution functionality such as mobile pus

Authors: Ashok Pancily Poothiyot, Kumar Sangareddi, Pari Sawant, and Jenny Medeiros This article goes behind-the-curtain to show how Adobe Experience Platform Data Science Workspace uses AI and machine learning to streamline the data-to-insights journey and enables brands to quickly deliver personalized customer experiences. Today's brands and customers want personalized experiences delivered in real-time. This prioritizes mining big data for insights that deliver meaningful customer interactions. The greatest barrier to insights is refining data, similar to how crude oil must be refined before it is useful. Skilled data scientists are at the helm of the data-to-insights delivery, but their workflow is hindered by repetitive tasks, overly-complex technology, and scattered data across multiple repositories in different schemas. Data scientists spend 80% of their time organizing data instead of deriving insights from it. Adobe Experience Platform Data Science Workspace is leading the ef

Authors: Naomi Meyer and Jenny Medeiros The following blog post is from Adobe Experience Platform< on tips and tricks for building products for the world. It will describe best practices for how developers can easily prepare JavaScript web and mobile applications to be used effectively across different locales and cultures in order to further international inclusion and accessibility. Developers and businesses can no longer afford to limit content to their default language. Internationalizing apps and websites is better than hard-coding English-only strings, because it enables users to function within the app in their native mother tongue, which improves the user experience and overall diversity, inclusion, and accessibility of the app. In today's world of continuous content and personalized products, let's rethink our approach and build software for the world to understand. Internationalization (I18N) is the process of designing and preparing software products (apps) to support mu

We are investigating using Adobe tags in our iOS and Android apps for configuring various systems i.e. turning features on and off.I've been trying to find the SDK documentation on how to do that, and have so far drawn a blank.I can see this tutorial which shows the app receiving the tags configuration, but I haven't found which API we would use to extract that information, use the settings in the app, and probably listen for any changes in the settings.If anyone could point me in the right direction, that would be very helpful - thanks!

Hi Team, I have created couple of segments in Adobe Experience Platform and each segment has a good number of audiences. Now I want to send these audiences (activation) to Adobe Audience Manager.  I was going through the below document, but not able to understand the whole integration:https://experienceleague.adobe.com/docs/audience-manager/user-guide/implementation-integration-guides/integration-experience-platform/aam-aep-audience-sharing.html?lang=en I may be wrong, but I think "Audience Manager Connector" is used to feed audiences from Audience Manager to AEP, not the other way. Can anyone please help me to understand on how to share the AEP audiences to Adobe Audience Manager? Thanks in advance. 

Hello Finders, Hope you are having a funfilled Thanksgiving. I am grateful for keeping up the pace and growing together in this learning journey. Today we are going to look at most important aspect Real-time Customer Data Platform (Real-time CDP).  Real-time CDP includes tools for data governance, identity management, advanced segmentation, and data science so that you can build profiles and define audiences, as well as derive rich insights while being able to enforce strict data governance policies. Read the complete guide to RT CDP. Destinations are pre-built integrations with destination platforms that allow for the seamless activation of data from Adobe Experience Platform. You can use destinations to activate your known and unknown data for cross-channel marketing campaigns, email campaigns, targeted advertising, and many other use cases. Read the complete guide to destinations. Let’s relate all of them in “what to do” Build the customer profile. Personalize the us

Dear Friends, We are trying to upload the sample data to test out the data ingestion through file upload method for the schema we have created. Whenever we are trying to upload the data with a single record in it through CSV upload, we are getting the following error. Screenshot attached below for your reference. NOTE: The strange thing that happens is we would be able to see the data getting ingested into the dataset. However, during the data ingestion process, it throws this 422 error (Unprocessable Entity). Please help us understand what is the cause of this error and how to resolve this.Thanks in advance. Gratitude.  

I created a curl command as shown below which will let me subscribe to library updated event and send response to a url. Executed this command in online curl editor which sent 201 response but I don't see any success response in the url when library is updated.curl https://reactor.adobe.io/properties/PRe88025c3c4de4dba84ebece68fc48ebf/callbacks \-H "Accept: application/vnd.api+json;revision=1" \-H "Content-Type: application/vnd.api+json" \-H "Authorization: Bearer [token]" \-H "X-Api-Key: [key]" \-H "X-Gw-Ims-Org-Id: [org id]" \-X POST \-d \'{"data": {"attributes": {"url": "[url]","subscriptions": ["library.updated"]}}}'

Hi All, In my AEP web sdk implementation, I am sending analytics event 8 to AEP on start of a registration form. However I am seeing this event populated as dimension in customer journey analytics and not as metrics. Below are the steps I did. Can anyone please guide me what I need to do to capture these events as metrics and use in CJA or point me to a documentation on how to capture analytics events as metrics from sdk ? 1) created an XDM data element to map event 8 to form start id name and value  2) create a rule in Launch to fire on form start. (this is working fine and data is seen in both AEP Debugger and Dataset) 3) Event 8 is appearing as dimension in CJA workspace and not as metric. 

Please I need help jumping this huddle. I am use to seeing a lot of warning in my Open Editor screen due to the line break in the plugin codes but now I get an Error which is now preventing me from compiling the library. Noticed this since the outage yesterday.. How do I save my library, I tried to remove line breaks from the plugin codes but still struggling to save. Please help as i have a go-live looming

I have a private extension and I am trying to use the extension bridge for code editor.When the code is saved I want that the code saved is saved as a function in the settings. function editConfig() { window.extensionBridge.openCodeEditor({ language: 'javascript' }).then(function(code) { //source property needs to be a function window.customCode = { source: function(window) { code } } }); }  However when I look at the window.customCode.source I can see that the body of the function does not contain the value of code from editor but justƒ (window) {code}I am using vanilla javascript in my project. Should I be using new Function('window', code) ?I would like to obtain same functionality as in the code editor for the data element action from the core extension.

Hey folks, Last Friday, we connected XDM, Schemas via data stream via this post. Reiterating, XDM is a framework on which schemas would be built for data ingestion. Actual data flow to schemas through DataStreams.  Schemas are rules on which the dataset would store data in form of tables. This Friday we would see more of Data ingestion from sources and getting the DataStreams. Source: A source is a general term for any input connector in Platform. Sources in Experience Platform are Adobe applications, advertising, Cloud storage, CRMs, Customer Success, Databases, payments, streaming and protocols. Source connector: Source connectors (also known as sources) help users easily ingest data from multiple sources, allowing the structuring, labelling and enhancement of data using Experience Platform services. Data can be ingested from a variety of sources such as cloud-based storage, third party software, and CRM systems Data ingestion: Data ingestion is the process of adding data from a

Hello Finders, Developing a holistic understanding of customer require relevant digital experience which is impaired due to fragmented customer data making a single customer appears as multiple identities. Platform Experience brings identity service to provide the comprehensive view of customers by stitching identities across devices and systems. Introducing some key terms Identity: An identity is data that is unique to an entity, typically an individual person. ECID: Experience Cloud ID (ECID) is a shared identity namespace used across Experience Platform and Adobe Experience Cloud applications. Namespace: An identity namespace serves to distinguish the context or type of an identity. Real-time Customer Profile:  It merges data from various enterprise systems to form customer profile in time series events. Merge policies: These are rules that Platform uses to determine how data would be prioritized and what data would be used to create customer Profile. Union Schema: Its ability

Author: Khushwant Sehgal (@KhushwantSehgal). We live in a world full of great digital and physical experiences. Companies invest heavily in creating personalized and enthralling experiences to capture the attention of their customers. These experiences help companies attract, retain, and grow their customer base. “Today, people buy experiences, not products, products [aren’t the main] differentiator anymore."— Shantanu Narayan, CEO, Adobe AEM Forms has helped many organizations deliver great onboarding and enrollment experiences over the years. These experiences have helped organizations convert leads to actual sales, process captured customer data with business workflows, deliver responsive experiences based on the audience profile, and much more. Now, AEM Forms is available as a Cloud Service. The cloud-native edition of AEM Forms allows you to quickly get started with AEM Forms to build beautiful data capture experiences without setting up local infrastructure. The Cloud

Author: Jaemi Bremner (@Jaemi_Bremner), Allan Witts (@allanwitts) and Eric Knee (@EricKneeDX).  This blog details a single implementation for a publishing customer on Adobe Experience Platform. Not all aspects are guaranteed as general availability. If you need professional guidance on how to proceed, please reach out to Adobe Consulting Services on this topic. “30-day free trial! 7-day trial period! First month free!” As consumers, we are all familiar with this kind of offer when signing up for a subscription service. It is an attractive offer, giving us the chance to try out and assess the value of the product or service before we commit to paying. From the business perspective, the logic is also clear — gain subscribers by postponing the payment barrier and attempt to convince the consumer that the product or service is worth paying for, such that the free subscribers go on to become paid subscribers. When running such a promotion, the key factor to make it succ

Authors: Raman Gupta and Vardan Gupta Adobe Experience Platform’s Orchestration Service provides APIs to author and manage multi-step workflows. Behind the scenes, this service leverages Apache Airflow as its workflow execution engine. It supports two types of workflow triggering/execution mechanism. Time-based trigger based on some cron schedule On-demand/ad-hoc trigger using APIs. But there are use cases/requirements to trigger a workflow based on some events. Like trigger data-prep or data warehousing job on the arrival of new data into Adobe Experience Platform. So what's missing is the capability to trigger a workflow based on some pipeline events. AEP Orchestration Service is being used by multiple solutions and event-based requirements are coming from most of them. So instead of every service writing their own event listener and placing a custom rule engine for identifying matched events, we thought of building event-based triggering capability as part of the orchestration se

Author: JB Creusat This post provides the steps necessary for Adobe Analytics users to take to ensure their cookies will continue to provide the data they need for customers using the new Chrome 80 browser. With the release of Chrome 80 in February 2020, the need for strong governance around your domains has never been so critical. Whether you have a single domain or manage several, you need to ensure you have secure and first-party cookie support. If you fail to account for all your domains, visitor identification issues will occur with sessions and marketing attribution broken. First validation checks Two common issues will arise when you don’t have governance around your domains: you will find some of your domains in the Referring Domain report and your Page report will include "Other" as a value. The last issue is the one you want to fix first: it means you have a domain hosting your Adobe Analytics library, but you have not included it in your Internal URL Filters. Review your cu