@PlabanDa1 This error ( Not Found), means that the referenced offer activity and/or placement is not available in the decisioning engine on the prod edge environment. This issue may occur in Adobe Journey Optimizer for several reasons: Staging vs. Production Synchronization - Entities (offers, activ...

@gengaipandi03 what's the error?

that's right @LuisCardenas 

@LuisCardenas I think this is documented somewhere, When you export/import journeys and dependencies, the mapping or schema linkage for contextual attributes sometimes breaks, or the imported message/template isn’t correctly flagged to accept contextual data.Your current workaround is the only broad...

@vikramcl  Use messageProfileID from the AJO Message Feedback Event Dataset messageProfileID is a unique GUID generated for each message sent to a recipient via a journey (including SMS).It exists in the AJO Message Feedback Event dataset and is specifically designed to identify each delivery to a p...

On the mapping screen, select the appropriate fields from your uploaded data to match the schema fields.Map: Email.key ⟶ the email address (from your data)Email.value.marketing.email.val ⟶ opt-in/out valueEmail.value.marketing.email.time ⟶ timestamp If you use the correct array of objects format, A...

@Michael_Soprano  "In Read audience or audience qualification journeys: the merge policy from the audience is used."Adobe Journey Optimizer | Journey PropertiesIf you update the merge policy for an audience, any active journey referencing that audience must be republished to access the new policy (s...

@gengaipandi03  The idSpecific attribute lives in the Consent Dataset (often named with consent, profileConsent, or similar). In most implementations, it’s tied directly to the Adobe Experience Platform XDM Individual Profile schema.The full field path (example): consents.idSpecific.Email.<email_add...

@gengaipandi03 Once a user unsubscribes via one-click (header), their idSpecific consent is set to n and there is currently no out-of-the-box way to reset it to y. To re-subscribe (set consent value n to y on idSpecific), you must perform an AEP ingestion/update directly to the dataset containing th...