Let's say you currently have, for example, a few tools firing after a purchase:

  fbq('pay', amount)
  ga('send', { hitType: 'event', eventCategory: 'Interaction', eventAction: 'Purchase', eventLabel: amount });
  ...

You would replace this whole block with

  zaraz.track("payment", {amount})

This would make one request go from the browser to Zaraz, and Zaraz will handle it from there. It would work without loading fbevents.js, analytics.js, and other tool-specific JS files.

For HubSpot's chat window we deliver a Facade (https://web.dev/third-party-facades/). Screen recording tools are harder to optimize, but we bundle their first JS with our response (saving a request for the browser), and we offer sampling them to only a percentage of your users (or based on some criteria, like not loading them for users with slow connections). We do this rules evaluation on our backend, unlike GTM and other tools that essentially are sending everything to all users and then evaluating things on the client side.