Product Communities

Hello Everyone  We’re hosting AEP user group sessions to network, learn, and share experiences at 3 locations - London, New York City and Bangalore. What are User Groups?User groups are community-led gatherings where Adobe Experience Platform practitioners come together to learn from each other’s implementations and real-world experiences, share best practices, challenges, and ideas, and build professional connections. Why attend? Hear practical AEP use cases and insights from your peers Grow your network and exchange ideas with others in your region Upcoming Meetups Join your regional Chapter at below locations and register on the Events page for the upcoming Kickoff. London Chapter is hosting Event on October 16, 2025(Link coming soon) New York Chapter is hosting Virtual Kick off on Sept 25, 2025 and in person meet on October 30, 2025  Bangalore Chapter is hosting Virtual Event on Sept 11, 2025 and Inperson Event coming soon. Interested in starting an AEP User Group in

The Problem A B2B RT-CDP customer recently noticed what seemed like “ghost profiles” entering their Adobe Journey Optimizer (AJO) journeys, more journey entrants than the number of profiles qualifying for the audience. This issue appeared across multiple journeys, skewing analytics and measurement. Typically, journey entrants are fewer than the audience size due to eligibility criteria, re-entry rules, or profiles leaving the audience before a journey starts. The customer’s data ingestion was standard: batch ingestion via a source connector from their enterprise data warehouse into Adobe Experience Platform (AEP). However, they also heavily relied on the Custom Upload feature to import audiences from CSV files that powered some of their AJO journeys and campaigns. The Cause To determine why AJO reported more entrants than expected, we examined profile snapshots and journey datasets. We found multiple profiles for the same person, created because of inconsistent casing in identity value

Native Visibility Rules and Progressive Profiling pack immense power. But one thing they can’t do is change whether a field is required: if a field is displayed per VR and/or ProgPro rules, it simply picks up the Required setting from Form Editor.   This means you need JS for advanced behaviors. Say Country should be optional for Home users:   Country and Company are required for Professional and Enterprise. while Number of Employees is displayed (via native VRs) but optional for Professional:   And finally, Enterprise users must provide Country, Company and Number of Employees:   Enter manageFieldRequirement() Here’s a little JS function that lets you achieve such special effects: /** * Programmatically require/unrequire a Marketo form field * @author Sanford Whiteman * @version v1.2 2025-08-25 * @license Hippocratic 3.0: This license must appear with all reproductions of this software. * */ function manageFieldRequirement(mktoForm, fieldName, userOption

Have you wished you had a guide for how to use advanced functions in your calculated metrics? Check out the link at the bottom of this post to see a new guide that I’ve written to help you understand the various functions available.   Calculated metrics are one of the most powerful features available in Adobe Analytics. Creating your own metrics gives you the flexibility to define KPIs like conversion rate or add-to-cart rate rather than simply relying on the events captured on your website (or Adobe’s out-of-the-box metrics). There are several features in calculated metrics that you can use: adding segments, containers, static numbers, and of course, functions.   Each function performs some type of mathematical computation in order to give you options for how you want to build your metrics. Some of these functions, like mean or median, are pretty basic yet still very powerful. You can use them to get an average of a particular metric without worrying about dividing it yourse

Have you ever attempted to use the Adobe Experience Platform Debugger to do some very simple troubleshooting tasks, like examining only your Web SDK payloads?  I have, and occasionally, my experience doing so hasn't been all that great, as exemplified by the following internal dialog:"Alright, I need to find a specific XDM object within a server call's payload"."I think I know which server call contains the correct payload and I think I know where to look within the payload itself""Okay, so I'll click here, then click there, then click here.""Is that it? Nope, darn. Okay, go back.""Click there, click here"."Wait, what is this?""Click here, click there, click, click, click.""Hmmm, why can't I just see everything all at once?"If you couldn't tell, it's all the clicking and guesswork that drives me crazy.  So, if you've had the same type of internal dialog as I have, please know you can set up a completely different method to look at your AEP Web SDK payloads – with a lot less c

In part 2 of this series I gave you a basic technical guide on how to get Adobe Analytics working with Web SDK. In this article, I will expand out more details of my recommended approach, particularly around how to efficiently populate the XDM Object. However, before we get on to what to do, I'm going to start with what not to do and my biggest mistake! Mental model Prior to using the Adobe Web SDK, based on years of successful deployments(!), I had a very strong mental model of how Data Collection - Tags should be set up to support Adobe Analytics.  My basic mental model went like this: Set a data layer in the website Read the data layer into Data Elements, normally on a one-to-one basis Use rules (which contain most of the logic) to: apply conditions to our data processing concatenate Data Elements together map Data Elements to Adobe Analytics variables send data back to Adobe Analytics My biggest mistake was initially sticking rigidly to this mental model and trying

Join the Engineering and Product team at Adobe Target in this impactful session as they cover key concepts related to the new Target UI, CDN experimentation, AI Assistant, and more. This 1-hour session aired in Feb 2025 and is your opportunity to learn all about what the Target team has been hard at work on for the past few months. Be sure to watch till the end for the customer Q&A!      If you don't have time to watch the whole session, you can view the attached presentation materials or review the transcripted customer Q&A by viewing the below information:    https://new.express.adobe.com/webpage/hI6qWvcex5lkb See below attachment PW for both: Target4u!   As always, let us know your questions or comments in the section below, and we'll do our best to get back to you as quickly as possible.

Hello All,I'm working on a Workfront project and need to send a reminder to the project owner three days before the Planned Start Date. I created a test project for this purpose, with a start date of September 5th at 8 a.m. I've confirmed that the project reminder notification is enabled, but the email still hasn't been sent. Has anyone encountered this issue or have any suggestions?" Thanks,DM 

Happy Friday everyone! Thanks for the awesome engagement yesterday at our Skill Exchange Session about Enabling New Features (and a bit of value realization too) always fun to get out and talk about Workfront.   Had a few people ask for slides so thought I'd share more broadly. If you have any questions that did not get answered yesterday, or any others that crop up post them down below and I'll respond. We can always tag in product experts to help with any specific release questions too.   Thanks to @kristinfarwell for being an amazing host as always!

First and foremost, a HUGE thank you to Kari @karib93wi for sharing the details of the creative brief process for Kohler and taking time to answer so many questions from the chat! And to everyone who attended, we hope that you left feeling inspired and excited about new process improvement ideas for your Workfront environment. There is no one-size-fits-all approach, so while this is just one example, find what works best for you and look to get leadership buy-in for support and adoption!   If you weren't able to join us live, below are links to the slide deck and recording, along with a short summary of what was shared: Slide Deck PDF – these are the Adobe slides (think User Groups, resources, upcoming events)  Kohler slides – this is what Kari shared for her presentation  Workshop recording  Kohler implemented a tiered approach with 4 request types, from large strategic campaigns (Tier 1 and 2) to simple revisions (Tier 4). As leadership approval h

Hello, friends!To anyone that has implemented WF Planning, I'd love to hear your specific use case - I know the reasoning why Planning was created, have read through documentation, and attended some webinars on it. But I'd like to understand some specific use cases:- Why did you go with Planning instead of core WF for your specific use case?- Are you using Planning only or a mix of Planning & core WF for your use case?- Pros/cons about Planning implementation?- Are you doing XYZ in Planning and then mapping record types to core WF and doing ABC in core WF/connecting the two?If you're inclined to be extra generous, I'd even love a short time with you to see it over screenshare - feel free to send me a private message in Experience League!

Hi,  I recall earlier this year I had an issue where suddenly review / contributor level users were no longer able to see the planned benefit field on projects within a report. This change is ultimately going to cause us to exceed our paid license count from our contract that was finalized earlier this year. Is there any way around this? Previously, these users were able to see that field without issue. 

I'm looking for a way to show within a form attached to a task the different Hour Types that were logged to it. For instance we use Task time and Support Time.  when i pull a Task report i want to know if only Task time, only Support time or if both Task and Support time were logged on that specific Job.Is there a way to do this within a calculated form field?Trying to avoid having to pull an Hours report as that will result in much more data manipulation when exported to do analysis.additionally.. not sure if there is a way to use calculated fields to total the different Hour types within the task show a total of all Support time logged, and total of all Task time logged. thanks!!

Hello Community,We are in the process of setting up the integration between AEM and Adobe Target. Could you please let me know which PIDs I need to use to create OSGi configs so that they are deployed as part of the code? Additionally, there are some existing configs that were created manually. I want to ensure that these existing configurations are not overwritten and that the new config is added as part of the deployment. Security -> Adobe IMS ConfigurationsAdobe IMS Technical Account ConfigurationCloud Services -> Legacy Cloud Services -> Adobe Target Configurations 

The Skill Exchange was the main event—now it’s time for the after party! 🎊Join us for the Workfront User Group’s Mega-WUG this week on September 10th. Expect a lively panel discussion featuring: Fresh perspectives on Workfront’s newest AI features Real talk on proofing and document approvals Unfiltered insights for boosting user adoption And more! Whether you’re a Workfront wizard or just Workfront-curious, this is your chance to connect, learn, and have a little fun while you’re at it. Don’t miss out. Register today.

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are weaving AI into their workflows securely, responsibly, and at scale. You'll walk away with: Getting legal & security approvals faster Prioritizing the right use cases Building trust for safe AI experimentation Can't attend live? No problem, register anyway, and we'll send you the recording after the event!   Register here: https://engage.adobe.com/scaling-aI-adoption.html

Introduction As organizations leverage Real-Time CDP to activate audiences across multiple destinations, data security and compliance becomes critical. One key consideration is the use of email hashing when sending audience data to downstream systems.  Email hashing is the process of converting email addresses into hashed values using functions such as SHA-1, SHA-256, etc. This obfuscates the original email addresses while retained its ability to act as a unique identifier for matching purposes in downstream systems. Hashing enhances data security and ensures compliance with data privacy regulations. Adobe Experience Platform (AEP) provides flexibility in handling hashed email addresses for identity resolution and audience activation.  Most out of the box Audience Export destination platforms in Real-Time CDP require that no personally identifiable information (PII) is sent in clear. The audiences activated out of Real-Time CDP can be keyed off hashed identifie

When enterprises face compliance requirements that restrict third-party domain management, we didn't just listen—we rebuilt how domain configuration works.   The Core Challenge Traditional marketing automation platforms require customers to delegate DNS management to the platform provider. For regulated enterprises, this creates an impossible choice: Why This Feature: Addressing Enterprise Compliance Challenges In highly regulated industries, marketing teams often face a critical barrier: compliance requirements that prevent third-party domain management. Whether it's HIPAA in healthcare, FINRA in financial services, or SOX compliance for public companies, these organizations need complete control over their domain infrastructure. This provides a complete separation between customer infrastructure and platform services :- No shared credentials between systems- Customer-managed certificates with full SSL chain control- Isolated infrastructure with no cross-customer dependenci

Hi all,   Adobe Journey Optimizer gives you endless ways to design experiences—but the real magic comes from how people actually use it. We’ve seen everything from clever quick wins to full-blown innovations that push the limits of what journeys can do.Let’s be honest—anyone can build a journey in AJO.…but can you build one that makes people go “no way you pulled that off in AJO”? That’s where the fun begins. 😏 We’re throwing down the challenge: Share your most clever, unexpected, or just plain awesome AJO journey. Your mission (should you choose to accept it): What problem were you tackling? What made your journey stand out? Any hacks, happy accidents, or lessons others should steal? Bonus points for screenshots (blur out the secrets) or a mini walkthrough—we want proof of your wizardry 🪄 Let’s see who’s got the boldest, wildest journey skills in the community! 🏆 ✨ Tag it with #JourneyHack or #MadeInAJO so we can all follow along.Or, if you’re fe

As I've found throughout my career in managing systems like Workfront, there is knowledge you acquire ahead of time via training and documentation, knowledge that you acquire just-in-time by troubleshooting challenges, and knowledge you acquire and then look back and REALLY wish that someone had taught you that 6 months ago. I will honestly admit that my example was a long-held belief that conditionally formatting a report column could only reference the data within that specific column. I'm /still/ second guessing myself on if/when that changed, or did it always do that and I just never noticed?    Even the most experienced admin occasionally runs into menu options, features or helpful tricks that they wish they'd know earlier in their admin career. So in that vein, what are some of the things you wish you could go back in time and teach previous-you to save some head-shaped dents in your office walls? Please chime in even if you're very new to the admin lifestyle,

This week's September 3rd, 2025 - Partner Technical Deep Dive is now available on demand.  The topics centered around several key topics related to Adobe Real-Time CDP and its capabilities. Including recent enhancements in Streaming Segmentation Monitoring and Visibility and Data Composability with Real-Time CDP and Cloud Data Warehouses Watch the recording and reference the presentation. Here are the main points and below are additional links to resources related to these topics. Enhanced Streaming Segmentation Capabilities: We introduced new monitoring and visibility features for streaming segmentation, including a dashboard for real-time utilization insights, proactive alerting, and the ability to allocate entitlements across sandboxes. These updates empower customers to deliver in-the-moment personalization at scale while maintaining data integrity. Data Composability for Warehouse-Oriented Customers: Adobe’s Federated Audience Composition (FAC) enables zero-co

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are weaving AI into their workflows securely, responsibly, and at scale. You'll walk away with: Getting legal & security approvals faster Prioritizing the right use cases Building trust for safe AI experimentation Can't attend live? No problem, register anyway and we'll send you the recording after the event!   Register here: https://engage.adobe.com/scaling-aI-adoption.html

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are weaving AI into their workflows securely, responsibly, and at scale. You'll walk away with: Getting legal & security approvals faster Prioritizing the right use cases Building trust for safe AI experimentation Can't attend live? No problem, register anyway and we'll send you the recording after the event!   Register here: https://engage.adobe.com/scaling-aI-adoption.html

I would like to suggest a few items regarding AI Assistant for Workfront: 1) can you provide videos and sample prompts to accompany the AI Assistant for Workfront documentation? The documentation is too generic and 2) will you have a best practices session on AI Assistant for Workfront?  Especially around prompts 

We’re exploring a migration from AEM 6.5 (6.5.19, Java 11, ~100-page static site) to AEM as a Cloud Service.Curious what others have experienced, like key things to watch out for migration challenges, no-go's, unexpected challenges.  Our website uses the typical1. 1 Language, region - en, us2. Assets3. Experience Fragments4. Tags5. ACS Commons - Lists5. No workflows, external API integrations6. Dev Stack : Java 11, Webpack, Bootstrap, React 18.2