How many times a trackAction is activated with an ID that is not registered or is entered incorrectly within the native app code.
Taking into account that the development cycles for the deployment of applications within the different STORES (Android & IOS) can take months, these trackActions are dirtying the data and can sometimes increase the useless consumption of SERVER CALLS in your company.
This can cause unwanted SERVER CALLS billing.
Currently, the "CONTEXT DATA" data in the event we want can be modified through Adobe Launch, enriching the event from "Adobe Launch", but we cannot prevent a "SERVER CALL" from being executed even if we do not need it in our implementation.
How would you like the function to work?
Ideally, to avoid unwanted "SERVER CALLS", we would include an option in the "MOBILE CORE" where we could prevent the execution of a "trackAction" or a "trackState", conditioning based on its "action name" and/or contextData (in Adobe Launch UI).
Current behavior
There is no way to prevent a "SERVER CALL" from being consumed and counted, even if it is not controlled, or has been included by mistake within the source code of the mobile application through the "trackAction" / "trackState" events.
There are some issues in the community regarding this that are quite old.
This feature should be a "MUST" to better control the data that reaches the Report Suites, it would give a lot of flexibility and control over the data.
