Adobe Experience Platform

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      }    }    ],

I need to configure that some Identity Namespaces be unique in Identity Service:IdentityA - entity 1 IdentityB - entity 2 IdentityC - entity 3 Additionally I need to configure the priorities. That is in the description of the priorities:Segmentation service: For each merged profile, segment memberships are recorded under the identity with the highest namespace priority.Lets assume that some customer has both IdenityA and IdentityB. However IdentityA has a higher priority. I configure the audience and different people fall into that audience (some has IdentityA, some has IdentityB and some has both). However when I create batch journey I need to choose the namespace.Does the people which fall into the audience which has IdentityB fall into that journey if they do not have IdentityA and IdentityA is the core namespace for that journey? 

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?

In one of our Web SDK implementations in AEP, we are collecting form data through an HTTP API, and the prospect email ID is being used as the primary identity. During the initial data flow mapping, we did not apply a lowercase transformation to the email field, so email values entered in uppercase were ingested into CDP as-is.We are now implementing lowercase mapping for the email value in the data flow. However, this is creating an issue because the historical records already stored in uppercase are resulting in separate profiles in CDP. To avoid duplicate profiles, we would like to apply lowercase mapping to the historical data as well in the AEP Profile UI.Could you please guide us the best approach on how to do this? other than reingestion 

Hello Folks, I am looking for a sanity check from anyone who has done this in production.My current setup Snowflake is our SoR for transactional/behavioral data (can't fully ingest into AEP due to cost + governance) AEP RTCDP holds identity, consent, streaming web/mobile events FAC federates the heavy Snowflake attributes (RFM, ownership, propensity) AJO for orchestration, Data Distiller for computed attributes There are around 80M profiles Currently the problem is :Business wants a Lapsed High-Value Reactivation journey that: Qualifies on a 180-day look-back in Snowflake (via FAC) Enters within approx. 30 min of a real-time cart-abandon event Personalizes with Snowflake attributes that can change intra-day The conflict: FAC audiences are batch-only, so they can't drive real-time journey entry. If I materialize everything into AEP via Data Distiller, I blow the profile budget and lose Snowflake as SoR.I would like to know :  Has anyone made a pattern work where FAC provides

Hi everyone,I'm running into an issue with an Event Forwarding CAPI integration and was wondering if anyone has encountered something similar.We're consistently receiving a 403 response from the destination endpoint. The response message indicates that the client IP address is in the banned country list.What's puzzling is that the requests are being sent from our Event Forwarding setup, and the vendor has stated that they do not believe the issue is on their side.A few questions for the group:Have you seen a similar 403 error related to a banned-country or geo-restriction policy? Is there a way to determine the actual source IP being used by the Event Forwarding request? Could this be caused by proxying, cloud infrastructure, or regional routing that results in requests originating from an unexpected location? Were there any configuration changes or allowlisting steps required to resolve it?Any insights, troubleshooting tips, or similar experiences would be greatly appreciated.Thanks i

Hi community,I have an use case to track the URL parameters via WebSDK and sendEvent with this params to AEP/AJO for Journey Triggers. However the challenge is that some of the URL params are needed to be encoded e.g. profile identity; Encoding via AJO should be feasible with helper functions, however I am not sure how can we implement decode logic at WebSDK level for the same identity. So that the incoming event from WebSDK can be stitched to the same identity, before sending any comm via AJO. Looking for your suggestions.  

Hi Adobe Community,We are designing a personalization architecture for our company’s website and mobile app using Adobe Experience Cloud, and I would appreciate hearing how others have implemented a similar solution.Our current ecosystem includes:Adobe Experience Platform (Real-Time CDP) Adobe Experience Manager (Content Fragments / Experience Fragments) Adobe Target Adobe Journey Optimizer (AJO)Our objective is to build a scalable content matrix that supports omnichannel personalization across website, mobile app, email, and push notifications.Our current thinking is:AEM serves as the central content repository where reusable Content Fragments/Experience Fragments are managed. Customer profiles, audiences, and behavioral data are managed in Real-Time CDP. Adobe Target delivers personalized website and app experiences. AJO orchestrates personalized customer journeys across email, push, SMS, and in-app messaging.However, we still have several architectural questions:How should the conte

Hi everyone,I'm working on a scheduled Data Distiller job that computes an eligibility flag for entities and writes the results to a Profile-enabled dataset.One of the output attributes is a timestamp that should represent when the entity first became eligible.The desired behavior is:If an entity transitions from not eligible → eligible, set the timestamp to CURRENT_TIMESTAMP. If the entity remains eligible in subsequent scheduled runs, preserve the original timestamp. If the entity becomes ineligible, reset the timestamp (or set it to NULL).Conceptually, the logic would be similar to:CASEWHEN current.isEligible = TRUEAND (previous.isEligible = FALSE OR previous.isEligible IS NULL)    THEN CURRENT_TIMESTAMPWHEN current.isEligible = TRUEAND previous.isEligible = TRUETHEN previous.EligibilityTimestamp    ELSE NULL ENDMy questions are:Is it supported to read the previous state from a Profile-enabled dataset and write the updated results back to the same dataset within a scheduled Data Dis

Hi, In AEP identity stitching is not happening properly and not showing data in events when we create 1 individual profile schema and 1 experience event schema when we have same identity namespace in both the schemas. Can anyone please help me on the same

I created a custom destination using Adobe Experience Platform Destination SDK. The destination activates audience data from AEP to a Salesforce Marketing Cloud Data Extension.As part of the activation, we need to send the AEP audience/segment name displayed in the AEP UI to SFMC. We do not want to send the mapping ID or segment ID.I found documentation and examples for passing the segment ID, but I could not find a supported parameter for passing the segment name.Could someone clarify: Is the AEP audience/segment name available to a custom destination during activation? If so, which Destination SDK field or transformation macro should be used? Can the segment name be included as a column in each activated record sent to the SFMC Data Extension? If this is not supported directly, what is the recommended approach for resolving the segment ID to the audience name? Any configuration or payload examples would be appreciated.

What should be the payload if the data is non XDM? I use Data Prep … Its not explained and I got the errors :(https://developer.adobe.com/experience-platform-apis/references/streaming-ingestion#operation/sendMessage

RTCP keeps only last profile fragment (XDM Individual Profile). How that looks like when it comes to Data Lake? 

I have got the case like this:Unrecognized User - ECID is added server side to IdentityMap  User logs in. a) I use email as an identity (but email has to be unique - only one in the profile - configured in Identity Service).  b) Data Element for that email is populated and added to the IndentityMap. I want that data element also be populated in the following events. SHould it be stored like that?Then the user logs-out  User logs in to the another account. Identity Service disjoin these profiles. I assume I need to clear IdentityMap and add new one. Any tips?What are your tips to manage IdentityMap?

Could somebody explain me what is “use guided events”?What is the specific use-case for that??

Assume that I have a crazy use-case like that. Customer has one Customer IDs. However he might have multiple Loyalty IDs. I can set up these as array with multiple Loyalty IDs. Are there any edge-cases for such a use-case? 

Hi AEP Community!Looking to sharpen your Adobe skills, discover new ways to work smarter with AI, and learn directly from Adobe experts and customers? Skill Exchange 2026 registration is officially open! 🚀  Adobe Experience Platform sessions will be held on August 6th, with sessions across 7 Adobe products throughout Aug 5th-13th. A couple sessions you can expect to learn from: One Platform, One Customer Governing at Scale: Building a Trustworthy Data Foundation  Building an Intelligent Activation Layer and Orchestration Drives Results See full Adobe Experience Platform session list here  Join us this August for: ✨ Expert-led sessions across 7 Adobe products 🤖 AI-powered tips and innovations 💡 Real customer stories 🎬 Live demos and practical takeaways you can apply right away 🤝 Opportunities to connect with fellow Experience Makers  Whether you're just getting started or looking to level up your expertise, there's something for everyone.  🎟️ Save your spot today: [Register Now]  

We have created multiple FAC workflows, and each workflow creates a saved audience. These audiences have also been activated to an S3 destination.Now we need to completely remove one of these audiences from the system, including:The S3 destination activation The saved audience The FAC workflowHowever, I don't remember which FAC workflow created this audience. Is there a way to identify the FAC workflow using only the audience name?Also, what is the correct deletion sequence? If I delete the audience, will it automatically remove the activation from the destination and stop/delete the associated dataflow run workflow, or do these need to be deleted separately? ​@SanfordWhiteman ​@JennaFeldman ​@stephaniedam ​@Jennifer_Dungan ​@NicholeVargas 

Currently, the native Marketo Engage integration uses Adobe's Sources connector framework & not Data Collection Core Service (DCCS). Data lands in the Data Lake and Real-Time Profile (which is why you can see it in Profile browse), however it never passes through DCCS nor does it create Unitary Events that would be extremely helpful for AJO use cases for triggering journeys based on Marketo engagement events & activities. Especially when we want to designate specific users and/or email addresses for the journeys in AJO when profiles have multiples per profile.Options for workarounds exists, however labor intensive & data heavy.Stand up a streaming ingestion path for the same events, so that they arrive via DCCS/Edge, which AJO B2C can listen to as a Unitary Event. Use AEP Audience (streaming) + Read Audience in AJO B2C, store the trail downloaded email in a lookup dataset either at ingestion time (a field like trail_email) or use Data Distiller to write it on a schedule. La

Hi All,For batch ingestion via Source Connector, we have been using field descriptors for hashed email and phone identities. We are now evaluating a move to identityMap approach.One thing we want to confirm before migrating — when a user's email or phone updates in a new batch, does AEP automatically remove the old identity node from the graph?Or does the old node persist and require manual cleanup? Curious if anyone has observed this behavior in production.

My question is:Does authenticatedState have any real-world impact when data is ingested via batch Source Connector?Or is it only meaningful for WebSDK / Mobile SDK scenarios where events are received in real time via Edge Network?

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?