We are redoing an mobile application and was hoping to use Adobe Launch for the data collection piece to simplify the analytics in the mobile app.
We were under the expectation that we could call MobileCore.trackaction or MobileCore.trackState which would allow us in Adobe Launch to listen on those events. And then apply any additional logic (filter in/out etc) and then fire the appropriate Analytics tracking event.
In our mobile application pod we did define "pod 'AEPAnalytics'" per various copy/paste docs we saw.
But the behavior appears to be calling trackAction and trackState is just sending the requests to Analytics and bypassing / ignoring Adobe Launch.
Then we discovered this gem in the documentation which seems to prove the above:
So I guess the ultimate question is ... Do we remove "pod 'AEPAnalytics'" from our mobile code and that will allow us to have the track* calls go to Adobe launch? (We're going to experiment with this idea to prove it out but curious if there is better how to's and guides for this stuff. Based on a different ticket - Support kind of paraphrased the following: "documentation is lacking and in transition - how about this 3rd party link.")
The mobile app tracking using Adobe Launch is different from web tracking. In web tracking, you can control a lot of tracking logic using rules in Adobe Launch to trigger what to track or not. However, for mobile app tracking, even with Adobe Launch in place, tracking is actually going out directly from your mobile app when you call trackAction and trackState, even if you use the new Edge.sendEvent.
What you can do with Adobe Launch rule is to modify data sending out from trackAction/trackState but the capability of the rule configuration in mobile tracking is very limited when compared to web tracking.