Adobe Experience Platform

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, 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.    

Computed Hours in AEP License usage is always same from May 27, may I know what's the reason  

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

we are trying to create a destination sdk to swoogo faccing issue which authentication type to use had tried OAuth 2 with Client Credentials Grant it is not working please suggest what kind of customerauthentication to be used for these destination .below for swoogo request api token for refernce :https://swoogo.readme.io/reference/post_oauth2-tokenSwoogo Api:https://swoogo.readme.io/reference/updatecontactthese was used in our config json it was not working: "customerAuthenticationConfigurations": [   {      "authType": "OAUTH2",      "grant": "OAUTH2_CLIENT_CREDENTIALS",      "accessTokenUrl": "https://api.swoogo.com/api/v1/oauth2/token",      "clientId": "XXXXX",      "clientSecret": "XXXXXXXXXXXXXX",      "options": {        "useBasicAuth": true      }    }    ],

 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):

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

I have several batch audiences which were activated to destinations within the past 2 years. They were created through the segment builder UI; there are about 300K+ qualified profiles. This week when I go to edit the audiences via the UI, under attributes there is an error which says “Cannot set properties of null (setting 'segmentJobData')”. Clicking Edit Audience results in an error of “Audience cannot be loaded. Cannot set properties of null (setting ‘segmentJobData’).”  Any thoughts on how to resolve this issue such that I can edit the audience?

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​​​

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,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?  

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

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?

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

We are about 18 months into a mature AEP + RTCDP implementation and have crossed 400 active segments across business units. We are starting to see non-trivial evaluation latency on streaming segments during peak ingestion windows and our architecture review flagged segment sprawl as a likely contributor.Adobe's documentation sets technical limits but doesn't offer much guidance on the operational governance model to prevent getting there particularly in a large enterprise where multiple teams (CRM, digital, paid media, product) all have write access to the segment builder.A few things I'm genuinely curious how others have solved:Do you enforce a segment approval workflow before publish to production, and if so, is that a process control or is there a technical gate you've built?   How do you handle segment ownership when the original creator has left the team? Orphaned segments with no owner are our single biggest hygiene problem. Have you seen a material performance difference between

Is such a dataset created for every specific merge policy created in the sandbox?

I was recently setting up a webinar campaign in Marketo and noticed registration numbers looked a little higher than expected. (In an ideal scenario, I should be happy about it, but contrary to it, I was skeptical!) When I dug into the records, I found that some attendees already existed in the database. Instead of updating those records, a few were being created as new leads because the data from the webinar platform didn't consistently match.What surprised me was how normal the situation was. Nothing was broken. The integration was working. The records just looked different enough to be treated as new people.It reminded me that duplicate leads often come from everyday marketing activities rather than major system issues.Lately, I've been thinking more about preventing duplicates before they enter Marketo instead of cleaning them up later.Some teams handle this with validation rules, while others use Marketo deduplication tools to help standardize and match records earlier in the proc

Hi ​@Community I created two fields in a profile-enabled dataset : customer_id (primary string) and customer_number. The dataset is enabled for Profile and upsert. Both attributes are visible in the XDM union schema and in the Profile UI. However, after running the ProfileSnapshot job, the new attribute customer_number does not appear in the ProfileSnapshot dataset and is therefore not available for export. The customer_id (primary attribute) is available in other datasets as well and helps in stitching..I have verified the dataset and it contains values for customer_number and same is visible in profile UI. Please assist in finding why the profilesnapshot dataset is not getting populated with the new attribute from profile enabled dataset.

I have got the profile which has 30x profile attributes. It recently authenticated. Why the profile attributes are not propagated to EDGE? How to do that? I need to use them in AJO or AT and then these would be available on EDGE? 

Adobe Experience Platform provides the foundational capabilities for collecting, unifying, activating, and analyzing customer experience data. But practitioners involved in implementation, production support, QA, migrations, and ongoing enhancements often need to move quickly between Query Service, dataset previews, Real-Time Customer Profile lookup, audience validation, and ingestion workflows.That day-to-day investigation can become difficult when business stakeholder question that requires more than a sample preview or a high-level UI view. Often, it is required to inspect a specific profile with hundreds of its attributes and events, extract and deep dive into a specific dataset, not just a preview and investigate all the profiles included in an audience, a capability not available in current AEP UI. In many cases, the question is not simply whether data exists, but whether the right data exists in the right place and can be validated efficiently.I faced these same challenges while