Access over Mobile tagging on Launch

[harshu24]

When we provide the data layer to mobile developers, they integrate it into their code and release it on the go-live date. Is it possible to abort or control any tracking tags (like trackAction or trackState) in Adobe Launch when they are triggered by specific user actions? Or is it solely in the control of the mobile developers to manage or abort tracking events once they implement the SDK?

[SumitK4]

You're asking about controlling tracking tags like trackAction and trackState in adobe launch for mobile apps. Mobile tracking with adobe launch works differently than web tracking.While in Web Tracking, Launch(Tags) rules give you a lot of control over when tracking happens. For Mobile Tracking, when your mobile app developer uses trackAction or trackState, the tracking call comes directly from the app code. So only developer control those calls.

However, Launch rules mainly attach the data that's being sent with these tracking calls. They don't usually stop the tracking itself.

Exception (Rare case): Also, there is an exception to this, if you've set up a Launch rule to itself trigger a trackAction or trackStateusing the extension, then you could control that specific trigger from Launch. But this is uncommon as we ask most of the time developer to trigger it.

So, your mobile app developers are primarily responsible for deciding when to call trackAction and trackState which are triggered within the app code. Launch helps you manage the data associated with those calls, not the calls themselves or in rare case if any such rules are triggered by launch extension in the Action, only those can be controlled through launch.

Let me know if you have any other questions.