This is a good point. But it would mean more work on the Monarch side (and possibly more support for the analytics team when their customer messes up etc).
I would bet that the JS is an implementation shortcut, and a way for the analytics service to avoid doing customer-side implementation support. Keep things as simple as possible (which is a reasonable business goal).
Plus it means that the service you're using can refactor or change around how they handle things and you don't need to be updating your code all the time?
But the tradeoff is that you end up in this situation where people ask "why do you need to load a JS file from a third party?"
I would bet that the JS is an implementation shortcut, and a way for the analytics service to avoid doing customer-side implementation support. Keep things as simple as possible (which is a reasonable business goal).
Plus it means that the service you're using can refactor or change around how they handle things and you don't need to be updating your code all the time?
But the tradeoff is that you end up in this situation where people ask "why do you need to load a JS file from a third party?"