Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
Save time writing scenario summaries — click Describe with AI in a scenario’s Settings panel and Fusion will generate a clear, human‑readable description for you automatically, based on the modules and configuration in the scenario.OverviewThis release adds a Describe with AI action to the Description field in a scenario’s Settings panel. When invoked, Fusion analyzes the modules, connections, triggers, and mapped outputs in the scenario and produces a concise description you can accept, edit, or discard. The feature is designed to help teams keep scenario metadata accurate and useful without having to compose descriptions manually. What’s newDescribe with AI button — One‑click generation of a scenario description from the Settings panel description field. Context‑aware summaries — The generated text reflects the scenario’s modules, triggers, key connections, and primary outputs so descriptions are actionable and relevant. Edit and accept flow — Generated descriptions are presented in
You can now authenticate your Salesforce connections using PKCE (Proof Key for Code Exchange) in addition to standard OAuth 2.0, and enable Refresh Token Rotation for improved long‑term credential security. When creating a Salesforce connection, choose the authentication method from the new Connection type dropdown.OverviewThis update adds two security‑focused options to the Salesforce connector: PKCE for secure, browser‑based authorization flows (recommended for public clients and scenarios where a client secret cannot be safely stored), and Refresh Token Rotation (RTR) to automatically rotate refresh tokens and reduce risk from long‑lived credentials. What’s newPKCE (Proof Key for Code Exchange) — Authenticate without a client secret by using a code verifier/challenge flow. Useful for public clients or environments where storing a client secret is not desirable. Refresh Token Rotation (RTR) — Optionally enable RTR for Salesforce connections so refresh tokens are rotated on each use.
TITLE EDIT: Rulesets at action levelhi ! is there a way to retrieve all journeys which are using a rule set? using API or query service? I already know that journey_step_events is handling those ruleset values but is there another way at action (communication) level? thanks
The customer Journey Management > message Execution field group physically exists in both the AJO message feedback schema and the AJO email tracking schema. I can see the field in the tracking schema and build a CJA report against it. But at runtime, the value is never actually populated on tracking events.Since opens are tracking events, and tracking events never carries messageExecution. metadata, any CJA report keyed on that metadata for opens/clicks will be blank.I tried identity stitching for tracking and feedback events datasets in CJA with an Identity Map as EID in both datasets. But still unable to see engagement metrics (email opens and email clicks) when using the metadata LOB value filter for email opens and clicks in Email Journey Reporting in CJA. Is anyone facing a similar issue in CJA?
I am looking to track the timeline historic changes of status - (mainly Approved to Complete) of projects. I can see the day it happened, but not the time it spent in a single status. This needs to happen without the use of Fusion and preferable excel. I have been looking into the journal reporting with calculations and so far nothing.
We noticed our original referrer data starting to get stripped which moved what would have been Natural Search traffic into Direct throughout the summer, but especially in early August. Are there any ideas on if this is related to the Safari 26 browser update tied to an iOS release, and are there any work-arounds to get that traffic back in under Natural Search in Adobe Analytics?
Hello, Does anyone know if there will be a challenge for 2026? I know the 2025 was canceled.Thank you
The Mention widget should automatically prioritize active conversations by moving any existing thread with a newly added comment to the top of the widget. This would improve visibility and help users quickly identify and respond to recent activity.Currently, users must scroll through the widget to locate new comments if the original thread was created some time ago, since thread placement is based on the thread's start date rather than the most recent comment. Reordering threads based on the latest activity would create a more intuitive and efficient user experience.
🚀 I’m excited to be speaking at the next Adobe Experience League LIVE session: Coworker Unlocked: Transforming CX Workflows with Adobe CX Enterprise Coworker!AI is evolving beyond helping us complete individual tasks. It's becoming a true teammate that can help organizations uncover insights, create audiences, optimize journeys, and automate work across customer experience workflows.Join the Product and Product Marketing team as we pull back the curtain on Adobe CX Enterprise Coworker and share:✅ How Coworker builds on the foundation of AI Assistant to help drive outcomes, not just tasks✅ The capabilities powering Coworker, including skills, plugins, and MCPs✅ Real-world use cases showing how teams can work smarter, move faster, and deliver better customer experiencesWhether you're a marketer, analyst, practitioner, or CX leader, you'll see how agentic AI is transforming the way work gets done!📅 September 24, 2026 | 8:30 - 9:30 AM PT👉🏻 Registration link here: https://engage.adobe.c
Make your mark at one of the biggest names in payments. We are looking for a Senior Marketing Operations — Growth & Acquisition is a business-critical role within the Revenue Marketing organization and will have a measurable impact on new customer pipeline and revenue growth. This person will own the end-to-end operational execution of acquisition marketing programs within a complex B2B2x sales model, working cross-functionally with Line of Business (LOB) stakeholders, analytics, creative, and sales teams to plan, deliver, and continuously optimize campaigns through the marketing automation system.This high-impact role requires a detail-oriented, results-driven marketer who thrives at the intersection of strategy and execution. The ideal candidate brings deep experience managing the full campaign lifecycle, from audience building and platform setup through launch, weekly performance optimization, and post-campaign debrief, and is equally comfortable driving day-to-day tactical deci
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
Hello, Can’t log in. The error message is “We were unable to authenticate your request.We could not locate your account or an active Salesforce connection associated with email address: amurphy@quenchwater.com”. I login using Salesforce. Below is the URL Adam
Has anyone else had issues with updating tokens where each time a token is updated the entire screen refreshes and jumps to the top of “My Tokens” view? When updating several tokens it is very difficult to keep track of each one.I’ve noticed this is Chrome and Safari. Is this a bug or a browser issue?
SUMMARYMake open tracking a per recipient decision driven by a person field, evaluated at send time, instead of an asset level setting. One email asset would then serve both consenting and non consenting recipients, and native Opened Email activity would still be generated for the consenting recipients only.TODAYThe only control over the open pixel is the asset level flag isOpenTrackingDisabled, exposed as the "Disable Open Tracking" checkbox in Email Settings and on the Emails Asset REST API. It is all or nothing for the asset.Adobe's own CNIL guidance therefore instructs customers to build two variants of every email, one tracked and one untracked, plus a Smart Campaign Choice step on a consent field to route recipients between them. Adobe Support has confirmed this is the only supported approach.Setting isOpenTrackingDisabled to true suppresses the pixel for every recipient of that asset, and Opened Email is a system activity that cannot be written back through the REST API, so ther
I found this old Idea that asked to be notified when the Desktop Proof App gets a new version released. Did this ever get considered? We have to get this app uploaded into our Self Service by our IT department and we don’t know when there is a new version out until someone has an issue. It would be great to get this processing as soon as a new version is released.
We cannot get the Computed Attributes Value Distribution to show anything except non-zero values. This remains true even after confirming that the Computed Attribute is evaluating and complete. In addition to the Value Distribution showing zeros, each of the shown sample profiles also shows a value of 0 for this Computed Attribute. This initially led us to believe there was something wrong with the underlying logic of the Computed Attribute itself. However we pulled one of our own ECIDs and checked the associated profile within CDP and we were able to confirm that the profile has a value of '9' for the attribute, which seems plausible We were recently informed by Ultimate Support that a minimum success rate of 30% is required for Computed Attributes. This is also where we learned that the 30% was not only a minimum threshold for the Value Distribution/Sample Profiles QA piece, but also for getting the Computed Attribute in and of itself to populate at all. This is an extremely high tar
We cannot get the Computed Attributes value distribution to show anything but non-zero values. We were recently informed by Ultimate Support that a minimum success rate of 30% is required for Computed Attributes. This is also where we learned that the 30% was not only a minimum threshold for the Value Distribution/Sample Profiles QA piece, but also for getting the Computed Attribute in and of itself to populate at all. This is an extremely high target threshold and unrealistic for many of our real-world applications. We did ask Ultimate Support if and how clients have adopted Computed Attributes given those requirements and we learned that there have not been many Adobe clients who have, and confirmed that many other clients have expressed similar concerns as we have. Can the Computed Attributes value distribution minimum success rate be optimized & improved beyond the current 30% minimum threshold?
We are scheduled for the AWS data center migration in mid August. Can anyone that has already been through the migration give their feedback on how that went, issues they faced, gotchas to have in mind prior to the outage? We’ve gone through Marketo’s documentation but some of it is a little vague. In addition if anyone can answer any of the questions below that will be helpful:Does anyone have any screenshots of what the pages / forms (embedded or otherwise) look like during the outage?Did you get a notification when the migration was completed? They offer to cache embedded forms - what is the benefit of this? Would this allow the forms to stay visible and receive submissions to be processed later or does it just mean they would stay visible. Did the migration get completed within the window they gave or was it longer / shorter? Other than updating IP Addresses were there any changes that might impact webhooks, endpoints etc that we might be missing?We are also recaching out to Marke
We cannot seem to get the Value Distribution for Computed Attributes to show any non-zero values? We were recently informed by Ultimate Support that a minimum success rate of 30% is required for Computed Attributes. This is also where we learned that the 30% was not only a minimum threshold for the Value Distribution/Sample Profiles QA piece, but also for getting the Computed Attribute in and of itself to populate at all. This is an extremely high target threshold and unrealistic for many of our real-world applications. We did ask Ultimate Support if and how many clients have adopted Computed Attributes given those requirements and he shared that there have not been many Adobe clients to his knowledge who have, and confirmed that many other clients have expressed similar concerns as we have. Hence the idea & feature enhancement request raised here.
Hello, Workfronters! On October 29th, we're bringing a day built just for Adobe Marketo Engage and Adobe Workfront users to New York City, and we'd love to see you there. Spend the day with Adobe customers, admins, and practitioners sharing the real-world insights and best practices they've learned firsthand. Think brand and legal approvals, AI-ready governance, reporting with Workfront Fusion, smarter planning, and a bonus peek at the Agentic Marketing Garage. Plus lunch, a networking reception, and plenty of time to connect with people who do what you do. Here's a taste of what's on the agenda:How Qualcomm rebuilt brand & legal approvals in Workfront Getting your Workfront instance AI-ready Turning data into action with Workfront Fusion From PowerPoint calendars to real Workfront Planning Bonus: Agentic Marketing Garage Are you in the New York metro area? Come join us! Not local? Share this with a colleague in the area! Check out the full agenda and register today: https://reg.ad
Hi!Looking for some help here. :) I watched a Adobe video a while back that someone shared how they use AI to help document the Fusion scenario by using exported JSON file and prompt the AI to fill a template out. Back then, our team hasn’t started the automation yet. (I should’ve bookmarked it.) Now that we start to leverage Fusion, I want to capture proper documentation but can’t find the video anymore. Does some know which video that is or have something they can share on this topic?Thank you in advance for any of your sharing!
Hi All, I ran the dispatcher utility in local and it auto-runs as part of web-tier in build stage too.Ideally one would expect same inconsistencies but there was a difference in my case. Local Validator - PS C:\Users\admin\Downloads\aem-sdk-dispatcher-tools-2.0.274-windows\bin> .\validate.cmd 'C:\projA\dispatcher\src'opt-in USE_SOURCES_DIRECTLY marker file detectedPhase 1: Dispatcher validatorCloud manager validator 2.0.892026/09/07 19:41:48 The following warnings were found: Did not find ServerAlias '*.adobeaemcloud.net' in any vhost file Did not find ServerAlias '*.adobeaemcloud.com' in any vhost file2026/09/07 19:41:48 The following suggestions are proposed: C:\projA\dispatcher\src\conf.d\enabled_vhosts\aem_publish.vhost: file is not a symlink, all files inside "enabled_vhosts" and "enabled_farms" should be symlinks2026/09/08 19:41:48 The following errors were found in the httpd config: C:\projA\dispatcher\src\conf.d\enabled_vhosts\aem_publish.vhost: link points to invalid lo
The Adobe Analytics API 1.4 is scheduled for decommissioning this summer, yet critical endpoints from this legacy API have not been integrated into API 2.0. This creates a significant gap in functionality that will impact many organizations relying on programmatic management of Adobe Analytics configurations.Missing Critical Functionality:The most important missing feature is the ability to programmatically:Create new Adobe Analytics variables (props, eVars, events) Modify existing variable configurations Delete variables when no longer neededCurrently, API 2.0 forces users to manually manage these variables through the Adobe Analytics interface, which is:Time-consuming for bulk operations Error-prone for complex configurations Incompatible with automated deployment workflows Difficult to integrate with CI/CD pipelinesBusiness Impact:Without this functionality in API 2.0, organizations will lose the ability to:Automate variable management across multiple report suites Maintain consiste
Hi Team,We are using:AEM 6.5 LTS Adobe Target AEP Web SDK (Alloy) AEM ↔ Target integration (activities are successfully created in Target)We have an AEM Targeted Parsys on a page to target the content based on the audience. The activity is successfully synchronized to Adobe Target and is Live.However, personalized content never displays. The component always renders the default content.ObservationsThe rendered HTML contains:<div class="mboxDefault" data-target-applied="fallback">and AEM generates maekup:mboxDefine(...)CQ_Analytics.TestTarget(...) Web SDK BehaviorThe page sends an Alloy request: {"decisionScopes": ["__view__"]} and Target returns propositions successfully.Returned activity IDs:xxxxxHowever, our activity:123456 is never returned in the proposition response.Activity DetailsActivity Type: XT Status: LiveAdditional FindingsThe browser does not have at.js loaded:typeof adobe?.targetreturns: undefinedbut Alloy is loaded:typeof alloyreturns:function QuestionIs the OOTB A
We're evaluating Ataccama and Celonis for metadata validation and asset completeness checks in our AEM DAM environment as part of our governance strategy.If anyone has experience integrating either tool with AEM, I'd appreciate insights on:Integration approach and any technical challenges encountered How you're leveraging these tools for metadata quality monitoring Any lessons learned or recommendations for implementationAny pointers or case studies would be helpful!
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
