Adobe Experience Platform

Authors: Joel Huff, James Rennie, Nishith Kota, Kevin Davis, Gowtham Ranganath, Jayant Bhushan, and Jody Arthur This blog is how Adobe Experience Platform was implemented at Adobe IT and Support organizations to help sales and support teams deliver better customer experiences as part of our "Customer Zero" program. When it comes to using enterprise data to deliver extraordinary customer experiences, 1/10th of the data often represents 10x of the complexity. This complexity is the result of customer data fragmentation caused by many different types of data from numerous data silos. Enterprises across all industries are struggling with data fragmentation as a roadblock to their ROI for deep investments in digital transformation intended to increase loyalty and retention by providing exceptional customer experiences. The data fragmentation roadblock presents two fundamental challenges that must be overcome in order to deliver indelible personalized customer experiences in real-time. The

Authors: Mandeep Gandhi, Som Satpathy, and Harry S. Adobe recently announced two new Streaming Sources and Destinations as part of its real-time customer data platform offering: Azure Event Hub and AWS Kinesis. This blog will detail the use cases, how we started, what technical decisions we took, and the challenges we faced while executing this release. Adobe Experience Platform has a large Kafka infrastructure with multiple environments and data centers. We had already built Pipeline Smarts for stream processing. It made perfect sense for us to explore Kafka Connect for our Ingress/Egress story. We got this opportunity in our Adobe Experience Platform Hack-week last December. During our Hack-Week in December 2019, we built a powerful proof of concept that included filters on attributes of data, SMTs, and how to ingress/egress. Development Common DSL We set on the quest of what would it take to get Kafka Connect production-ready. The idea was not just to build a couple of connectors a

Join us for our next Adobe Campaign Community Q&A Coffee Break, on Thursday, April 21st, 2022 @ 8am PT   We'll be joined by a team of Adobe Campaign Enterprise Architects, namely Scott Segrin, aka @scotts44930614, @scotts44930614, Manager - Enterprise Architecture Eric Knee, aka @eric.knee, Principal Enterprise Architect David Loyd, aka @david_loyd, Principal Enterprise Architect Peter Mancuso, aka @pmancuso, Enterprise Architect They all will be signed in here to the Adobe Campaign Community to chat directly with you on this thread to take your Adobe Campaign questions pertaining to their areas of expertise:  Adobe Campaign & Experience Cloud Integrations Adobe Campaign & AEP Integration - Segment Sharing   REQUIREMENTS TO PARTICIPATE  Must be signed in to the Community during the 1-hour period  Must post a Question about Adobe Campaign Coffee Break topic on this t

Hello Finders, We are meeting after two weeks of break. Hope you had been catching up with the Platform Experience to working on learnings. Till now we had we had created Schemas, datasets, connectors and data streams. Data sources need to be mapped by XDM-schema which ingests data from sources. Sources could vary from CSV to streaming data. In this FF, we will try implementing Web SDK. Let’s see key concepts: Adobe Experience Edge: It’s a new framework for low latency data collection, pluggable computing and rapid activation. It provides SDKs for different channels like JavaScript, Mobile, server side according to needs of your environment. It sends data to common Adobe domain (adobedc.net) and receives a single payload back for data and experience delivery. Experience Edge consist of AEP Web SDK, AEP Mobile SDK, AEP Platform edge Network. Adobe Experience Platform Web SDK: A JavaScript SDK and tag extension to dramatically simplify deploying Adobe technologies Adobe Experience P

Authors: Jaemi Bremner (@Jaemi_Bremner), Peter Fransen (@meatcouch), and Chetan Prasad (@praschetan). In late 2016 we embarked on a journey to reimagine our existing Adobe Experience Platform Mobile SDKs. There were a few concrete goals in mind, as well as a few nice-to-haves. First and foremost we wanted to implement an extensible and pluggable architecture that would allow for incremental additions of functionality, both internally developed and from partners and customers alike. Additionally, we wanted to build platform-independent logic that was easily portable across various client devices and operating systems. Lastly, we wanted to ensure that the various performance metrics that we track for the SDK (CPU time, memory consumption, binary size, stability) remained at least the same as our pre-existing SDKs. Language selection With our baseline requirements and architectures in hand, we moved on to the selection of the underlying language(s) that could be used to achieve or e

Hello Everyone, Seeing our thriving community, We look forward to pick 4 contributors for month of February. Looking for rising stars who are new to community and spreading knowledge with most accepted solutions. Looking for people who are building the networks of likeminded people with productive discussions. Looking for leaders who switched gears in short span of time; Leveled up at a faster pace. Keep Rising along with lifting community! Cheers, Nimasha | Product Community Manager | Platform Experience | Adobe

Author: Oliver Lindberg Adobe has a long history of building products, services, and tools that serve a range of users. We moved from shrinkwrap software that was delivered every 12–18 months to having a connected relationship to our users 24/7. As we continue our journey in the cloud, we are growing a comprehensive and open platform for developers who can manage integrations, extensions, and build on our platform for their own custom solutions. The Adobe Experience Platform (formerly the Adobe Cloud Platform) provides a suite of Infrastructure-, Platform-, and Software-as-a-Service capabilities that support Experience Cloud, Document Cloud, and Creative Cloud. The clouds ingest, manage, and derive value from the information that users entrust to Adobe. By joining content and data in an open cloud platform, developers are able to create apps and experiences quickly, effectively, and at scale. Platform businesses have a "network effect," which means the more that people are using somet

This post is part of a series about auto-taggingWhile using a tag management system (TMS) like Adobe Launch, you can use different tagging methodologies to achieve your requirements. There are 3 main concepts of tagging which are:DOM scraping which uses the functionalities of the DOM API to gather the data from the web pages. While it is a fast and flexible approach, it is also fragile as any changes in the DOM can break your implementation without notice.Direct Call Rule which involves calling the rule/tag directly from your platform code. This approach is less flexible than the DOM scraping one. It is more robust and allows you to streamline your implementation. One of the main issues with DCR implementation is that in most instances there is no defined data structure and it also requires you to use the reference to the TMS object in your platform source code which will become a huge technical debt.Data Layer which allows you to define a JavaScript object which will contain a structu

Authors: @danny-miller, Shruti Jagtap, Douglas Paton In this post, we look at the process for capturing the latest event experience across multiple products in Adobe Experience Platform. We also dive into how this technique can be used to create dynamic list segmentation for these products. Data models can sometimes be structured in such a way where you can track different types of events in one schema/dataset. For example, this might be a single dataset that has all subscriptions for newsletters or subscriptions. The data structure might be common, but you have many newsletters across many products with differing statuses over time. When subscribe and unsubscribe events are tracked as individual events, it is common to want to know what the current state is so that you can deliver the next best customer experience. To address this, we considered two approaches during implementation for a customer: Track the current state on an Array on the profile Use a segment against the

Authors: Alexander Falca, Constantin Scacun, Eleanore Jin, Douglas Paton This blog is next in the series of how Pipeline powers Stream Processing in the Adobe Experience Platform. We take a deeper technical look into how we approached Stream Computing and unlocked it as a service for our clients. Introducing Adobe's streaming compute framework: Smarts Adobe Experience Platform Pipeline processes roughly 15 billion events a day. While this is an impressive number from a technology point of view, each one of these events needs to be processed in a way that is meaningful to our customers. The problem was that the sheer volume of events creates a huge amount of manual work for people. Along with the manual aspect of the work, it was virtually impossible to do any of the work, without the involvement of a developer who could produce the code necessary to properly process and filter the events. This created a situation that was burdensome and time-consuming for our customers. This led to cu

Authors: Richard Ding, Tamal Biswas, Hitesh Shah, and Steven Sit The following is a summary of how we deployed an orchestration service using Apache Airflow for Adobe Experience Platform. Modern big data applications need to connect to many different backend services and build sophisticated data pipelines or workflows. These workflows need to be deployed, monitored, and run either on regular schedules or triggered by external events. Adobe Experience Platform component services needed an orchestration service to enable their users to author, schedule, and monitor complex hierarchical (including sequential and parallel) workflows for Apache Spark (TM) and non-Spark jobs. What is the Adobe Experience Platform orchestration service? We have built an orchestration service to meet Adobe Experience Platform requirements. It is architected based on a guiding principle to leverage an off-the-shelf, open-source orchestration engine that is abstracted to other services through an API, and extend

Hey folks, Did you get your sandboxes up and enabled? If you hadn’t, get it done by this post. Standardization and interoperability are key concepts behind Adobe Experience Platform. To ensure this we have XDM, schemas, datasets and mixins. Let’s understand them as Experience Data Model (XDM) Experience Data Model (XDM) is an open-source framework that uses standard schemas to unify data for use with Experience Platform and Adobe Experience Cloud applications. XDM standardizes how data is structured and speeds up and simplifies the process of gaining insights from massive amounts of data. Schema: A schema is a set of rules that represent and validate the structure and format of data. A schema is comprised of a class and optional field group(s) and is used to create datasets and datastreams. Data stream: A data stream is a set or collection of messages which share the same schema and are sent by the same source. Dataset: A dataset is a storage and management construct for a collect

This post is part of a series about auto-taggingIn this article I will describe how to create your views for your Adobe Launch extension. Extensions are a way to extend your tagging implementation to provide reusable content for your tagging team to use in all your Adobe Launch containers.When building a private or public extension, you will be given the option to provide a configuration view for your extension or extension feature. While it is optional to provide a configuration, I will advise you to always choose this option.As a best practice it is advised to add a view when creating a data element or a condition or a rule or an extension. Even if you are not planning to return a settings object, a view should be used to provide additional details about the feature.Going forward I will consider that you have already ran the following command and answered yes to the question about the configuration view.npx @adobe/reactor-scaffold What does the scaffold command doWhen

This post is part of a series about auto-taggingAdobe Launch release process is by design simple. This simplicity sometimes comes at a cost as quality checks are often missing before code goes to production. You should also have tagging and coding standards set up to facilitate the release process.Peer reviewAdobe Launch publishing process is built in a way that your build should be approved before being pushed to production. During this approval process, you should have one of your tagging peers to review the build and validate that the tagging and coding standards are being followed.You should also use a tool like JIRA to document the peer review process and only if an "approved" comment is present should you then release to production.Release typesWhile it is possible to deploy Adobe Launch build when and how you see fit, it is a good idea to understand when the best time is to deploy sensitive changes to the website. This will minimise the impact of any issues.N

This post is part of a series about auto-taggingAdobe Launch TMS allows you to use built in features to deploy tags on your website. In some instances, you will be required to write some JavaScript custom code as the tagging features are not enough to achieve your requirements.By injecting JavaScript code directly on the website, there is always risks that your changes can bring a functionality or the whole website down.Several best practices should be followed by your tagging team to minimize these risks.JavaScript Style GuideYou should always first check inside your organisation if a JavaScript style guide has been defined. If there is one it is always a better choice to use your organization one than to use an external one.If there is none then you can try to adopt one that is shared online. In most cases your team will not have enough skills or knowledge in JavaScript to define one from scratch. One safe choice is to use the one defined by Airbnb.try/catchIt is acceptable for

Hello Everyone, We are closing year on a note of growing with learnings; FridayFinding being one of such effort. Thank you Finders who were part of this journey and many more to come. A big shoutout to @karandhawan @ankita_sodhi @skand for their consistent efforts in content and we have winner Jacob Miller who had been sharing his observations! Congratulations @jacob-dddev and big thank for your observations! Hope you enjoy the swag 🙂 Cheers, Nimasha

Hello Finders,    Use this master thread for learning through all the published FridayFindings.   Introducing #FridayFindings with Adobe Experience Platform | 1 | Lets grow together FridayFinding | 2 | User Permissions and Sandbox Management FridayFinding | 3 | XDM, schema, and datasets FridayFinding | 4 | Data Ingestion - Sources; data stream FridayFinding | 5 | Web SDK FridayFinding | 6 | Profiles, Identity UI and Namespace FridayFinding | 7 | RTCDP and destinations FridayFinding | 8 | Alerts FridayFinding |9| Journey Orchestration     Cheers, Nimasha

Hello Everyone, To recognize and reward the top contributors of Platform Experience Community, we are starting a new initiative to give back our top contributors by a token of ThankYou. Every month, A top user would be selected from PlatformExperience and its sub communities with maximum posts answering queries, generating ideas, or initiating discussions. Going forward, blogging could be another way of growth. While we hope this token of appreciation motivates you to give back to other members, we do hope that you already enjoy networking in community.   Score Board of Contributors of the months award Season 1 S.No. Contributor name Username Award Score Level Victory Months 1 Pardeep Subramanian @pradeep_nextrow 1 Level 4 December, 2021 2 Sneha Parmar  @ parmarsneha 1 Level 2 Janurary, 2022 3 Yu Hui Balasingam-chow @yuhuisg 2 Community Advisor Febrarury, 2022 April, 2022 4 Jayakrishna P @jayakrishnaaparthasarathy 2 Level 3 Febrarury, 2022 March,2022 5 M

Hello Finders,   This will be last learning of this season’s Friday finding. Don't forget to share your observations, learning or findings to win the exclusive swag.   Journey Optimizer allow you to build real-time orchestration use cases leveraging contextual data stored in events or data sources. Adobe Journey Optimizer helps companies to deliver connected, contextual, and personalized experiences to their customers. The customer journey is the entire process of a customer’s interactions with the brand, from the first moment of contact until the customer leaves. It starts with the awareness phase, where the customer learns about the brand and starts engaging. The customer will then further interact with the brand, visit online and physical sites, and make purchases, send messages, or post reviews. Adobe Journey Optimizer is built natively on the Adobe Experience Platform and combines a unified, real-time customer profile, an API-first open framework, centralized offer decis

Authors: Erin Davis, Russell Stringham, along with several product managers and engineers across Adobe who contributed to these cookie updates What can I gain from reading this article? Starting February 4, 2020, Chrome 80 will treat cookies with no SameSite value as SameSite = Lax, a setting that prevents a cookie from being used in a 3rd-party context, or "cross-site." Chrome will require developers to set any cross-site cookies to SameSite = None and label them as secure. New or existing cross-site cookies without proper labeling and the secure attribute for cross-site cookies will be unusable on Chrome 80 and above. Adobe standard visitor cookies for Analytics, Target, Experience Cloud Identity Service (ECID), Audience Manager, Advertising Cloud, Bizible and Marketo Munchkin will include the necessary labeling by early January. Most updates are in production today. Adobe cookie updates are handled via Adobe servers; no JavaScript library updates are needed by our customers. Custo

Hello Finders, We are in last leg of growing with Platform Experience, till now we have got idea of basic working of Platform experience, how we can know our customer behavior and identify the patterns leading to the behavior.  Today we will talk about Alerts. Adobe Experience Platform allows you to subscribe to event-based alerts regarding Adobe Experience Platform activities. Alerts reduce or eliminate the need to poll the Observability Insights API in order to check if a job has completed, if a certain milestone within a workflow has been reached, or if any errors have occurred. Read all about Alerts from here. Adobe Experience Platform provides several predefined alert rules that you can enable for your organization. Checkout the Adobe provided alert rules from here. Let’s relate all of them in “what to do” To get started, select Alerts in the left navigation. The Browse tab lists the available rules that may trigger an alert. Select a rule from the list to

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 

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