Adobe Experience Platform

Hi Everyone, Exciting news! We have a new UX team at Workfront dedicated to improving the connection of the platform to itself, and I'm helping with the team's first initiative. We are interested in talking to people in marketing organizations about the way you hand work from one person to another during a campaign. Please note that to participate in this study, you do not need to use Workfront! We are interested in speaking to both non-Workfront and Workfront customers about how you coordinate your work across DX products.  If you're interested in speaking to me and the new UX Platform Architect, Dan, please sign up using this link: https://calendly.com/wf-product-and-design-research/marketing-work-orchestrationPlease note that we may need to schedule a follow-up session depending on how much we get through in your first sign-up. Additionally, if you know of any other team members within your marketing organization who you think would be great f

Authors: @mbroom, @johnba12, @agregg, @danny-miller  Website personalization is one of the most popular use-cases we see our customers getting value out of with Real-time CDP segments. As our customers move towards a CDP, they are looking for ways to move more areas of their MarTech stack towards a centralized place on the CDP. As they do this, they want to incorporate it into the various activation touchpoints.   We are always answering questions about the best ways to activate RT-CDP segments specifically with Adobe Target—and this is because there are a lot of different ways to do this. Each method of activating your segments to Target has different strategy considerations and pre-requisites. We’re going to set the record straight and walk through all these different options so you can choose the best integration method to power your personalized experiences.   Personalization Connection via RTCDP Destinations  This relatively new option is a pers

Welcome to the 2nd edition of the Adobe Platform Experience Community Lens! Adobe Platform Experience Community Lens is like your community bulletin board highlighting the latest updates from the Adobe Platform Experience Community in one place. In this edition, we are sharing updates from August 2022, including, the most viewed Adobe Platform Experience content on Experience League, as well as the latest product releases, upcoming and past learning opportunities, and a lot more! Adobe Platform Experience Community Lens LATEST RELEASES Learn about all the new capabilities, upgrades, improvements, and fixes that were included in the latest release for Adobe Platform Experience: Artificial Intelligence and Machine Learning Services : AI/ML services empower marketing analysts and practitioners to leverage the power of artificial intelligence and machine learning in customer experience use cases. Attribution AI: Attribution AI is used to attribute credits to touchpoints leading to convers

Authors: @mbroom, @agregg, @danny-miller While a lot of focus in AEP is on the Real Time CDP (Customer Data Platform) and the Profile, we wanted to dive into the next area of AEP that is often overlooked or given little attention. Segments. While the Profile is the foundation for who a customer is or does, the way in which we activate them is mostly based on the segments they are a part of. For example, I want to send an email to people who abandoned cart or personalize my site for those who previously purchased a product.  Thus, we want to dive into several intriguing ways segments are being used as they are more interesting than when they first appear.  What are Segments? In its most basic form, a segment is a set of rules that evaluate and store the result/qualification of those rules on the Profile. Rules The rules are a set of criteria that describe a characteristic or behavior. It fundamentally is composed of: Characteristics of the Pr

Hello Everyone,   Calling out interests in AEP certifications. Will discuss details later.   Category 1: I am certified. Shout your name and certification. Category 2: I want to be certified. What certification are you looking for?    Need details, lets know. Keep watching the thread!   Cheers, Nimasha 

How do I get multiple libraries built for one environment?Currently when I have 2 libraries in my development environment I can't build either and get publish errors like 'Could not find Extension for "core::events::library-loaded"'I also couldn't push more than one into staging. If I remove the extra library I can then go about my business as usual. If this is expected behaviour please raise this as a feature. If it's unexpected I'll raise with customer care.

Use this thread to ask any questions related to the Experience League LIVE session titled, "Ask the experts: Useful extensions in Tags (Launch) to help super charge the Web SDK." Experts are monitoring this thread to ensure your questions are answered. Thanks and we hope to hear from you!

Are you using the Akamai hosting option for your Launch libraries? If the answer is yes, then this post is for you!We have been working with Akamai to implement cache control headers on DTM and Launch libraries. This functionality is now in production for both Adobe and Akamai. This means that all production libraries hosted on Akamai will now have a cache request of 60 min included in the header. However, this still a request and is up to the browser to respect the request.Previously, we were not setting the cache control request, so browsers would make their own caching decisions, which lead to unexpected results occasionally.If you are using Launch, there may be action required to fully deploy this feature. Your production library will have a request of 60 min without any action on your part. However, development and staging libraries for Launch will need to have either "-development" or "-staging" in their filename. If they do not, their cache control will be set to 60 min instead

Use this thread to ask any questions related to the Experience League LIVE session titled, "Ask the experts: Useful extensions in Tags (Launch) to help super charge the Web SDK." Experts are monitoring this thread to ensure your questions are answered. Thanks and we hope to hear from you!

Original article   Feature Flags or Feature Toggle is a common practice used by developers. It allows to deploy specific functionalities in an incremental manner and only enable them when needed. In the tagging world feature flags is a little-known concept. Most of the time a standard tagging release will consist of creating the tag, testing it with the tag management system dev endpoint then publishing it to production. This means that sometimes the release timing is crucial as it needs literally to be done at the same time as the new platform feature has been released to production so it does not impact user experience. What are feature flags? Feature flags are a development concept that allows to wrap a functionality inside an if condition that checks a specific variable value. This variable is usually a Boolean, so the possible values are either true for enable my feature or false for disable my feature. This allows the development team to deploy

Welcome to the 1st edition of the Adobe Experience Platform Community Lens! Adobe Experience Platform Community Lens is like your community bulletin board highlighting the latest updates from the Adobe Experience Platform Community in one place. In this edition, we are sharing updates from July 2022, including, the most viewed Adobe Experience Platform content on Experience League, as well as the latest product releases, upcoming and past learning opportunities, and a lot more!   Adobe Experience Platform Community Lens LATEST RELEASES Learn about all the new capabilities, upgrades, improvements, and fixes that were included in the latest release for Adobe Experience Platform: Dashboards: Adobe Experience Platform provides multiple dashboards through which you can view important information about your organization’s data, as captured during daily snapshots. Data collection: Adobe Experience Platform provides multiple dashboards through which you can view important information abo

All the Adobe experience cloud customers would soon be provisioned to AEP and features of AEP for no extra cost. Several foundational Experience Platform capabilities will now be provisioned to every Experience Cloud customer Below are the features that will be part of this Assurance Datastreams Experience Data Models/XDM Schemas Identity Namespace Places Service Privacy Service Note that, features and applications built on AEP like Event Forwarding, AJO, and CJA will still need to be provisioned separately and are billable services. You can reach out to your account manager on the same for costing and provisioning Adobe Experience Platform Data Collection (our tag management solution, formerly called Launch) will continue to appear as its own separate product card. You will soon be seeing the Adobe experience platform in your admin console with all the above capabilities as well if you are an Adobe experience cloud customer as a separate product card. Isn't it exciting!&nb

I have divided the implementation into 6 steps. While the first three steps are very well explained on our official documentation. I would concentrate from step 4 onwards These are the documentation links for the first three steps Create Schema https://experienceleague.adobe.com/docs/platform-learn/tutorials/schemas/create-schemas.html?lang=en Create Datastream https://experienceleague.adobe.com/docs/experience-platform/edge/datastreams/overview.html?lang=en One additional step is that along with other services, like Adobe analytics, I would need to select Even forwarding as well. For example, I want to send data to non-adobe solutions through event forwarding as well along with Adobe Analytics Install Web SDK Extension https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/tags-configuration/install-web-sdk.html?lang=en Create Even Forwarding Property If your org is provisioned for Event Forwarding, you should be able to see the option "Event Forwarding" in Launch

Hello Community Advisors/Advocates,   Thanks for joining the product call with Senior PM Abhishek where he walked us through framework to enable frictionless and quick ingestion of data in any format from any data source.   This is a contextual thread to post your queries which will be answered by internal AEP experts.  Cheers  Nimasha

Join us for first Adobe Experience Community QnA Coffee Break taking place on 21st July,22. There will be livestream session where our AEP experts Eric Matisoff, Rudi Shumpert and Jeff Chasin will provide a deeper dive into Adobe's advanced data collection capabilities.  It will be followed by coffee break with Travis Jordan, Senior Product manager in digital experience. Coffee breaks are live threads which are answers instantly by the experts. Details of live stream session -> here Coffee break Timings  21st July @ 10:00 AM PDT/10:30 PM IST How to participate in Coffee break  Must be signed into the Community during the 1-hour period  Must post a Question about Adobe Experience Platform THAT'S IT!  *(think of this as the Adobe Experience Platform Community equivalent of an AMA, (“Ask Me Anything”), and bring your best speed-typing game)  Instructions Click the blue “Reply” button at the bottom right corner of this post Begin your

Authors: @danny-miller @mbroom Introduction Have you been in the segmentation builder, saw the option to create a container, and wondered how exactly that works? As you will see, sometimes they can be simple (quite literally), and sometimes they can be a little more complicated.The other day, I was working on some segments for Season Ticket Holders.  We were trying to get the logic correct and noticed some fields had containers, while others didn’t.  My curiosity got the best of me, and I started diving into what containers are and how do they work? ContainersWhen creating segments in the RTCDP Segmentation Builder, there are multiple ways to group together rules to create a segment. Containers allow control over the order of execution using nested queries.https://experienceleague.adobe.com/docs/experience-platform/segmentation/ui/segment-builder.html?lang=en#containers Simple ContainersSimple Containers allow users to build a nested query using

Our Adobe Experience cloud communities are the heartbeat that connect, engage, and empower our users to create game-changing digital experiences for their customers. We onboard Advisors every quarter into the program.  Today, I'm thrilled to announce the Community Advisors, class of 2022. During their tenure, Advisors will participate in speaking engagements, provide product feedback, and most importantly, share their expertise with the Experience League/ Marketo/workfront Community.The Advisor program is designed to promote career growth and develop deep connections with users by giving them a voice in the broader customer ecosystem.     Announcement on Adobe blog  🎉🎉   Congratulations to the class of 2022 🎉🎉

Use this thread to ask any questions related to the Experience League LIVE session titled "Ask the experts: Real-Time CDP Connections."  Experts are monitoring this thread to ensure your questions are answered. Thanks and we hope to hear from you!

Use this thread to ask any questions related to the Experience League LIVE session titled, "Ask the experts: The basics of Web SDK." Experts are monitoring this thread to ensure your questions are answered. Thanks and we hope to hear from you!

This post is part of a series about auto-taggingTagging Standards will allow you to set up a set of rules for your tagging team members to follow. By following them we will ensure that the content of your Adobe Launch container is secure, maintainable, and reusable.Naming ConventionAs a member of the tagging team, a big part of your daily job involves working inside the Adobe Launch interface. Without proper naming, you will soon realize that it is very difficult to maintain over time. Example of good naming convention:use camelCase when possible. This is particularly useful for data elements and direct call rules. Try to avoid snake_case or PascalCasenever use a single character to describe the web property, rule, data element, or a buildnever use trailing or leading underscores (except if it refers to_satellite object)acronyms and initialisms should always be capitalized or all lowercaseinactive rules and data elements should be prepended by zzz so you can filter

As AEP dynamically evolves, getting used to all the terms at once can be tough. Here are few links I find useful, have you come across any other docs with the same usage? https://experienceleague.adobe.com/docs/experience-platform/landing/glossary.htmlhttps://jimalytics.com/adobe-experience-platform/adobe-experience-platform-aep-dictionary/

Author: Klaasjan Tukker In the past couple of months, I spent a significant amount of time with our technical sales and consulting organization at Adobe, to bring them up to speed on the power and capabilities of Adobe Experience Platform. Experience Platform operates two "brains" that are connected with each other. First, an analytical brain, to store and process a huge amount of analytical data, run machine-learning with Data Science Workspace, query the data with Query Service. The second brain is the Real-Time Customer Profile, which is optimized to power real-time experiences at scale. This real-time Customer Profile is at the heart of Adobe Experience Platform and has several very unique features. How do you simply explain this complex system? During the workshops, I developed a simple analogy, where I used sticky notes to explain the concept of the real-time Customer Profile. Attendees were given sticky notes and asked to write down the answers to a number of questions. Let me

Author: Brandon Poyfair Location is the most personal context for designing and delivering personalized experiences. Understanding where your users are fundamentally changes how you understand and engage with them. Experience Platform Location Service enables your mobile apps with location intelligence while maintaining privacy sensitivity for your users. You can use the Location Service to Send a real time notification when someone is near your store to drive foot traffic. Segment an audience of health conscious users based on frequency of visits to gyms and health food stores. Personalize an in-store experience. Analyze where users are most likely to use certain features. Increase engagement by limiting touch points to contextually relevant settings. Dynamic point of interest database management The point of interest (POI) database allows you to easily create and manage geofences unique to your organization. This can be done in our product interfa

Authors: Anand Phatak, Nipun Nair, Anshuman Nangia, and Dave Weinstein A summary of how we deployed a single enterprise-level message bus ("Pipeline") using Kafka for Adobe Experience Platform, from our presentation at Kafka Summit 2018 in San Francisco. Over the last decade, the expectations for data processing at scale have changed dramatically. Data collection and processing have moved from being a largely batch-oriented affair to requiring fully streaming methodologies. This change has been driven by the needs of companies to work on high-velocity data and respond to changes in customer behavior and demand in seconds, not days and hours. The aggregation, enrichment, and near-real-time analysis of high-frequency data present a whole new set of challenges. Particularly when the goal is to take data collected at any experience point, derive insights, and then deliver the next best experience at the speed customers demand, tying multiple messaging systems together is a non-starter. To

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