Hi @Abie ,This issue is still ongoing. Despite deleting the dataflow and submitting the request from Postman, profiles are still being registered in Adobe Experience Platform (AEP).Based on the response from Adobe, we have parked the issue for now.

I got the below response from Adobe. Disabling the dataflow alone will not guarantee that ingestions are prevented. Since AEP auto create system dataflows if the target dataset is enabled for profile, data may still come in.

Hi @bjoern__koth ,Yes, I tried again just now, and profiles are still being registered in AEP. Thanks ,Mahesh  

Hi All,I have configured an HTTP API streaming dataflow and successfully tested it using Postman-profiles are appearing in AEP as expected. However, I recently disabled the dataflow and then submitted another request via Postman. Surprisingly, the profile was still registered in AEP, even though the...

Hi,As I understand, you can create a CTAS (Create Table As Select) statement by referencing the profile snapshot table and applying the required conditions. Please update the identity value as needed for your specific use case. This approach will provide all segment IDs associated with each profile....

Hi,When you send data to a profile-enabled dataset in Adobe Experience Platform, it goes into both the Data Lake and the Profile store ,there’s no way to split that up. If you want to keep some data out of customer profiles, start by putting it into a non-profile-enabled dataset so it stays just in ...