Adobe Experience Platform

Hello Community,I am preparing to kick-start my journey as an Adobe Experience Platform Analyst. With an analytical mindset and enterprise IT experience, I am drawn to how AEP solves complex data integration, segmentation, and omnichannel activation at scale.To accelerate my growth, I am looking for ways to gain practical exposure: Mentorship & Guidance: Any advice on the ideal roadmap for Adobe certifications (such as the AEP Qualified/Certified Expert paths). Hands-on Exposure: Open to volunteer work, entry-level internships, or shadowing practitioners on implementation use cases. Key Resources: Recommendations on community repos, labs, or documentation beyond standard Experience League tutorials. If you are open to connecting or have advice on where a newcomer should focus their first 90 days, please feel free to drop a comment or reach out directly. Looking forward to learning from this incredible community!

Most orgs running AEMaaCS at scale eventually split into a Platform team (Cloud Manager, pipelines, environment governance) and one or more Product teams (business logic, content). This split is healthy in principle, but in practice it creates constant friction around anything that touches deployment, migrations, bulk content transforms, scripted rule changes, because ownership of “who ships this” isn’t architecturally defined, so it gets negotiated project-by-project.I want to propose a pattern that’s worked well for us and ask whether others have converged on something similar (or better):The core idea: instead of arguing jurisdiction over a piece of work, split the artifact so each team owns a layer they already have legitimate authority over.Platform team owns the engine, a generic, reusable OSGi service deployed once via the standard Cloud Manager pipeline. It knows how to execute a class of change (e.g. template transformation, bulk property migration) but contains no business-sp

Hi AEP Community!Looking to sharpen your Adobe skills, discover new ways to work smarter with AI, and learn directly from Adobe experts and customers? Skill Exchange 2026 registration is officially open! 🚀  Adobe Experience Platform sessions will be held on August 6th, with sessions across 7 Adobe products throughout Aug 5th-13th. A couple sessions you can expect to learn from: One Platform, One Customer Governing at Scale: Building a Trustworthy Data Foundation  Building an Intelligent Activation Layer and Orchestration Drives Results See full Adobe Experience Platform session list here  Join us this August for: ✨ Expert-led sessions across 7 Adobe products 🤖 AI-powered tips and innovations 💡 Real customer stories 🎬 Live demos and practical takeaways you can apply right away 🤝 Opportunities to connect with fellow Experience Makers  Whether you're just getting started or looking to level up your expertise, there's something for everyone.  🎟️ Save your spot today: [Register Now]  

Currently, the native Marketo Engage integration uses Adobe's Sources connector framework & not Data Collection Core Service (DCCS). Data lands in the Data Lake and Real-Time Profile (which is why you can see it in Profile browse), however it never passes through DCCS nor does it create Unitary Events that would be extremely helpful for AJO use cases for triggering journeys based on Marketo engagement events & activities. Especially when we want to designate specific users and/or email addresses for the journeys in AJO when profiles have multiples per profile.Options for workarounds exists, however labor intensive & data heavy.Stand up a streaming ingestion path for the same events, so that they arrive via DCCS/Edge, which AJO B2C can listen to as a Unitary Event. Use AEP Audience (streaming) + Read Audience in AJO B2C, store the trail downloaded email in a lookup dataset either at ingestion time (a field like trail_email) or use Data Distiller to write it on a schedule. La

Dear AEP Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with Adobe Experience Platform.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for June 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for AEP. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEP-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – creating highly personalized digital experiences with AEP.Start supercharging your problem-solving skills today by exploring our Top KCS Articles! Take a look:Custom

 The Problem StatementHow do we connect RT-CDP audience segments with CJA event data to analyze customer journeys, despite differences in identity stitching models and delayed audience data availability? Answer-If you are setting up Adobe Customer Journey Analytics (CJA) along with Real-Time CDP (RT-CDP), you might notice an interesting challenge.Both platforms handle identity stitching in very different ways:RT-CDP builds a real-time Identity Graph to link users across systems. CJA works on fast, query-based analysis using flattened event data (like web/mobile logs).So the key question is:How do these two systems connect?How does an audience created in RT-CDP match perfectly with web or mobile events in CJA?Let’s break it down step by step.Core Concept: Persistent ID vs Person IDWhen you configure a dataset (WebSDK or Mobile) in CJA, you define two important fields:Persistent ID → Identity Graph → Person ID(Raw Input) (Linking) (Final Output) Persistent ID (Input):

Exited to host this even with Adobe AEP Product Manager.Join us for this virtual session where Adobe Product Manager will showcase the latest upgrades, features, and best practices for B2B use cases in Adobe Experience Platform and connect directly with Adobe experts and network with fellow professionals.Event is scheduled on June 24, 2026 at 3 PM CST.Register here: https://bit.ly/4g5Sp0r

I was recently setting up a webinar campaign in Marketo and noticed registration numbers looked a little higher than expected. (In an ideal scenario, I should be happy about it, but contrary to it, I was skeptical!) When I dug into the records, I found that some attendees already existed in the database. Instead of updating those records, a few were being created as new leads because the data from the webinar platform didn't consistently match.What surprised me was how normal the situation was. Nothing was broken. The integration was working. The records just looked different enough to be treated as new people.It reminded me that duplicate leads often come from everyday marketing activities rather than major system issues.Lately, I've been thinking more about preventing duplicates before they enter Marketo instead of cleaning them up later.Some teams handle this with validation rules, while others use Marketo deduplication tools to help standardize and match records earlier in the proc

Adobe Experience Platform provides the foundational capabilities for collecting, unifying, activating, and analyzing customer experience data. But practitioners involved in implementation, production support, QA, migrations, and ongoing enhancements often need to move quickly between Query Service, dataset previews, Real-Time Customer Profile lookup, audience validation, and ingestion workflows.That day-to-day investigation can become difficult when business stakeholder question that requires more than a sample preview or a high-level UI view. Often, it is required to inspect a specific profile with hundreds of its attributes and events, extract and deep dive into a specific dataset, not just a preview and investigate all the profiles included in an audience, a capability not available in current AEP UI. In many cases, the question is not simply whether data exists, but whether the right data exists in the right place and can be validated efficiently.I faced these same challenges while

Dear AEP Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with Adobe Experience Platform.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for May 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for AEP. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEP-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – creating highly personalized digital experiences with AEP.Start supercharging your problem-solving skills today by exploring our Top KCS Articles! Take a look:Blank J

Adobe Commerce performance mistakes I see in almost every auditAfter dozens of Adobe Commerce (Magento) audits across B2C and B2B storefronts, the same culprits keep appearing. And they're not exotic , they're avoidable.MISTAKE #1 : VARNISH MISCONFIGURATIONCache hit ratio under 60% on category/PLP pages.What I find: ESI not set up properly, TTL values too conservative, cache invalidation firing on every CMS save.Fix: Audit your Varnish VCL, separate CMS cache from catalog cache, use hole-punching for cart/account blocks.MISTAKE #2 : SYNCHRONOUS INDEXING IN PRODUCTIONFull reindex triggered on product save, blocking storefront performance.What I find: indexers still set to "Update on Save" instead of "Update by Schedule".Fix: Switch all indexers to schedule mode. Use cron for execution. Use partial indexing wherever supported.MISTAKE #3 : N+1 QUERIES IN CUSTOM MODULESCustom GraphQL resolvers hitting the database once per product in a listing.What I find: Third-party or custom modules byp

A question that comes up frequently when working with shared Field Groups: does marking a field as Primary Identity in one schema affect other schemas using the same Field Group? And how do you handle required fields that don't apply to your specific dataset?These are two separate concerns that get conflated because they both live in the schema layer.Primary Identity is Schema-LocalMarking a field as Primary Identity is a local decision scoped entirely to that schema. It has zero upstream impact on the Field Group definition or any other schema using it.Identity designation and field group constraints are completely separate layers in AEP's Schema Registry:- Field Group = shared blueprint with structural rules (required, data type)- Schema = local implementation including identity role assignmentsField A stays required everywhere because that constraint is defined at the Field Group level. Field B being Primary Identity in Schema X doesn't change anything for other schemas.Handling Req

I had the pleasure of speaking at an Experience League Community AMA at Adobe Summit this year, and I wanted to bring the conversation here for those who couldn’t make it. This is the kind of thing I genuinely wish someone had told me before we started.AEP on AWS  - Summit AMA RecapThe ContextWhen we set out to implement Adobe Experience Platform (AEP), the working assumption was that it would behave like any other cloud deployment. It didn’t. AEP’s defaults around networking, identity models, and tooling integration had been built against a specific cloud environment. That wasn’t documented anywhere, it was something you discovered by running into it. In our case, we discovered it during an architecture review, well into the project, not in a test environment.On top of that, Real-Time CDP and Customer Journey Analytics had to go live at the same time. That meant every foundational decision from schema design, identity resolution to data integration had to be right for two production s

Excited to co-host with  ​@DavidBarnes11 an open AEP / AJO community discussion on March 24 at 11 AM EST.This will be a fully audience-driven session - the challenges, blockers, and ideas we explore will come directly from the people who show up and share their experiences.If you work with Adobe Experience Platform or Adobe Journey Optimizer, bring your toughest questions:• What’s blocking you?• What limits are you hitting?• What do you wish the platform could do better?The goal is simple: learn from each other and tap into the collective knowledge of the community.🔗 Learn more & RSVP:https://lnkd.in/eYfJ8XWC💬 If you want to influence the discussion, message ​@Asheesh_Pandey or ​@DavidBarnes11 with the AEP / AJO challenge that’s keeping you up at night. ​​​​​@NimashaJain ​@Sukrity_Wadhwa @Stephanie Dam

 Product area: Audience builder UI (AEP Audiences / AJO Audiences) — field selection/search, audience enrichment dataset selectionProblem: When creating audiences in the UI (especially when leveraging audience enrichment datasets), the field/dataset picker becomes visually cluttered. Search returns too many similar results with limited ways to narrow or rank them, which slows down audience creation and increases the chance of selecting the wrong attribute/dataset.Request: Enhance the audience builder search experience to support filtering and prioritization so users can quickly find the right fields/datasets and reduce UI clutter.Requested enhancements:Filter by metadata (e.g., dataset, field group/object, namespace, label/tag, data type, source system, enabled for audience enrichment). Include / exclude logic in search (e.g., show items labeled X but exclude items also labeled Y). Prioritization / ranking controls so the most relevant attributes appear first (e.g., allow admins to mar

Dear AEP Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with Adobe Experience Platform.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for April 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for AEP. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEP-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – creating highly personalized digital experiences with AEP.Start supercharging your problem-solving skills today by exploring our Top KCS Articles! Take a look:Custo

I need a correct roadmap to become Adobe Experience Platform developer to prepare my skills

Hello everyone,we are based in Germany and are active users of Adobe Real-Time CDP Data Collaboration. You can find us in Adobe Collaboration as a collaborator.Our current primary Match Key is hashed email addresses from our publishers’ subscriber bases.iq digital media marketing gmbh is the exclusive marketer for leading media brands in Germany, covering general news, business & finance, trade media, and millennial‑focused content. Our portfolio includes well-known websites such as DER SPIEGEL, FAZ.NET, Handelsblatt Online, SZ.de, WirtschaftsWoche Online, and many more.We just startet. So far, we are very happy with the ease of use of Collaboration - and what is further to expect on the timeline here. It is easy to use and straightforward to operate, which we really appreciate. Therefore, we would like to invite advertisers and data providers who are already working with Adobe CDP to start a conversation about this new product (available in Europe since 2026) and to explore potent

Hey everyone — I built a free tool that might save you some time on your next AEP implementation.SynthAEP generates realistic XDM-compliant synthetic data for AEP sandboxes. Instead of manually crafting test profiles and events, you pick a scenario, set parameters, and download ready-to-ingest data.The multi-schema feature is what I'm most proud of: upload 2-5 schemas (mix of profile and event), choose batch or streaming format for each, and get a ZIP with unified data where identities stitch correctly across all datasets. Streaming exports come with Postman collections so you can POST directly to your DCS endpoint.Free tier available, custom/multi schema you can try once per day.aepsynthdata.comWould love to hear what would make this more useful for your workflows. What scenarios should I add? What field groups are missing?

Dear AEP Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with Adobe Experience Platform.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for March 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for AEP. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEP-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – creating highly personalized digital experiences with AEP.Start supercharging your problem-solving skills today by exploring our Top KCS Articles! Take a look:Profi

Hey AEP practitioners, One thing that keeps coming up when I talk to teams across the industry: staying on top of Adobe release notes is genuinely hard. Not because the documentation isn't there - it is - but because carving out time to check it regularly just doesn't happen when day-to-day work takes over. I built DXP Intel to solve exactly that. It monitors release notes across Adobe Experience Cloud solutions weekly, summarises what's new, and surfaces it in one place. You subscribe to the products you care about - Target, AEP, CJA, AJO, whatever's relevant to you - and only get an email when there's actually something new. No noise, no digest of nothing. Check it out → dxpintel.com Happy to hear any feedback - this is early days and I'm actively improving it.

Get certified at Summit - we are ready with expanded testing capacity! Full passholders attending Adobe Summit 2026 can get certified for free by passing an on-site certification exam. All exams (except Adobe ColdFusion and Adobe Captivate) will be available. You may take as many different exams as you like, but you may not take the same exam more than once.  Testing hours are April 19-21 @ 9am-5pm PT and April 22 @ 8am-1pm PT. Seating is first-come, first-served. Find us at the Adobe Certification table on the 5th floor of the Venetian.  You must bring your own fully-charged laptop to take advantage of this offer. Free stable and secure Wi-Fi will be provided.  Learn more today! 

We’re excited to celebrate Björn Koth ​​​@bjoern__koth ), who has been named the 2025 Community Member of the Year for the Adobe Experience Platform community!   Over the past year, Björn has distinguished himself as a trusted and familiar presence in the AEP community, consistently showing up with deep expertise and a strong commitment to helping others succeed. His steady, thoughtful contributions make complex topics easier to navigate and help members move forward with confidence. What makes Björn stand out is the level if care he brings to every interaction. He takes the time to share clear, practical guidance, keeps conversations moving in a positive direction, and creates a space where learning feels approachable and collaborative. Through his consistency, generosity, and community-first mindset, Björn has had a lasting impact on the member experience in the AEP Community and across the Experience League as a whole, making him a natural choice for this recognition. The Community

Background:Working with AEP and connected tools like CJA and AJO for a while now, one thing has become painfully obvious lately: the lack of a useful documentation of the client setup. There may be great yet unofficial community tools out there, but let's be honest, in many cases people using the system may not have the required setup like programming languages (Python or NodeJS) to generate the documentation for themselves, so might require a developer to support them. What I am trying to say is:The Adobe tools are powerful and highly complex to set up, and creating and maintaining client-specific documentation on that is cannot possibly be a manual task. This is surely not sustainable. What I would like to pitch is:We need a Documentation section built into the UI AEP and connected tools, that lets you generate an ad-hoc, standardized documentation as downloadable Excel workbook.This you can then either keep in AEP to be accessible for everyone with access, or decide to download and

Dear community from abroad of USA.For accountant reasons we need a 2026 Certificate of residency of ADOBE INC, usualy published on the company site. I would like to make a subscription. I found here the 2024 Certificate. It is issued by Department of Treasury Philadelphia. for taxplayer Adobe INC. The main text is: “I certify that the above-named corporation is a USA corporation, and a resident of USA for purposes of US taxation. “Can you please direct me how to obtain one ? The virtual assistant dosn’t understand my issue :).