Product Communities

Introduction A little while ago we introduced Simulation Mode — a way to test run a draft journey with lightweight, AJO-native Simulated Users before you ever publish. It was a big step: instead of pulling in AEP test profiles to try out a journey, you could spin up purpose-built test profiles right inside AJO.But Simulation Mode still left one job on your plate: you had to figure out which test users the journey needed, and you had to build each one by hand.The Journey Simulation Agent takes that job off your plate. It reads your journey, works out the minimal set of paths needed to exercise every branch, and uses AI to generate a realistic test user for each one, complete with the profile attribute values that path needs. Then it triggers them into the journey and hands you a single verdict: is this journey ready to publish, or not? No path-tracing, no hand-built profiles, no digging through logs.This post walks through that end-to-end, using an example journey.  The Issue: Hand-Craf

I spoke at the Adobe Summit Experience League Theater AMA series a few weeks ago. For anyone who missed it - or who's been wrestling with the same adoption challenges I keep seeing - here's what I covered. The Adoption CeilingMost Adobe Analytics and CJA implementations eventually hit the same wall. Power users are thriving. Everyone else is frustrated. They don't understand what the dimensions mean, or why some of them have no data. They've stopped trusting the numbers. And whenever they need something, they file a ticket with IT - where it joins a queue.CJA makes this worse before it makes it better. More data sources means more dimensions spanning multiple departments, and most people have no map for any of it. The Lighthouse FrameworkAt Accrease, we've built an approach around this called the Lighthouse Framework. The idea is simple: instead of routing everything to IT, every business unit gets one trusted point of guidance - a 'lighthouse' - who sits in their team, understands the

 The Problem StatementWhen the same customer profile is ingested to multiple Profile-enabled datasets, how does Adobe Experience Platform (AEP) determine which attribute values appear in the Real-Time Customer Profile?More specifically,Does Dataset Precedence behave differently from Timestamp Ordered? Does Batch or Streaming ingestion affect the final profile?Common Understanding of Merge Policies      Most users assume that Timestamp Ordered replaces the entire customer profile with the latest ingested record, while Dataset Precedence always uses all values from the higher-priority dataset. However, AEP merge policies don't work at the record level. Instead, they evaluate individual attributes based on the configured merge policy, often producing results that differ from these common expectations.Let's validate this with a simple test. To understand this behaviour, I created the following setup in Adobe Experience Platform.2 XDM Individual Profile Schemas with same set of attributes P

AJO is the channel marketers already trust to get every communication right — email, push, and SMS, orchestrated from one place. Adobe Target, meanwhile, has been the brain behind your best on-site moments — the right offer, the right visitor, the right second. That intelligence used to stop the instant someone left your site. Not anymore: AJO can now reach out mid-send, pull that same targeting logic straight from Target's Delivery API, and carry it into an email, a push notification, or an SMS — so the trust you've built on-site travels with every message AJO sends. Most teams have solved this the hard way before: rebuilding the recommendation logic inside the messaging tool, keeping two systems in sync by hand, and hoping the "top pick" in tonight's email actually matches what's live on the homepage. AJO closes that gap with Integrations — connect the Target Delivery API once, and any message template can call it at send time. The smartwatch a shopper almost bought yesterday shows u

Adobe Accelerates Agentic AI Adoption Through New Agency and Technology PartnershipsAdobe is expanding its ecosystem of agency, technology, and AI partners to help organizations create, activate, and measure personalized customer experiences at scale. New collaborations with companies including WPP, Accenture, Omnicom, Stagwell's Code and Theory, Anthropic, and Microsoft bring together content, customer data, and AI to help brands deliver more connected, intelligent customer experiences while maintaining governance and brand integrity.Why It MattersAs organizations move from experimenting with AI to operationalizing it across marketing and customer experience workflows, they need a trusted foundation that connects creativity, data, and AI. Adobe's expanding ecosystem helps brands unify paid and owned channels, automate customer experience delivery, and gain deeper insights that drive more relevant engagement and measurable business outcomes.Learn MoreDiscover how Adobe and its ecosyste

Turn Media Network Potential into Performance with Adobe Real-Time CDP CollaborationAs commerce media continues to grow, media networks are under pressure to turn valuable first-party data into scalable advertiser revenue. Adobe Real-Time CDP Collaboration helps media networks connect audience discovery, activation, measurement, and creative workflows in a single privacy-centric solution, making it easier to deliver better targeting, stronger performance insights, and more impactful advertiser experiences.Why It MattersToday's media networks need more than audience access to stand out. Adobe helps organizations scale audience monetization, connect advertisers with valuable first-, second-, and third-party insights, streamline campaign execution, and measure outcomes with greater confidence, all while maintaining strong privacy controls. That’s what Adobe Real-Time CDP Collaboration for Media Networks is built to do. With native connectivity across the Adobe AI Platform, it enables true

 That email from IT we all dread: Urgent: Remediation Required with a list of supposed Marketo config issues found during an external audit. Typically, the issues’ll range from factually false[1] to meaningless[2] to head-shakingly unactionable[3], but there’s sometimes a valid point in there. (Especially if it’s tagged Low Priority so neither side has to get defensive.) A legit point that came up recently is missing DNS CAA records for Marketo LP and Branding (click tracking) domains. The Marketo instances still passed the audit because it was tagged P3 (Low), but there’s good reason to try to make IT happy. What CAA records doCAA records list the specific Certificate Authorities allowed to issue SSL certs for a host. For example, if your company is on AWS with Amazon-issued ACM certs, IT can publish a CAA record that says only Amazon’s CA is allowed to issue certs for example.com and all its subdomains. Any other CA must reject a cert request if they are to stay in good standing with

Hi all! I'm a PM on the Customer Journey Analytics team at Adobe. We've sketched an early concept for exploring multi-level business data in CJA: the kind of structures where things roll up from specific to broad (opportunity ➡️ account ➡️ parent account, SKU ➡️ product line ➡️ category, or region ➡️ market ➡️ store). I'd value input from anyone who works with data shaped like this.The survey asks how you explore those levels today, where it gets painful to find what's actually driving a number, and whether an org-chart-style way of browsing your accounts, products, regions, or campaigns inside Workspace would help. About 4 minutes.Survey: https://survey.adobe.com/jfe/form/SV_5mUPLXYElPn4MQuHappy to post a summary back here once it's compiled, so it's useful to the group and not just to us. And if you'd rather just tell me how you tackle this today, reply in the thread: I'm reading everything. Thank you so much for any time you can spare.

Hi everyone,I wanted to bring up an idea and see if there is interest from the European Workfront community.I’ve noticed that we currently don’t have a dedicated Workfront User Group chapter focused on Europe. I think there could be a great opportunity to create a European chapter - even starting as a virtual group - where Workfront users, admins, and practitioners can connect, exchange ideas, share best practices, discuss challenges, and learn from each other. 🙂Would anyone here be interested in joining or helping shape a Europe-focused Workfront User Group?I’d be happy to help organize, coordinate, and support getting this started if there is enough interest. It would be great to bring together people from different countries and organizations to share experiences and build a stronger Workfront community across Europe! 😎If this sounds interesting, let me know in the comments - would love to hear your thoughts!

Hi everyone,With Adobe Analytics 1.4 APIs deprecating (Aug 2026), the Processing Rules “view” endpoint will no longer be available, and currently there’s no equivalent support in 2.0 APIs.To help with this gap, I built a lightweight Chrome extension called AA Processing Rules Exporter.The extension extracts Processing Rules directly from the Adobe Analytics UI and downloads them in the same 1.4 API JSON format.This can be useful for: Processing Rules documentation Debugging mappings Managing rules across multiple report suites The extension is fully open source and runs locally in the browser.Extension Link: https://chromewebstore.google.com/detail/plcmmgiheecgepcmpkibmffodanlemhoGitHub Repository (Open source): https://github.com/abhishekDhami/AA_Processing_Rules_ExporterWould love any feedback or suggestions 🙂

Have you ever wished that Monique could answer your question or give you advice? Well, this Friday, June 26th, that dream can come true! And no Workfront topic is off limits!The WUG-DMV is hosting a casual, summer-themed virtual hangout and everyone is invited! Minimum slides and no presentations just a relaxed space to get your trickiest system roadblocks solved and celebrated live by fellow Workfront enthusiasts.🔥 Your Burning Questions: Throw your messy request queues, permissions knots, or reporting headaches at us so we can troubleshoot a fix together.🌤 Your Sizzling Hacks: Have a favorite text-mode recipe, dashboard setup, or shortcut? Bring it along to share with the group!👉 RSVP Here Today! 

We are currently relying heavily on the Adobe Real-Time API 2.0 to retrieve near real-time readership data for our analysis. I understand that the API is designed for fast processing, which is likely the reason behind the current limit of 1000 on realTimeValuesPerPeriodparameter as mentioned here - https://developer.adobe.com/analytics-apis/docs/2.0/guides/endpoints/reports/real-time#limiting-the-number-of-dimension-return-values-per-periodHowever, this limit is proving to be too restrictive for our use case. At present:We fetch data at a 5-minute interval, where we observe peak volumes of almost 8,000 events per interval Even after increasing the polling frequency to 1-minute intervals, we still receive approximately 3,000 events per intervalDue to the current cap of 1000, we are consistently missing a significant portion of events, which impacts the completeness and accuracy of our analysis.We have explored the option of further increasing the fetch frequency, but this is not feasibl

Tired of maintaining versioned custom indexes in AEM as a Cloud Service?In this blog, I explore Simplified Index Management using Diff Index, a powerful feature that allows developers to maintain only index differences instead of full index definitions.✅ Migrate existing custom indexes✅ Create brand-new custom indexes using only diff.json✅ Validate and verify migrated indexes✅ Understand limitations and best practices A must-read for AEM developers looking to reduce index maintenance overhead and simplify upgrades.  Want to Read more :- https://www.aemcq5tutorials.com/tutorials/simplified-index-management-aem-cloud-service-diff-index/ 

Là nguồn tham khảo thời tiết dành cho cộng đồng Việt Nam, ThoiTietHomNay.org cung cấp các bản tin dự báo chi tiết, dữ liệu môi trường và những thông tin hữu ích liên quan đến khí hậu. Website hướng đến việc hỗ trợ người dùng đưa ra quyết định phù hợp trước những thay đổi của thời tiết. 

Many thanks to Senior Product Manager Mayank Gaur and Computer Scientist Priyank Modi for showcasing the power and possibilities of AEM Dynamic Media! If you weren’t able to attend live – or want to revisit any part of the session – we’ve compiled a summary, session materials and additional resources below!  Session SummaryThe session focused on how AEM Dynamic Media helps organizations move from managing assets to activating personalized, governed digital experiences at scale. Using a coffee product launch example, the presenters demonstrated how Dynamic Media enables automated image and video optimization, AI-assisted asset activation through the Content Optimization Agent, secure and governed delivery controls, and scalable personalization through Dynamic Media Templates. The event also covered reporting capabilities, upcoming roadmap enhancements, and customer Q&A. Session MaterialsSlide Deck PDF Webinar Recording Consolidated Q&A Additional ResourcesEvaluate Dynamic Media

Are you integrating AI into your AEM or Edge Delivery Services environment (or planning to)? Wondering how to do it without introducing security risks or governance gaps into your production architecture? This webinar took place on June 24, 2026. AEM Champion Krishna Kalyan Gorthi (​@gkalyan) will cut through the noise to share practical design patterns, real-world implementation guidance, and proven strategies for adopting AI responsibly in AEM environments. You'll get concrete, actionable takeaways you can bring directly back to your team. What You'll Learn:Where and how AI fits into AEM and EDS architectures for maximum impact How to proactively address risks like prompt injection, data leakage, and untrusted outputs Real-world implementation patterns across application code, OSGi configuration, and dispatcher for secure AI adoptionThe slides from this session have been attached to this post. This article will be updated as soon as the recording has been uploaded to Experience Leagu

adaptTo() 2026 takes place from 28–30 September 2026 in Berlin.The schedule for this year's conference is now available. Following a record number of more than 70 submissions, we have put together a program covering AEM, Edge Delivery Services, open-source projects, case studies, and technical deep dives.https://adapt.to/scheduleTickets for adaptTo() 2026 are still available. Loyalty Tickets for returning attendees remain available until 3 July 2026.https://adapt.to/ticketsTiming reminder: To allow arrival on Monday morning without missing content, we’ve adjusted the times this year.Registration starts Monday at 11:00.Conference begins Monday at 12:00.– adaptTo() Conference Team

Thanks to everyone who joined today’s workshop, Own Your Impact as a Workfront System Admin! The session was led by Workfront Champion and Enterprise Workfront Platform Lead & Product Owner at TD Bank, Nuria Munguia ​@NuriaMunguia , who shared a compelling perspective on how System Administrators can translate their work into measurable business value and financial impact.  Key Takeaways:  The best work of System Admins is often invisible, so it's up to you to communicate a value story to leadership before someone else defines it for you.   Translate technical work into business value. Focus on outcomes such as time saved, costs avoided, risk reduced, and capacity created rather than listing tasks or activities completed.   Make your impact visible before leadership asks. Consistently track, measure, and communicate the business results of your work to demonstrate strategic value.  Capture value at intake. When requests are submitted, ask users to estimate time, effort, or cost sav

Thank you to everyone who joined us for our MEGA-WUG panel discussion on building and advancing a career as a Workfront Admin! We had a fantastic conversation with experienced Workfront professionals who shared their career journeys, lessons learned, and practical advice for anyone looking to grow their skills and expand their opportunities in the Workfront ecosystem.  Let’s Keep the Conversation GoingHave a career question that wasn't answered during the session? Looking for advice on growing your Workfront skills, advancing your career, expanding your network, or incorporating AI into your role? Post your questions in the comments below! Our panelists will be monitoring this thread and jumping in to answer questions, and we encourage other members of the Workfront Community to share their experiences and perspectives as well. One of the greatest strengths of this community is the willingness of members to learn from and support one another.Whether you're just getting started as a Wor

The recording of today’s Experience League LIVE show is now available on Experience League:https://experienceleague.adobe.com/en/docs/events/experience-league-live-recordings/episodes/exl-live-episode-06-24-26Target expert ​@drburnsTarget27 shared the latest ground-breaking innovations in Adobe Target as we embrace our new agentic era with a new Target MCP. We’ll share what it does, how to access it and show it in action. We’ll also showcase all of our new Adobe Target releases with demos showcasing expanded use cases and improvements in intelligence and execution!Jump in, ask your questions here, and connect with our experts.

Allow for creation of a Document Approval Template that does not include a specific approver. We have generic templates in Workfront Proof today that sets the Proof Creator as the default reviewer. The approver(s) is added when the proof is created.  We would use this template to pre-set multiple decisions/stages and due dates.

Hey all! To help you get oriented to Campaigns module in Coworker, here are a couple resources to check out: Blog: "From Prompt to Campaign" (Project Halo was the internal project name)  Get started guide: Coworker Product Docs Press release: Adobe Announces General Availability of CX Enterprise CoworkerMost importantly, try Coworker! Test different prompts and content generations. Try it in different languages. Leave feedback using the conversation icon in the top right nav. We’ll continue posting release news and resources here in the community as they’re available. Have additional questions? Put up a post or DM any of the Adobe team members posting in this community! 

It would be extremely helpful if the Adobe Cloud Manager UI displayed clear information on which user initiated a pipeline execution as well as which user approved or rejected the pipeline in the approval step.Today, identifying who triggered or approved a pipeline often requires navigating through logs or API calls, which is not intuitive. Having this information surfaced directly in the Cloud Manager interface would provide:Better traceability – Quickly identify the person responsible for starting a deployment or making an approval decision. Improved auditability – Essential for teams that must comply with governance, security, or compliance standards. Faster troubleshooting – When a deployment causes issues, teams can easily see who initiated or approved the pipeline and follow up with the appropriate individual. Enhanced collaboration – Team members and stakeholders can more effectively coordinate by knowing who has taken action at each stage.Displaying the triggering user and the

Hello Workfront Community,    I can’t believe it’s already June! Time has flown by since our last review, but I wanted to update you all on our H1 2025 Community Ideas review. As you may recall, this effort is part of our bi-annual ideas review process, which involves our product team as they review and respond to the top 20 ideas from the past 2 years. Please note that this 2-year period includes ideas from our last review cycle in November 2024. Ideas from our last review cycle are listed in the second chart below, labelled ‘H2 2024 Carryover Ideas.’ Many of you may have already been notified of these idea updates if you’ve interacted with them previously, but I wanted to consolidate all product responses into a single page.    A couple things to keep in mind:    All reviewed ideas below were published in the past 2 years.   Ideas responded to in this cycle will be updated periodically by the PM Owner until they are moved to a 'final’ stage,

Please add ‘Entered by’ to the list of fields available in a ‘Billing Record’ report.  Being able to audit who entered a ‘Billing Record’ is critical when you’re dealing with finance issues, we were surprised this wasn’t possible already. You can find a thread about this issue here: