Welcome to the Adobe Experience Platform Community! Connect with peers to ask questions, share best practices, explore release updates, and contribute ideas that shape the future of Adobe Experience Platform.
Recently active
Is there any way to debug with Assurance why the VEC experience is not returned?
I am looking for guidance on a personalization use case involving AEP Edge Audiences and Adobe Target, specifically around extending personalization beyond the current session and supporting a TTL-based return visit scenario.Current Architecture* Adobe Web SDK* Adobe Experience Platform (AEP)* Adobe Target* Edge Segmentation enabled in the Datastream* ECID as the identity* Same domain journey User Journey1. User lands on Homepage (`abc.com`).2. Homepage contains a "Get Started" banner/blade.3. User clicks the banner and navigates to a quiz page (`abc.com/quizpage.html`).4. User completes the quiz.5. Upon quiz completion, a custom event is sent via Web SDK.6. AEP audience qualifies based on quiz completion attributes.7. Business requirement is to hide the "Get Started" banner on the homepage for quiz-completed users. What We Successfully AchievedPOC – Same Page PersonalizationWe created an AEP audience using quiz completion attributes that only become available when the quiz completion
Hi Community,I have to replace complete array with new values of array on every batch ingestion, but on every batch ingestion new items gets appended to this array in target dataset instead of replace. I have used upsert_array_replace in a calculated field and my dataset is profile and upsert enabled. Below is the structure of my target and source array, it has a primary identifier as "key" and "comm_details" array object to replace. Calculate Field : upsert_array_replace (_tenant.comm_details) -- Source Dataset Field : _tenant.comm_detail[*] -- TargetI have already gone through documentation. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform/overwriting-the-array-object/m-p/566290https://experienceleague.adobe.com/sv/docs/experience-platform/data-prep/functions#arraysCould
Greeting Adobe Community! I am observing the following error code UPINGT-030024-424 An error occurred while processing the batch. Please contact support. and here are the details of the error - “The XID cannot be generated for code userId.XID generation failed for nsCode = {code}, nsId = {id}” I am getting similar error messages in the AJO Push Profile Dataset while testing push notifications for different fields where all ingestions are failing due as XID cannot be generated. Has anyone faced the same? Any guidance and support would be really appreciated. Thanks,Sambit
I’ve been trying out the Adobe Reactor API and was wondering if others have had the same experience with the revision media-type parameter in the accept header. It might be me, just misunderstand its functionality. The documentation states: All GET requests to the Reactor API require an Accept header to determine what data is returned by the system. In most cases, this value will be application/vnd.api+json;revision=# (where # is the revision number of the resource you want to retrieve, e.g. 1).However, when I make a request for a single rule (https://reactor.adobe.io/rules/{RULE_ID}) that have multiple revisions, and I use the header Accept: application/vnd.api+json;revision=6. I get a 406 not acceptable.The only value that seems to work is revision=1. So my question is: is the revision parameter actually functional, or am I misunderstanding something?Another question I have, is about the format of the Accept header. It seems standard to allow optional whitespace between the media ty
Computed Hours in AEP License usage is always same from May 27, may I know what's the reason
The method appendVisitorInfoForURL returns in some situations a “|” character. When these urls are processed by some of our systems this character is causing problems.adobe_mc=TS=1781184368|MCMID=30298187359278372896471907409936339487|MCORGID=A174401053C92A7E0A490D4CWould it be possible to encoide this url without causing other side effects or losing the user journey?
Facing issue in sending qualified audiences to facebook custom audience from adobe experience platform. I am getting is error as 404 , have done with all the prerequisites facebook connection mentioned in document. Still it’s not working."Permissions error","code":"400 BAD_REQUEST".Appreciate any help on this.
Subject: Guidance Required – upsert_array_replace Support for Batch IngestionHi everyone,Good evening.I need some guidance regarding the behavior of upsert_array_replace with Batch Ingestion in Adobe Experience Platform.I am trying to update an array field in an existing Profile using Batch Ingestion (Upsert). However, instead of replacing the existing array values, the new values are getting appended.I have gone through the available Adobe documentation and tested different approaches, but I couldn't find any confirmation on whether upsert_array_replace is supported for Batch Ingestion.From the documentation, I could confirm that upsert_array_replace is supported for Streaming Ingestion, but I couldn't find any mention of Batch Ingestion.Could someone please help clarify:Is upsert_array_replace supported for Batch Ingestion?If not, is there any alternative approach to completely replace array/object-array values during Batch Upsert?Is there any official Adobe documentation that explic
If you're using Adobe Client Data Layer (ACDL) in Tags (Launch) and ordering of Rules is important to your setup, then setup your ACDL Events to listen to "All Events" only. Preface / Legend For the rest of this post, I'm going to use specific upper- and lowercase spellings to distinguish various items. Uppercase "Event", "Condition", "Action": these refer to the Events, Conditions and Actions in Tags that come from extensions. For example, the ACDL extension has an Event called "Data Pushed". Uppercase "Rule": this refers to Rules that are setup in Tags. A Rule can contain 1 or more Events (where each Event doesn't have to come from the same extension), 1 or more Conditions, and 1 or more Actions. Lowercase "event": any other event that occurs during your web page's runtime, i.e. when it is loaded and interacted with in the user's browser. "ACDL event": an event that got pushed into ACDL / adobeDataLayer. Background Tags, or Launch as is more commonly known, has a fantasti
Hi all,struggling a little bit to set up the Visitor ID sync between parent frame and iFrames by configuring whitelistParentDomain and whitelistIframeDomains. Background: we have two domains, domainA.com and domainB.com .both domains run their own Launch property both use the same AdobeOrgID both track into the same Adobe Analytics Report Suite third-party (demdex) cookies are disabledNow, we want to make sure the ECID is synched across outer frame and iframe for a stitched view on the visitor.Outer Launch property Experience Cloud ID Service config: (whitelistParentDomain is added, so it should be able iframes from the same domain, open for discussion if needed)Outer Launch property Experience Cloud ID Service config Data Element “whitelistIframeDomains”:return [ "www.domainB.com"]; iFrame Launch property Experience Cloud ID Service config: (note that the consent is disabled by default / for testing, but don’t work with consent enabled for both, either)iFrame Launch property Experi
Hi @Asheesh_Pandey , @jachlt , @Parvesh_Parmar , @SantoshRa5 I’m looking for guidance on how to backtrack and analyze excluded identities during exports in AEP. Currently, we don’t have any mandatory fields or consent labels configured, so I’m unsure what might be causing these exclusions.Are there other factors or checks we should be considering that could lead to identities being excluded? Additionally, how can we effectively trace back and understand why certain identities are not included in the export?Any insights or suggestions would be greatly appreciatedhttps://experienceleague.adobe.com/en/docs/experience-platform/dataflows/ui/monitor-destinations#dataflow-runs-for-batch-destinationsThak
DescriptionI wish there were a more comprehensive panel for Engageable Profiles in Adobe Experience Platform. Why is this feature important to youPrimarily, it would provide organizations with a deeper understanding of profile usage.Recently, our organization faced an issue that resulted in nearly one million profiles becoming engageable due to an error. Identifying the root cause required us to use Query Service to identify the journey, then open the journey to determine the associated audience, and finally analyze the audience to understand how those profiles were ingested.This investigation process was very time-consuming. Having an out-of-the-box monitoring capability for Engageable Profiles would significantly simplify troubleshooting and usage analysis. Important monitoring could include:New engageable profiles by day Which journeys are triggering new profile engagement, allowing users to display a sample of the newly engaged profiles Which namespaces are being used by those jour
Hi Everyone, I’m new to Web SDK implementation, and I’ve noticed that an upgrade is available for the web sdk extension. If we proceed with the upgrade, will it have any impact on the existing rules and data elements?Also, could you confirm whether the extension needs to be upgraded separately in each environment, or if upgrading it in a lower environment makes it available in the library for validation across environments?I’ve gone through the release notes, but wanted to double-check—are there any potential risks or issues we should be aware of during or after the upgrade?
How can I map an array of date strings coming from the Adobe Analytics source connector into an XDM array field with dateTime datatype in AEP Data Prep? Since we cannot transform it upstream, does Data Prep support element-wise date conversion for array values, or is post-ingestion processing required?
Hi All,I am hoping someone across Application Design reads this, because it does not fall into the topics in the list, but is more across the whole Experience Cloud Product.Recent changes have made it so that ALL links pasted into applications, such as Email or Microsoft Teams, just say “Adobe Experience Cloud”. Previously when sharing an AA or CJA report - or a link to a Marketo program, it would be more definitive. This makes it hard for the receiver of links to know what each link is for. Screenshot from Microsoft Teams of a Marketo link. With recent changes, and I have especially noticed with migration of Marketo to Experience Platform, it is very hard to identify which browser TAB I have which application open in. I use multiple applications and have them all open at the same time - AA, CJA, AEP, Marketo, Admin Console. But the favicon is all the same. Can you implement different colours on the favicon, or some other visual identifier, to make it easy for me to switch between a
Hi, I am currently working AEM 6.5 on premise project. I would like to incorporate LLM visibility scans into our CI/CD pipeline.So far I have found LLM optimizer. Do you know if LLM optimizer provides some API that we can call during our automations tests?Alternatively there is AI Content Visibility Checker chrome plugin. Do you know how it calculate visibility metric?
There is a streaming segment with condition - AttributesInclude First name equals latencyEvents(Include audience who have at least 1 Any event where (Event Type equals latency.ingested) ) and occurs in last 10 minute(s) Scenario 1 - event ingested first - no qualificationafter 2 min profile ingested - imediate qualified to the segment.--Scenario 2 - after 10 min from first event ingestion the Profile got exited from the same segment.qa) IS THIS EXPECTED? I have not ingested any event or profile attribute during this 10min.--Scenario 3 - after the profile got disqualified from the segmentEvent ingested again without altering profile attributes - re qualified qb) IS THIS EXPECTED? Just event is ingested and the profile attributes from previous ingestion stays as it is. Can some one give answers to qa and qb with supporting adobe documents.
Dear AEP Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with Adobe Experience Platform.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for June 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 AEP. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEP-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 – creating highly personalized digital experiences with AEP.Start supercharging your problem-solving skills today by exploring our Top KCS Articles! Take a look:Custom
Problem Statement :How can we support near real-time or frequent audience evaluation in AEP, when the platform only allows one scheduled batch segmentation run per day and does not support sub-daily automation? Solution: In Adobe Experience Platform (AEP), batch segmentation is designed for daily execution (one run per day per sandbox). This becomes a challenge when business requires more frequent audience refresh (hourly or near real-time use cases).To handle this, AEP provides a combination of on-demand execution, optimization strategies, and alternative approaches. 1. Understand the Core LimitationOnly 1 automated batch run per day per sandbox No hourly or multiple recurring schedules supported Schedule timing (default 5:00 AM UTC) can be modified only via API, not UI👉 This means native batch segmentation cannot meet high-frequency use cases 2. Use Flexible Audience Evaluation (FAE) – On-Demand RunsTo overcome this limitation, AEP provides Flexible Audience Evaluation (FAE).✅ What
The Problem StatementHow do we connect RT-CDP audience segments with CJA event data to analyze customer journeys, despite differences in identity stitching models and delayed audience data availability? Answer-If you are setting up Adobe Customer Journey Analytics (CJA) along with Real-Time CDP (RT-CDP), you might notice an interesting challenge.Both platforms handle identity stitching in very different ways:RT-CDP builds a real-time Identity Graph to link users across systems. CJA works on fast, query-based analysis using flattened event data (like web/mobile logs).So the key question is:How do these two systems connect?How does an audience created in RT-CDP match perfectly with web or mobile events in CJA?Let’s break it down step by step.Core Concept: Persistent ID vs Person IDWhen you configure a dataset (WebSDK or Mobile) in CJA, you define two important fields:Persistent ID → Identity Graph → Person ID(Raw Input) (Linking) (Final Output) Persistent ID (Input):
Have you ever noticed a strange behavior in Adobe Experience Platform (AEP)? You can build a structural blueprint called a Schema with a special map called an identityMap. You can add an email and a phone number as normal identities, but leave the "Primary Identity" field completely blank. The system still allows you to click "Enable for Profile" and save it without any errors at all!It looks like everything is working perfectly. But underneath the hood of Real-Time CDP, this creates a hidden trap: the system will connect your IDs in the map, but it will fail to create actual customer profiles.Let’s understand why this happens using a simple story based on a real-world company: Walmart. The Problem: Missing Profiles Imagine Walmart is tracking digital shopping activity using an AEP Schema. A customer goes online and makes a purchase, providing their phone number and email.Because the Walmart Schema has an identityMap at its root, AEP stores this transaction. Later, a data analyst check
Hi all,we are using the “Device Lookup” feature in our datastreams.In addition to Adobe’s lookup data, we would still like to receive the _actual_ userAgent string from our Web SDK calls.Now we noticed, that when we set it through Launch in `environment.browserDetails.userAgent`, it seems to be reset by Adobe, and in CJA we always see “No value”.Interestingly, Assurance shows that the value is present in the hit, but whatever happens from there on is not really understandable and the final result not logged in Assurance.I mean, I get that the radio button indicates you can have either user agent / client hints OR device lookup.But if the device lookup does not populate/overwrite that field, why is it resetting it then? Does anyone knowwhy this is? a way to figure out the final processed request payload within Assurance?
I regularly check the CJA release notes for updates and fixes using the link provided. However, I am trying to locate the descriptions and details for the ticket numbers listed in the ‘Fixes for Customer Journey Analytics’ section. In the past, I have opened several support tickets, but my tickets begin with ‘E-’, while the ones in the fixes section start with ‘AN-’. Can you help me understand where to find the information for these 'AN-' tickets?https://experienceleague.adobe.com/en/docs/analytics-platform/using/releases/latest#fixes-in-customer-journey-analytics
Exited to host this even with Adobe AEP Product Manager.Join us for this virtual session where Adobe Product Manager will showcase the latest upgrades, features, and best practices for B2B use cases in Adobe Experience Platform and connect directly with Adobe experts and network with fellow professionals.Event is scheduled on June 24, 2026 at 3 PM CST.Register here: https://bit.ly/4g5Sp0r
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
