Adobe Real-Time Customer Data Platform

Hi,   I have no idea if this is the correct place for this, but I didn’t see anything else that was close.   I don’t know if you can help me with this or maybe point me in the right direction. I checked a few U-Tube videos, but they almost seemed to be in complete opposite directions from each other.   Anyway, I was not paying close enough attention and formatted the external hard drive #1 that I have used for several years to store my digital files. I also have other external hard drives #2 and #3 and a cloud account that also had (almost) all of the files on it. So, I have all of the digital images with the exception of several days that I still had on two memory cards. One of the things that I tried was clicking on an image in Lightroom Classic and when it asks where the file is located I clicked on the external drive, year, month, and day and they ‘find’ the file. The problem is that with hundreds of dates in seven years to locate that day it will take forever. Also, there were sev

Hi,We are currently reviewing how to control which fields of WebSDK datastream are ingested into Real-Time Customer Profile while still retaining the full dataset in the Data Lake.For the Adobe Analytics source connector, Adobe provides the Column-level filtering capability, which allows specific columns to be selected for ingestion into Profile while the remaining columns continue to be available in the Data Lake:https://experienceleague.adobe.com/en/docs/experience-platform/sources/ui-tutorials/create/adobe-applications/analytics#filtering-for-profileFor example, with Analytics data we could configure the ingestion so that only eVar1, eVar2 and eVar3 are included in Profile, while the rest of the Analytics fields are still ingested into the Data Lake but do not contribute to Profile.We would like to achieve the same behavior for data collected directly through Adobe Experience Platform Web SDK.I have the following questions: Is there an equivalent column-level filtering capability fo

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

This feature only works with Campaign Orchestration?Enable change data capture for source connections in the API | Adobe Experience Platform

This is turn on. It collects automatically all clicks in AJO web campaigns in Offer Decisioning campaigns in Web? 

I need to delete two XDM schemas in a development sandbox and I've hit what looks like a closed loop. Hoping someone has been here before.What I'm trying to doSome field paths in our dev sandbox differ from prod by character case only - for example campaignUseCase1 in dev versus CampaignUsecase1 in prod. Since XDM field paths are immutable once created, I understand the fix is to rebuild the field group and schemas correctly rather than edit them in place.Where it breaksI can't create the correctly-cased fields while the incorrect ones exist, because both paths would land in the same Profile union and AEP rejects paths that differ only by case. So the old objects have to go first.But:I can't delete the field group - two schemas compose it. I can't delete those schemas - both are Profile (union) enabled. I can't disable Profile in the UI - the toggle is there but Save stays greyed out. I can't remove the union tag via API. PATCH on the schema with {"op": "remove", "path": "/meta:immutab

From Audiences to Insight: Identifying Your Most Valuable Customers If you're running Adobe Real-Time CDP, you've already done the hard part. Your data sources are connected. Identities are stitched. Profiles are unified, and your team can build an audience and activate it across channels in minutes.So, here's the question worth sitting with: open your audience builder right now. Can you segment on how much each customer is actually worth to your business, ranked, current, and ready to activate today?Most Real-Time CDP teams can't. And the reason isn't a gap in Real-Time CDP. It's that the attribute you'd need to segment on doesn't exist on the profile yet.The limits you've probably already hitReal-Time CDP gives you computed attributes, a genuinely useful way to aggregate event-level data up to the profile. If you need a count of purchases in the last 30 days, that's exactly the right tool.But computed attributes work within the boundaries of the Profile Store. They operate on a pre-d

Hi Community,We're working on a use case where we need to surface ExperienceEvent-derived values at the profile level so they can be activated to a destination specifically Adobe Campaign Classic  for email personalization.Can we use Computed Attributes to aggregate ExperienceEvent data (e.g. last purchase date, total orders in last 90 days, last product viewed) onto the profile, and then have those values flow through standard Audience Activation to ACC as regular profile fields?Specifically looking to validate:Whether Computed Attributes are fully supported in the ACC destination activation flow Whether the aggregated values appear as mappable fields during the audience-to-destination mapping step Whether there are any limitations or gotchas with Computed Attributes in this context (e.g. lookback window limits, supported aggregation functions, refresh latency)Our current stack:AEP (Real-Time CDP) Adobe Campaign Classic as destination Azure Data Lake Storage as intermediaryAny guidanc

Source system is ingesting data to AEP-XDM dataset at specific time of the day.Data distiller copies the data from AEP-XDM to OCM-Relational tables at specific time of the dayData distiller performs transformation job on the data present in OCM-Relational tables at specific time of the dayAudience are evaluated at specific time of the day.Campaign which are using those audiences are evaluated at specific time of the day.How do we get E2E timeline view of this ? Are there set of APIs that can be called to get such a timeline view ?

Hi Real-Time CDP 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 Real-Time CDP (alongside Adobe Experience Platform and Applications (Journey Optimizer and Customer Journey Analytics) 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 From Insight to Impact: Building a Next-Generation Experimentation Program Building an Intelligent Activation Layer and Orchestration Drives Results See full Adobe Experience Platform and Applications 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 y

Trade desk integration enhancements that connect paid to own.Adobe and The Trade Desk are helping brands bridge the gap between paid media and owned customer experiences by bringing advertising exposure data back into Real-Time CDP. By connecting paid media engagement signals with customer profiles, organizations can gain a more complete understanding of customer behavior and use those insights to improve audience segmentation, personalization, and future marketing efforts.Why It MattersToo often, paid media insights remain isolated within advertising platforms. By turning media exposure data into actionable first-party intelligence, brands can create richer customer profiles, improve customer experiences across owned channels, and make future campaigns more effective. This connected approach helps organizations move beyond campaign reporting to continuous audience learning and optimization.Learn MoreSee how Adobe and The Trade Desk are helping brands connect paid media performance wit

We are configuring a destination in Adobe Experience Platform using Destination SDK server configuration. We are able to create the connection and send profiles to the destination, but the payload is resolving to null values even though the source attributes are populated.We are using PEBBLE_V1 in the requestBody template and referencing nested profile attributes under personal_details, we are looking for guidance on whether there is any syntax issue in the template logic that could cause populated fields to resolve as null.structure:{  "templatingStrategy": "PEBBLE_V1",  "value": "{\n  \"items\": [\n    {% for profile in input.profiles %}\n    {\n      \"firstname\": {% if profile.personal_details.first_name is empty %}null{% else %}\"{{ profile.personal_details.first_name }}\"{% endif %},\n      \"lastname\": {% if profile.personal_details.last_name is empty %}null{% else %}\"{{ profile.personal_details.last_name }}\"{% endif %},\n      \"emailaddress\": {% if profile.personal_detail

when we execute a query, is there a away to find if query used regular QS vs data distiller ? 

 The Problem StatementWhen the same customer profile is ingested to multiple Profile-enabled datasets, how does Adobe Experience Platform (AEP) determine which attribute values appear in the Real-Time Customer Profile?More specifically,Does Dataset Precedence behave differently from Timestamp Ordered? Does Batch or Streaming ingestion affect the final profile?Common Understanding of Merge Policies      Most users assume that Timestamp Ordered replaces the entire customer profile with the latest ingested record, while Dataset Precedence always uses all values from the higher-priority dataset. However, AEP merge policies don't work at the record level. Instead, they evaluate individual attributes based on the configured merge policy, often producing results that differ from these common expectations.Let's validate this with a simple test. To understand this behaviour, I created the following setup in Adobe Experience Platform.2 XDM Individual Profile Schemas with same set of attributes P

Adobe Accelerates Agentic AI Adoption Through New Agency and Technology PartnershipsAdobe is expanding its ecosystem of agency, technology, and AI partners to help organizations create, activate, and measure personalized customer experiences at scale. New collaborations with companies including WPP, Accenture, Omnicom, Stagwell's Code and Theory, Anthropic, and Microsoft bring together content, customer data, and AI to help brands deliver more connected, intelligent customer experiences while maintaining governance and brand integrity.Why It MattersAs organizations move from experimenting with AI to operationalizing it across marketing and customer experience workflows, they need a trusted foundation that connects creativity, data, and AI. Adobe's expanding ecosystem helps brands unify paid and owned channels, automate customer experience delivery, and gain deeper insights that drive more relevant engagement and measurable business outcomes.Learn MoreDiscover how Adobe and its ecosyste

Turn Media Network Potential into Performance with Adobe Real-Time CDP CollaborationAs commerce media continues to grow, media networks are under pressure to turn valuable first-party data into scalable advertiser revenue. Adobe Real-Time CDP Collaboration helps media networks connect audience discovery, activation, measurement, and creative workflows in a single privacy-centric solution, making it easier to deliver better targeting, stronger performance insights, and more impactful advertiser experiences.Why It MattersToday's media networks need more than audience access to stand out. Adobe helps organizations scale audience monetization, connect advertisers with valuable first-, second-, and third-party insights, streamline campaign execution, and measure outcomes with greater confidence, all while maintaining strong privacy controls. That’s what Adobe Real-Time CDP Collaboration for Media Networks is built to do. With native connectivity across the Adobe AI Platform, it enables true

When I am working on Adobe another website automatically opens called Adobe Genuine Service, that tells me my Adobe is not genuine and I should buy from this website. While in fact I have a licensed version. I am not able to block the link since it says adobe.com

In AEP - Profiles/Overview there are these two widgets:Customer AI scoring summaryCustomer AI distribution of scoresNothing is displayed, but a message saying: "You don’t have permission to access this feature.Permission needed: view-is-customer-ai, manage-is-customer-ai"What are these two permissions and how can they be granted? I checked under Administration/Permissions but couldn't find anything of the sorts. Adobe documentation didn't help either.Thanks.

Hi Team, We are sending data to Event hub Destination and the source of the records are streaming. We have observed that even after profiles no longer meet the audience criteria, records are still being sent to the destination (at least for the first occurrence after exit).After reviewing the Adobe documentation on Profile Export Behavior, it appears that this is expected behavior in AEP for enterprise streaming destinations.Profile export behavior | Adobe Experience PlatformHas anyone encountered a similar scenario earlier? If so, could you please suggest any potential workaround or best practices to handle this? Thanks in Advance Regards,Mustufa Momin