Adobe Experience Manager

Please build API where you can store the user activity from 12 months to var node and so that based on that we can able to identify the how many active users are there from past 12 months. 

Thank you to Jyothitha Chandran (Product Manager) and Mayank Gaur (Senior Product Manager), for a great session exploring how AEM Dynamic Media and Adobe Journey Optimizer work together to deliver personalized experiences at scale. We appreciate all the insights, demos, and roadmap updates! Session SummaryMayank and Jyothitha demonstrated how teams can create and manage Dynamic Media templates and bring them into AJO to build personalized, reusable content for omnichannel campaigns. The team showcased how AJO can combine profile and external data for real-time personalization, dynamically tailoring elements such as product names, prices, images, and regional content. Mayank shared a look at the product roadmap, including deeper Dynamic Media integration within the AJO email designer, expanded open-time personalization, and AI-assisted workflows, while gathering customer feedback to help shape future capabilities. Session MaterialsSlide Deck Webinar Recording Consolidated Q&A Additi

Just been going through some of the announcements from Adobe Summit 2026 around AEM as a Cloud Service and wanted to get a real-world pulse from folks actually building on it day to day.A few things I’ve been thinking about after working on enterprise AEM Cloud implementations:The Edge Delivery Services push is getting louder but I’m curious how many teams are actually migrating existing Sites implementations versus greenfield only. In practice the replatforming effort is significant and I haven’t seen a clean story for brownfield migrations yet.Universal Editor is getting a lot of attention but author adoption in enterprise environments has been mixed in my experience. Has anyone actually rolled it out to a large non-technical authoring team and how did that go?On the pipeline and CI/CD side, Cloud Manager has improved but environment promotion still feels like it needs work especially around content variable management across stages.Would love to hear from others are these things you

Adobe Summit 2026 is packed with innovation across AEM, Agentic AI, LLM Optimization, DAM, Forms, Brand Concierge, and more. To make it easy for everyone, we’ve created one single, complete list of all AEM-related sessions in one place, so you can:Quickly scan everything Plan your schedule Share with your team Register directly Bookmark this post for recordings (they’ll be available at the same links after Summit)How to Use This PostClick the session title to go directly to the Summit catalog  Register from there After Summit, revisit the same link to access recordings (when available) Share this page with peers so no one misses outSession Title Session Description Schedule Location Speakers Session Type L335 – Build An Experience in Adobe Experience Manager the Agentic Way Generate new sites and features faster by leveraging generative AI in Adobe Experience Manager to transform specs into websites in hours. 2026-04-20 • 9:30 AM–11:00 AM • 90 min Marcello 2 Gabriel

You’re invited to The Skill Exchange 2026, a free virtual event running August 5-6 and August 11-13. Looking to sharpen your Adobe skills, discover new ways to work smarter with AI, and learn directly from Adobe experts and customers? This is the event for you! Skill Exchange 2026 registration is officially open! 🚀  Join us for:✨ Expert-led sessions across 7 Adobe solutions  🤖 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 AEM Sessions are on Wednesday, August 12th!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 AEMaaCS does NOT offer an efficient way to create a set of pages from different hierarchies of the website which should be sent to translation in multiple target languages.If you have one page you can use the SITES console to create a translation project, also here the option is to include their subpages. But if you need to create a package of pages which are stored in different hierarchies of the website structure, you need to go to Projects > Translation Project and you need to add those pages to EACH target language that you have. Let’s say you have 30 languages of your website - so you need to do this adding of pages 30 times!This manual task is NOT efficient at all and takes a lot of time!AEMaaCS as an enterprise CMS should offer a smart way so that you have to do the selection just one time and then just select the target languages that apply. Current situation is more than disappointing!

Hello,I am trying to work on allowing the Adobe Creative Cloud on our network and am looking for the minimum required list just to authenticate via the Creative Cloud and use Premiere Pro. Our network & security teams are very strict on what gets whitelisted and will question if there are 10+ domains added to a request.What is the bare minimum to just allow us to log into creative cloud and use Premiere Pro?Thank you

We're excited to partner with the Adobe AEM Customer Success team for a 4-part event series to help teams turn AEM Assets from a repository into a true part of the marketing operating model.Across these sessions, you'll build a working understanding of Adobe Experience Manager Assets - including how it supports content reuse, governance, collaboration, and omnichannel activation. Whether you're a marketer or work alongside one, you'll come away knowing not just what AEM Assets does, but how it helps your team find approved content faster, improve consistency, reduce duplication, and support business goals across every channelEach session will offer a mix of live presentation, demo, Q&A, and more: Sessions include:  August 19 - From Content Chaos to Content Reuse: How Marketing Teams Move Faster with AEM Assets September 2 - Find It. Trust It. Reuse It. The Power of Metadata, Taxonomy, and Governance ( ​@DanaPoliti ) September 16 - The Right Access for the Right Teams: Designing

I’ve been experimenting with Playwright for testing the AEM authoring experience — not just the rendered pages.A few interesting issues surfaced that component/rendering tests simply wouldn’t catch:Dialog validation that didn’t match the field description A field that silently accepted an invalid configuration Rich-text input losing characters Test cleanup failing because of browser/API session differences Shared/included dialog fields that were easy to miss in component-based test coverageThese bugs lived in the authoring interaction — the clicks, typing, dialog state and sequence of actions an author actually performs.I wrote up the lessons learned, including some of the Playwright patterns that worked (and the ones that didn't 😄):👉 Testing the Click, Not the RenderCurious how others are approaching automated testing of the AEM authoring experience. Are you testing the editor UI today, or mainly the rendered output?

I made the following observation:In the Designer (FormDesigner.exe) for interactive forms, the preview window remained blank.Although the AcroRd32.exe process was launched in the background and the temporary PDF was created in %TEMP%, it was not displayed.A quick analysis revealed that the Windows Update KB5121003 had been installed the day before.Once it had been uninstalled, the problem was resolved.Is this behaviour known?

Dear AEM Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with AEM.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for August 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 AEM. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEM-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 – empowering you to provide a truly personalized experience to your customers with AEM.Start supercharging your problem-solving skills today by exploring our Top KCS Articles!Take a look:

Thank you to Karthik Muralidharan, Director, Strategy and Product Marketing, for the insightful presentation and demo on Adobe Brand Visibility! So many exciting things coming to the Generative Engine Optimization space!If you missed out, or want to replay the session, check out the links below:Slides Webinar Recording Check out the product yourself: play.bv.nowFeel free to use this space to keep the conversation going! Add your thoughts, follow-up questions or takeaways here and maybe let us know what feature you’re most excited about.If you missed it, check out the session we did in July with Darrel Smith from WK Kellogg and Emily Kellman-Kessel from Adobe.com. They shared their experiences of marketing in the world of AI. Also, save the date for September 22, for our next AI Search and Discovery Forum session – registration link coming soon!

If your team is planning (or mid-way through) a migration from on-prem AEM or AMS to AEM as a Cloud Service, here's a rundown of the things that tend to blindside people beyond what's in Adobe's official migration docs.1. The "no full read/write access to the repo" shift is bigger than it soundsOn-prem, you got used to poking around CRXDE Lite, hotfixing content in prod, or running ad-hoc Groovy scripts against the JCR. Cloud Service locks that down hard no CRXDE Lite in prod, no direct repo shell access. Everything has to go through code, content packages, or the Cloud Manager pipeline. Teams that relied on "just SSH in and fix it" workflows need to rebuild that muscle memory around proper CI/CD and content sync tooling months before cutover, not during it.2. Cloud Manager's code quality gates will fail builds you didn't know were brokenCloud Manager runs static analysis (Sonar-based rules) on every build, and it's stricter than most teams expect. Common failures:Deprecated APIs (Reso

🗣 Looking to continue the conversation after Experience Makers The Skill Exchange? The conversation isn't over.At Skill Exchange on August 12, AEM experts ​@ghowell15 and ​@pstolmar will take the stage — Gary with Scaling Content Creation with Product Launch Accelerator and Generative AI and Peter with Scalable Content Workflows for Authoring and Asset Governance. Afterwards, they'll host an open office hour built for one purpose: to keep that dialogue going with you.This is your chance to bring the questions you don't get to ask live, the use case you're still working through, or the challenge you hit the moment you tried applying what you learned. Come with your real-world scenarios — Gary and Peter will be here to work through them live.What you'll walk away withDirect answers from two AEM experts on scaling content creation with generative AI and building governed, scalable authoring workflows — grounded in what they're seeing in real implementations, not just theory Practical nex

🗣 Looking to continue the conversation after Experience Makers The Skill Exchange? The conversation isn't over.At The Skill Exchange on August 12, AEM Champions ​@BrettBirschbach and ​@venkatkrishnat will take the stage — Brett with Leveraging AI in AEM Cloud Service Development and Venkat with Content Authoring Evolution and Best Practices. Afterwards, they'll host an open office hour built for one purpose: to keep that dialogue going with you.This isn't a repeat of their sessions. It's your chance to bring the questions you don't get to ask live, the use case you're still working through, or the challenge you hit the moment you tried applying what you learned. Come with your real-world scenarios — Brett and Venkat will be here to work through them live.What you'll walk away withDirect answers from two AEM Champions on applying AI to AEM Cloud Service development and modernizing content authoring — grounded in what they're seeing in real implementations, not just theory Practical nex

Big news for the AEM community! 🎉 Adobe User Groups now have a unified home — and that means it's never been easier to find your people. Whether you're just getting started with AEM or you've been in the ecosystem for years, there's a local or virtual chapter where you can connect, learn, and grow alongside fellow users. What's new: ✅ One destination for all Adobe User Groups across Adobe Experience Manager, Adobe Experience Platform, Adobe Analytics, Adobe Commerce, Adobe Marketo Engage, and Adobe Workfront ✅ Increased event options around a multitude of topics and global locations ✅  More community-building opportunities within the Adobe CX Enterprise ecosystem  How to get started: Learn more about the new experience from our Community Pulse blog:  Find an Adobe User Group chapter near you 👉 https://usergroups.adobe.com/?cgen=1K8FD178&mv=other 

Been thinking about this a lot lately, and curious how other AEM teams are approaching it.For years, we've poured effort into hardening the perimeter around our AEM environments — VDIs, VPNs, SSO, locked-down repos, strict PR gates. Classic castle-and-moat thinking: keep the outside out.But here's what's nagging at me: with AI coding agents now part of the daily workflow, files like CLAUDE.md, AGENTS.md, and .cursorrules have quietly become some of the most information-dense documents in the repo. Dispatcher configs, content fragment models, component architecture, business logic — plain-English descriptions of exactly how the system works.And that's the actual problem: these files usually don't get the same treatment as code. They're committed casually, reviewed loosely (if at all), and often live at the repo root where any contributor — human or AI agent — can read them. Unlike obfuscated code or config buried three folders deep, this is a plain-English map of your system: auth flows

⭐⭐ Congratulations to ​@ghowell15, AEM Champion of the Month! ⭐⭐Gary is one of those Champions who doesn’t just support his greater AEM community, but shows up and shows out for his fellow AEM Champions. Whether it’s stepping up to lead a session at The Skill Exchange, partnering with other Champions and Adobe Product team members on Perspectives articles, or actively participating at a Champion social event, Gary is a true pillar within the Adobe Champion community, and we wouldn’t be as strong without his leadership, dedication, and positive attitude.Want to see Gary in action? Check out his Skill Exchange session, “Scaling Content Creation with Product Launch Accelerator and Generative AI" on Wednesday, August 12 at 10:30am PT: https://reg.adobe.com/flow/adobe/skillx26/landingpage?source=COMMUNITY&sdid=Y2KRGJ1X

🙌 Congratulations to ​@gkalyan, AEM Champion of the Month - June 2026! 👏 🏅 Kalyan has gone above-and-beyond in the last year as an AEM Champion, stepping into multiple leadership roles in the AEM User Group Program, internal Adobe product feedback sessions, and Community advisory. He regularly raises his hand to help mentor new and existing customers and serve as an advocate of the Adobe CX Enterprise ecosystem, including as a speaker at internal and external Adobe events like Adobe Summit. Please join us in congratulating Kalyan for this impressive achievement!

In AEM as a Cloud Service (AEMaaCS), the out-of-the-box (OOTB) CIF component Commerce Retriever APIs currently return Optional.empty() for both a successful GraphQL query that yields zero products and an execution failure (such as timeouts, HTTP 429s, or transient connectivity issues).Because both scenarios produce the exact same return value, custom implementations have no supported way to differentiate between them. This prevents us from delivering a tailored user experience, such as showing a "No products found" message versus a "Service temporarily unavailable" retry prompt.Proposed Implementation Approaches (Flexible):We leave the exact contract to Adobe Engineering's discretion, but viable options include:- Exposing a separate error object or status indicator.- Throwing a specific checked or unchecked exception on execution failure rather than swallowing it into an empty Optional.- Providing a metadata wrapper alongside the result.

What a fabulous discussion yesterday! Many thanks to Darrel Smith from WK Kellogg and Emily Kellman-Kessel from Adobe.com for sharing their experiences and insights on Generative Engine Optimization (GEO), as well as to our moderator, Karthik Muralidharan, for keeping the conversation flowing and engaging!If you missed it or what to revisit any part of the session, you can access everything below:Slide Deck PDF Webinar Recording Also, don’t miss out on our follow-up session on August 20. AI Search and Discovery Forum: Inside the Future of Brand Visibility. We’ll review the roadmap, recently released capabilities, customer success stories, and give an exclusive look at Adobe Brand Visibility. Register now! We’re looking forward to continuing these discussions and learning more from you. What are you seeing in the world of GEO? 👀

Dear AEM Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with AEM.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for July 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 AEM. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEM-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 – empowering you to provide a truly personalized experience to your customers with AEM.Start supercharging your problem-solving skills today by exploring our Top KCS Articles!Take a look:An

Test

Problem: the OOTB Content Fragment component makes every field of a referenced fragment editable in the Universal Editor. There's no supported way to expose some fields (title, body) while protecting others (slug, featured image, metadata owned by other teams). This is the default behaviour, not an edge case.I went down a deep rabbit hole and tried several approaches: The Field Contract Pattern worked: A proxy component whose editables point at the component's own node (so the rail resolves a model I control, not the CF schema), reading the fragment live for display and writing approved fields back via a ResourceChangeListener. Hidden fields simply aren't editables anywhere — enforcement by construction.Full writeup with code: Selective Content Fragment Editing in AEM Universal Editor: Building a Field-Level Editing ContractOpen question for the community and Adobe: is there a supported way to scope the CF schema returned to /details per editing context, or a cancellable pre-persist ex