Hello @AnkitJasani29 ,The issue has been resolved. We discovered that the problem was due to testing on an older version of iOS. Once the device is updated to the latest iOS version, thein-app messaging works as expected within the journey.Thank you for your valuable insights. ThanksAJODev

Hello @PadmajaS , Follow this documentation : https://developer.adobe.com/client-sdks/home/ ThanksAJODev

Hi @Ikmo7 ,Check this documentation: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/manage-journey/timezone-managementThanksAJODev

Hey @AnkitJasani29 ,do you have any idea why i have to configure in-app messaging through a campaign instead of a journey? is there any limitation or any in differences in how message delivery or rendering is handled between campaigns and journeys?Since it is working in android why not in IOS with j...

Hello @AnkitJasani29 , Yes i checked and see events in Assurance and i believe the issue is with IOS app.ThanksAJODev

Hi @FrankXu3 I believe this is current web channel limitation in AJO. Arrays of objects aren’t supported in web channel personalization because personalization engine is optimized for simple, fast, and secure substitutions.For complex data, flatten key attributes or handle rendering in your web appl...

Hello @Mikael_Strangnefjord , Yes, You can only assign one IP pool per email channel configuration even if you use dynamic subdomains within that configuration.You need to create a separate email configuration for each country, each with its own subdomain and assigned IP pool.This is the only way to...

Description -Currently, when we need to make changes to a published journey in AJO-such as updating content templates or making workflow adjustments-the only option is to stop the journey, duplicate it, edit the duplicate, and then publish it as a new version. This results in multiple versions of es...

Hello @learner_monk ,When you use streaming source with mappings, AEP can transform or map your incoming data to match the XDM schema, allowing for more flexibility in field names, structure, and types. With XDM Compatible enabled, this mapping step is skipped, so the payload must be a perfect match...

Hi @PadmajaS ,Add Initialization code in app.tsx file. ThanksAJODev