Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
Hello,We are investigating an issue in AEM as a Cloud Service where some customer requests are being rejected by the Adaptive Rate Limiter with the message:server load exhaustedThe logs show that the rejection is based on the calculated server load and the predicted additional load, rather than the maximum number of in-flight requests being reached.*INFO* [qtp1005821649-5497] com.adobe.granite.ratelimit.AdaptiveRateLimitFilter Rejected <url>, server load exhausted. Server load: 749009/750000, inflight: 68/200, prediction: 35381Any guidance on interpreting these Adaptive Rate Limiter log fields and recommended troubleshooting steps would be appreciated.Thanks,Prince
Adding this product enhancements request for a customer - Background: Journey testing has been a significant hurdle for our organization. We are unable to use dry run fully as we have API calls to manage our opt outs and dry run stops working when there is an API call. Test mode is very limited because we, as a product team, do not have access to build test profiles in AEP to match the journey strategy scenario - business rule decision. It requires one of our engineers to manually build them for us, and we need to put that request in far ahead and we are unable to adjust test profiles in the midst of a testing cycle. With this, we have limited access to test mode. Simulation Experience and Requests: When simulation mode came out, we were very excited as it "solved" all our issues. It is a valuable tool to streamline the testing process and also to ensure we are testing all potential scenarios. With test mode (prior to simulation mode), we would require 2-3 sprints of time (4-6 w
I was recently blocked from sending an email due to one of the URLs in a button being too long, and not adhering to Marketo’s URL shortener. Because there was no error message that would have alerted me to the cause of this email not sending, I spent a lot of time (and tokens) trying to diagnose the root cause. In Marketo Engage, erroneous email components should clearly display the error that will cause the email to not send or be delivered, so the editor can resolve the issue.
Has anyone implemented a holiday send freeze for an always-on nurture program in Marketo Engage? I am looking for a way to temporarily pause email send from a specific nurture journey built with trigger smart campaigns during holiday periods while keeping members in their current wait steps and preserving the existing journey logic.
Our team frequently uses optimize nodes for various journey orchestration use cases. The ability to reorder these paths in the menu would improve organization and usability. Currently, if a path needs to be moved higher in the list, users must rename paths or recreate the Optimize node entirely and rebuild the associated logic. This increases effort, introduces risk of configuration errors, and makes maintaining complex journeys cumbersome. We are requesting drag and drop functionality or simple move up/down controls that allow users to reorder paths within an Optimize node without impacting existing configurations or logic. This would reduce the risk of configuration mistakes when modifying production journeys and improve operational efficiency for managing large, complex journeys. Overall, it would be a nice quality of life upgrade. Our current workaround is just to recreate the optimize node with the paths in the correct order.
I’m setting up Recommendations for the first time using this as reference: How Do I Implement Recommendations Activities? | Adobe Target but also many other pages of instructions.I understand that to build the list in the Catalog, I can use Feeds or the Recommendations API. There is a third option, Delivery API, that I haven’t explored. I tested using the Recommendations API and it worked. I was able to pass an entity.I’m not clear about this step (from the above page): 3. Pass behavioral information and contextIn Launch (aka Data Collection) I set up a Web SDK Variable and Rule that sets various entity attributes such as entity.id, entity.name, entity.categoryID, and so on. I can see this data on the interact payload and assume it’s being passed to Target. More inf here: Send parameters - Migrate Target from at.js 2.x to Web SDK | Adobe TargetWhat is the purpose of passing Target params? Is it to inform Target about visitor behaviour? Is this a different thing than adding entities to
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
I am investigating an Adobe Analytics implementation issue and would appreciate guidance on understanding the root cause.Current SetupWe are using:Adobe Analytics Extension (AppMeasurement) Custom Tracking Server configured in the Adobe Analytics Extension AEM as a Cloud Service Author and Publish environmentsThe Adobe Analytics Extension is configured with: Tracking Server:smetrics.company.comSSL Tracking Server:smetrics.company.comBased on Adobe documentation for trackingServerSecure, my understanding is that Analytics hits generated by this implementation should be sent through the configured tracking server rather than Adobe's default collection domains.Observation #1While testing an AEM Author URL similar to:https://author-pxxxxx-exxxxxx.adobeaemcloud.com/content/site/page.htmlI inspected Network requests and found Analytics calls being sent to:amcglobal.sc.omtrdc.netwith report suite information resembling:amc.global.prodinstead of using the configured tracking server:smetrics.co
I would like to share a key feature enhancement request for Adobe Experience Platform (AEP) Real-Time CDP architecture regarding data modeling flexibility. Ideally for B2C, B2B & B2P editions as we have consolidated all into single Prod & Dev sandboxes as advised by Adobe Ultimate Support.The Feature Upgrade:Enable native Many-to-One (N:1) schema relationships between non-B2B XDM schemas. This will allow multiple custom data records to link directly to a single parent account record within standard XDM profiles, without requiring both B2B XDM classes.Use Case & Business Need:Current Scenario: We have custom data entities (e.g., competitor products, telemetry, certifications) where multiple rows of data map to a single core business account. The Problem: Standard non-B2B XDM schema relationships are restricted to lookup options, which force data into arrays. This results in complex architecture and confusing schema building UI. Proposed Solution: A flexible parent-child rela
Hi All, I wanted to know if anyone has attempted to make a Proof HQ api call in order to remove/close out an active approval process? Looking for a way to close out outstanding proof approvals on projects that should be closed.
I got the case like this: Would have multiple identities for the logged user in my AEP implementation - however its easily done using IdentityMap. I would have multiple business entities However in AT there can be only one Identity - Target Third Party ID Namespace (so Target Profile can recognize only one Identity from IdentityMap How the user recognition works? AEP connects with AT on Edge so I assume its based on the IdentityMap not Target Third Party ID Namespace? Did you have the case like that?
Hi @Community I am working on activating qualified audiences to an SFTP destination in Adobe Experience Platform.We are seeing an issue where some profiles that have already exited the segment are still being sent in the SFTP export and misses the realized ones.Current setupAudience qualification / segment evaluation happens at 8:45 PM IST Export for same Audience is configured at: After segment evaluation to the SFTP server 10:30 PM IST 11:30 PM IST What we are observingThe 1st and 2nd exports look the same In these exports, 1–5 profiles out of around 100 sometimes appear even though they have already exited the segment The 3rd export at 11:30 PM IST contains the correct and additional data all are in realized state. ImpactBecause of this issue, the same profile (1-5) is being sent again on the next day. My questionI expected the export job to run only after segment evaluation is completed. In the AEP UI, it looks like the evaluation finishes first and then the export starts.Could
Hello, Can anyone help me with the intended use of being able to map segment membership in the destination out of the box mapping tool? segmentMembership.ups I am attempting to map a master audience to a destination and use ECN segment membership from other audiences to derive an attribute. I do not want to map the audiences I need segment membership from to the destination. Can anyone tell me How can I use segmentmembership.ups in destination mapping? Solutions for mapping segment membership from other audiences into a calculated field where the audience is not published to the destinationThank you!
Quick lesson from a recent Marketo-AJO project: Marketo is program/campaign-centric whereas AJO is event/journey-centric. This sounds obvious, but it changes the schema design, segmentation, and journey logic. This is not a mere lift-and-shift setup. The two main things aren’t the journeys themselves. These are schema design and identity resolution. Both are harder than they look. XDM Schema DesignIn Marketo, the data model is flat and permissive - custom fields can be added without touching anything else. In AEP, the schema is formal and more structured that every journey, segment, and destination downstream depends on.Few things that matter in practice:Schema classes come first: AEP has 2 main core classes - XDM Individual Profile (attributes like name, email, title, etc.) and XDM Experience Event (timestamped events like website visits, form fill outs, etc.). Every Marketo field needs to be sorted into one of these buckets before building anything else. Some Marketo fields have no
I use a Contentful as a CMS for web. CMS requests Edge Decisioning API and then render the offer. I need to debug what identities are sent in the request do you know if that request land is some specific dataset?
Have you used that API?My Prod and Dev are not 1:1 so I am expecting problem. I assume as a first step do the POC: Prod Offer Decisioning → Dev Decisioning for one specific Decision ScopeDo you recommend creating all the profile attributes, audiences etc on Dev and then map prod → dev?Any advices?
I am from AEM Dynamic Media team and I help customers get more measurable value from Dynamic Media: faster experiences, assets that work harder across channels, and a clearer view of what happens after content goes live. One simple self-service report has become especially useful in those conversations. It is the Dynamic Media delivery report. If you use AEM as a Cloud Service with a Dynamic Media license, you can generate and download the report yourself. The visibility gap of asset activationWe often hear customers say that once an asset leaves the DAM, visibility becomes fragmented. We know what we created and published, but we do not always know which assets are receiving the most delivery, which channels are consuming them, or how that consumption varies across markets. The Dynamic Media delivery report helps reconnect that last mile.To keep this conversation practical, I stepped into the shoes of a growth marketer at a fictional fashion retailer, “Luma Retail”. I used one month o
Managing enterprise-scale Digital Asset Management (DAM) requires more than traditional repository searches. With millions of assets, organizations need intelligent, scalable, and governed metadata management.This architecture introduces an AI Agent-based approach for Adobe Experience Manager (AEM) Assets:🔹 Business Users interact through chat interfaces or portals using natural language.🔹 AI Agent Layer understands intent, extracts entities, and selects the right tools.🔹 Custom Metadata Services provide governed access for search, validation, authorization, audit, and updates.🔹 External Metadata Repository enables high-performance search across 1M+ assets without scanning AEM repositories.🔹 AEM Assets Cloud Service remains the System of Record for all metadata updates.🔹 Synchronization Services maintain consistency through events and scheduled reconciliation.Key Architecture Principles✅ AI agents access enterprise systems through controlled APIs✅ External indexing enables fast m
I have a Fusion scenario that creates a Workfront project from a CSV file emailed to a request queue. Some emails also include supporting files that must currently be added to the project manually. I want the scenario to automatically upload these files to the project’s Documents folder. The scenario can distinguish the CSV used to create the project from the supporting files by their extensions. How can I ensure it processes the CSV first, waits for the project to be created, and then uploads the remaining attachments? Can the scenario loop through the attachments twice, or temporarily store the supporting files until the project is available?Any and all suggestions would be greatly appreciated. Thanks in advance.Frank
A comprehensive guide to isolated Dev and QA environments with AEM Author, Publish, Dispatcher, Nginx, persistent storage, and WKND validation Local AEM development often begins with a single Author instance. That is sufficient for early coding, but it does not validate the complete delivery path. A mature local setup should make it easy to test Publish behavior, Dispatcher filters and caching, environment-specific configuration, content activation, reverse-proxy routing, and repeatable environment lifecycle management. PURPOSE This guide presents a reproducible, Docker-based approach to local development and QA validation. It mirrors production engineering practices but does not replace AEM as a Cloud Service environments, Cloud Manager, or Adobe-supported production deployment models. What you will buildTwo isolated environments: Development and QA AEM Author and Publish services in each environment Apache HTTP Server with Dispatcher in front of Publish Optional
We're the Platform team behind Adobe's own AEP implementation, the biggest one in the world, actually: over 3 billion profiles, hundreds of campaigns and journeys, and thousands of internal users. Adobe's digital transformation isn't just something we help customers achieve. We did it ourselves first. Through the Adobe on Adobe (AoA) initiative, Adobe has optimized how we use customer data, orchestrate experiences, and engage with customers across the business. Our team built and operates the platform that makes this possible. Because we're running Adobe's own business and personalization efforts on the platform, we're often among the first to deploy and validate new AEP capabilities in production environments. That's how we became early adopters of CX Enterprise Coworker- an AI teammate that helps practitioners accomplish tasks faster by bringing together platform knowledge, business context, and workflow execution in one place. By using Coworker within our platform, we were able
We don't worry about the time of due dates. We've always looked at end of the day as the deadline. Yes, sometimes we have to stay late to get it done on time. Now we have Workfront (in our 4th month) and the planned completion date has a time portion, which has cause some issues for us. Tracking On Time delivery, even 3 minutes past is considered late. We only worry about it going out on the date it was requested due. (We've worked around this with a custom field on a report, using the "cleartime" function, to get accurate reporting for our needs)We have two teams, one in Minnesota and one in Chile. We have a lot of issues with tasks and time off sliding up or down a day on the schedule because of the time zone difference. Makes for a scheduling nightmare! (we can work around this by setting every project and task due date to be ie. 5pm, but that's yet another tiny detail for our PM's to have to not forget) We'd rather not have to work around these iss
Ohio WUG has now opened up registration for our virtual December roundtable discussion. Sign up today! December 4th12 - 1 pm ESTRegister: https://usergroups.adobe.com/events/details/adobe-user-groups-workfront-ohio-chapter-presents-december-2026-roundtable/
We’re excited to partner with the Adobe Workfront Product team for a 3-part event series to help you prepare and feel empowered for the changes coming to reviews and approvals in Workfront. Each session will offer live demonstrations, best practices, and more to help you with the transition to Unified Review and Approvals. Sessions include: August 11 – Everything You Need to Get Started with @Elise_Lawley September 15 – Making the Switch: Preparing for your Move with @Travis_Jordan October 28 – Making the Switch: Completing Your Move with @MikeEngel This post will serve as a central location for: Registration links for upcoming sessions Event recordings after they happen Related resources and documentation It’s not required, but if you’re interested, we did a session in March – Understanding Unified Approvals: Direction, Reporting, and What’s Next. You can catch the recording and resources here. Don’t forget to click the star at the bottom of this post to subscribe, so you’ll a
Hi everyone,We use the Next or Previous panel to analyse navigation, and we compared it with paths rebuilt from our raw data (page events ordered by timestamp within each visit). The results are very close, which makes this panel really valuable. But I think two options are missing to reflect real user behaviour:Include repeat instances. The panel uses the "Non-repeating instance" model, so consecutive views of the same page (e.g. a search results page reloaded after each date change) disappear. Flow already offers "Include repeat instances". Having the same setting here would make both views consistent. Show visit entries. When the page is the first of the visit, there is no previous page, and these occurrences are excluded. A "No previous page / Entry" row would let the previous pages add up to 100% of the page's occurrences.Today we work around this with a manually edited segment, but it has to be rebuilt for every page and panel, which doesn't scale.Would others find this useful t
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.