I don't disagree with the thought that a well-built system should be able to reject the additional fields; I actually changed my process to do just that as protection in the future and it is a much better solution than what I had.  However, I am disappointed by Adobe's response above.  Maybe I'm jus...

I just got this reply on my support ticket: The fix is pushed to prod. Additional fields `itemIds` and `values` are removed from the response in traditional analytics. 

Latest reply from Support:  The fix is pushed to prod. Additional fields `itemIds` and `values` are removed from the response in traditional analytics. 

The API is still reporting the same fields and has not been addressed.  I just ran a request to the API to make sure.

Just submitted a ticket through the Admin Console.  Hopefully they can figure it out.

We are having that issue also, with no changes to our codebase.  The response from the API has these new arrays so it isn't on our end.