@NestorAr I think you should receive the notification with FCM implemented, let us know if you face any issue I will check with our mobile team.

Flutter wrapper doesn’t expose MobileCore.setPushIdentifier(token) directly. So you have to Fetch the Firebase token in the native Android/iOS code Call MobileCore.setPushIdentifier(token); from native code and not directly from Flutter. @NestorAr  After initializing things natively, the messages sh...

@Silvio6 you may need to clone and re-map to a new surface.

@Silvio6  Updating certain fields (like execution address) on surfaces that are already active is now restricted for compliance/stability reasons.You typically can only change this for: New surfacesSurfaces in draft/pending states

yes there are certain limitations when using profile.timeSeriesEvents (and its fields, like identityMap). just thinking it may be due to limited support for iterating or calling deep-access helpers on collections/arrays within offers.  https://experienceleague.adobe.com/en/docs/journey-optimizer/usi...

@Michael_Soprano  For fixed placements (such as specific in-app locations for offers), the recommended integration pattern is to use the Edge Decisioning.

@FrankXu3 profile.timeSeriesEvents is an array of event objects, each with its own identityMap. profile.timeSeriesEvents.identityMap means: "the array of identityMaps for each event"  so it’s actually an array of maps, not a map by itself. try this: select the first event, then access its identityMa...

@Selliers can you submit this request as feature request via support portal, I will take it to our product team once support has the request. 

@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...