@VaniBhemarasetty - We are migrating from traditional data collection to AEP Mobile SDK (Implementing AA, AT, AAM and AEP through Edge and following XDM standard) from the mobile app front, could you please help me with this please.
1) Is there any way we can access XDM data field using Launch (all the XDM data fields are mapped from app front and triggered the send events) i.e, similar to accessing context data elements earlier.Is this feature will come near future if its not already available?
2) In the similar fashion earlier we tried to access OOTB data fields which Core library provides like below but they are coming empty after the libraries are upgraded
"appid": {%%app_id%%}, - not working
"ecid":{%%ecid%%}, - not working
whereas accessing them like below is working fine (https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-journey-optimizer-decisioning#define-...)
Solved! Go to Solution.
Views
Replies
Total Likes
@satyanarayanam1 Not sure, if attaching data to edge is supported yet from Adobe Launch. May be you can check with client care to know more on this
@satyanarayanam1 Not sure, if attaching data to edge is supported yet from Adobe Launch. May be you can check with client care to know more on this
Sure, I will check with them.
Also I have another question on Mobile App life cycle data and curious to know your thoughts.
When we implement life cycle tracking using edge approach following the tutorial in the link below, do we still need to implement the life cycle calls manually on the app end calling lifecyclestart and lifecyclepause methods explicitly?
Will the below edge approach works for both Android & IOS to populate all the lifecycle metrics and dimensions?
Views
Replies
Total Likes
We are facing similar issue with our implementation after upgrading to AEP Mobile SDK. Lifecycle Metrics like appID are returning empty values when trying to fetch them using data elements utilizing Mobile Core Extension and Lifecycle Type.
Views
Replies
Total Likes
@yatins78957443 - for the OOTB life cycle events the app id gets auto tracked. Are you referring to the custom events that you trigger for track state or track action (pageview, interaction) calls?
If yes, we also noticed the same thing. By default, mobile sdk doesn't attach the app id to custom events, you might have to work with developers to attach it manually similar to how you do the XDM mapping.
Views
Replies
Total Likes