For one of my tracking scenario, Adobe is automatically generating a POST call potentially because the request size is greater than 2047 bytes, for that specific post-call we are seeing that one of the variables is not receiving a standard camel case value that we enforce through the plugin within app measurement library. What could be the reason for the same?
For other requests, the variable is displaying a similar problem, i.e. not being forced to the correct casing. But somehow this was never noticed till now.
For this particular request, it sounds like there's some extra processing being done, since more variables are being tracked. Could it be that somewhere in that extra code, this particular variable has been "reset" somehow such that your plugin is not being called?