Describe the issue

Shopper usage tracking utilizes Ajax requests to record activity at various touchpoints during the checkout process. Each record event emits a separate Ajax request. For high-traffic stores, there can be a high amount of Tracks originated requests hitting the merchant server.

Shopper Tracks events are enabled by default and does not follow the merchant's Tracks opt-out checkbox.

1. We need to investigate ways to reduce the number of requests going to the merchant server. One option is making these requests in batches. One thing to be cautious of with such an approach is that we need to store the correct timestamp of the user action (not the request timestamp). This will require some refactoring of tracks_build_event_obj function.

2. Consider introducing a new filter to disable front-end tracking altogether when needed.

3. Consider respecting the existing merchant's Tracks opt-out checkbox.