As you stated, that implementation is done and SSF is enabled. So, if any AA variable fires in the AA call while accessing the mobile app, then those AA variables will be hitting the AAM server as signals (key value pairs).
You can check the unused signal reports, and you will be able to see some signals coming from mobile app like these: c_contextdata.[signalname]
You need to create your traits using these signals. If you want to filter with more granularity then you can also add platform variables (signals). Check this doc on platform variables for devices: Device Targeting With Platform-level Keys
I am not sure, I understood your query properly or not. But as per my understanding you want to share/ utilize Audience manager segments with your Mobile App using adobe SDK. Also you want to use it in a way shared destination so you can control the segment to share. So, for that:
- first your need to implement Audience Manager through Mobile SDK. For SDK code please refer SDK Code link.
- Once implemented you will start capturing signals into Audience Manager and make traits and segments out of those Signals. (Make sure while using Data Source, it should be type "Device Advertising ID". This setting is used to identify mobile devices.)
- Once you have the segments with you then you can use that segment via Audience Lab feature to share it with different destinations and can see/ analyze which third party destination is performing well for you.
Hope this helps, let me know if you have any further query or I misunderstood your query.
As far as I'm aware, this process is fairly similar in v5 and Launch. The difference is that you can deploy new configurations to your SDK and deploy new tools for the SDK without needing to publish a new version of your app to the app store. With that said, you could post a question in the Adobe Experience Platform SDKs community to be sure. We've got our experts on the SDK monitoring that community.