Based on the question, we need to combine two different table to see the journey name. This is common issue for everyone, instead, they would have place that attribute in tracking and feedback status table itself will solve unwanted query in the system. 

Normally message id will be different from before and after execution, will that be same for all the tables? AE._experience.customerJourneyManagement.entities.channelDetails.messageID = MF._experience.customerJourneyManagement.messageExecution.messageID

Basically, event forwarding can be done through the edge level. Once you configure the event forwarding, using that json, can we send to AJO for API triggered email? Let me know if you still need further details. 

Thanks, i tried in my development sandbox where it is removing total profile details when we use the namespace and the expiry date in the profile settings like the below 

Hi, In addition to the below offer setup, this is for your later suggestion as keep the offers in same collection. you can capping like the below to show the second offer after some number of decisioning happen. So use priority and capping on the same collection will be ok for your needs.  

@Asheesh_Pandey , @bjoern__koth please check if you can assist here

yes, it works as per your expectation. Basically, from email 1 if a person unsubscribe then he will be excluded from email 2 automatically provided, we need to use the native landing page unsubscribe solution which automatically store the"XDM Individual Profile>  Consents and Preferences > Id Specif...

Is there any way Adobe going to fix it in the future? 

Based your details, i can see the following suggestions.  1. As you have more than one topic like newsletter, promos etc.. you should create the subscription list first and create the landing page with these options to optin or optout through email, you can collect these preference. 2. once it is co...

I am planning to create a new profile where unique namespace is going to be created which is not available for any other profile. it is a proper profile upload where we enable the dataset for profile enabled. if i use that namespace id for pseudonymous profile deletion. Will that work ?