@ZacharyTa1 In Adobe Experience Platform, lookup schema attributes (like Coupon Name in your case) are not automatically available for event-based segmentation. You should ensure Make sure the dataset is enabled for profile.The join key (Coupon Master Id) is mapped as an identity in both schemas and...

@AndrewWe15 I'd recommend to escalate to Adobe Support with IDs Share: Dataset ID, Purge Request ID, and last successful ingestion Job ID. Ask them to check for a dataset ingestion lock and uncompleted purge cleanup in the backend pipeline.

@PrikshitBa Here are steps 1. Use the Catalog Service API to fetch dataset details. 2. Now call the Schema Registry API to fetch the schema. 3. In the response, under meta:identity, inside the field definitions, you will see "primary": true - This marks the primary identity field.  

@Rockett All data used by Experience Platform is encrypted in transit and at rest to keep data secure. AEP Data Security Architecture : https://experienceleague.adobe.com/en/docs/experience-platform/landing/governance-privacy-security/encryption  Data stored on Adobe Experience Platform is encrypte...

@gautham_madala  The Weather Channel provides APIs for accessing weather data. Check public pricing to access API on https://www.weathercompany.com/weather-data-apis/

@venkataak Yes, you can update the field mapping for an existing destination in AEP without recreating the destination or dataflow, but there are a few limitations depending on the destination type and integration method.  Use the Flow Service API to list your existing dataflows https://developer.ad...

@BrandonFa6 you would need to send signals to AEP using either of the methods. upload updated records via batch ingestion. Ex. update the schema consents.collect.val set to "Y" and a current timestamp.send consent updates in real-time using streaming Ingestion or Edge Network APIs.capture consent ch...

@VimalRa1 moved it from AEP to AEM community.

@RS195 These dash normally gets update once in 24 hours. It problem persist, contact client care. Alternatively visit Customer > Profiles > Profile count trend line chart.  

@SahuSa1 It usually means that AEP is not able to evaluate the consent condition. I recommend using the Policy Service API to manually evaluate which profiles match the condition.