What is a good pattern for data marshaling between JS modules?

This question is regarding a best practice for structuring data objects using JS Modules on the server for consumption by another module.

We have many modules for a web application, like login view, form handlers, that contain disparate fragments of data, like user state, application state, etc. which we need to be send to an analytics suite that requires a specific object format. Where should we map the data? (Pick things we want to send, rename keys, delete unwanted values.)

1. In each module. E.g.: Login knows about analytics and its formatting requirements.
2. In an analytics module. Now analytics has to know about each and every module's source format.
3. In separate [module]-analytics modules. Then we'll have dozen of files which don't have much context to debug and understand.

My team is split on what is the right design. I'm curious if there is some authoritative voice on the subject that can help us settle this.

Thanks in advance!