@EyeMed_Don Given that you already enabled Lifecycle reporting, which would have been my first question. The only thing that I can think of is that your 'new' reportsuite you do not have the same permissions as previous. Depending on how your permissions are granted in the Admin Console, it may be that you do not have the appropriate rights to see the everything for the new reportsuite. My other thought is that it is taken longer amount of time to enable the variables and to log out and log in a...

HiI took a quick look at reports and it shows that the message was delivered to 2 users. With a new implementation, it will take typical Analytics processing time in order for a user in a Analytics Segment to be realized. The app needs to be installed, a hit to VisitorID service, a hit to Analytics where the user has 'allowed' notifications (opt-in true) and then the hit to sync the VisitorID and the push token. Once all this is confirmed via Griffon/Charles/Debug Tool and you see an estimated a...

Hi George, In order to be able to edit variables within the Mobile Services UI, you are required to be an Analytics Admin. When logged into the Experience Cloud www.experiencecloud.adobe.com and you navigate to Admin, you need to add the user to the Analytics Product Admin. https://docs.adobe.com/content/help/en/mobile-services/using/get-started-ug/c-mob-roles-and-permissions.html Jen

Hi, The equivalent in the AEP SDK is "getSdkIdentities" found in the documentation here.https://aep-sdks.gitbook.io/docs/resources/privacy-and-gdpr#retrieving-stored-identifiers Jen

Hi, The link to describe sending trackState and trackAction is found here https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference#track-app-states-and-views Data with the Mobile SDK is sent as contextData therefore processing rules in Analytics will need to be created based on what you are sending via the methods, to be captured in the Analytics reporting for specific, evars/props/events. Jen