It doesn't matter how scrumtrelescent MixPanel is, cross-site javascript inclusion from third parties is extraordinarily unwelcome on a site that exposes full access to my banking to the DOM.
How you can not understand this and still work at a fucking bank? (even an affiliate one)
Does that mean you're only going to use them on the brochure side of the site?
There is no way I'm going to be your customer if you intentionally leak my financial actions to two third-parties to get analytics or grant full client-side access to my bank account to them along with a third just for fancy fonts. Sure I could block them in my browser but I'm not going to use a bank that would even try that shit.
"Does that mean you're only going to use them on the brochure side of the site?"
Congratulations. You're actually attributing a bit of reason to us. Conversations will be much more productive now. In any case, Mixpanel is easier to integrate on pages with secure data than typekit. There are ways, albeit ways that further narrow our browser compatibility profile.
But I can't get past the idea that you trust Google's scripts with your financial data. They're the single biggest target on the internet; if anyone wants a big score GA is going to be where they hit first. Even 5 minutes serving to GA pages could potentially result in millions of stolen passwords.
I'd assumed that at first but your statement about how absolutely every rich site should be using MixPanel hinted at something so unreasonable that it made me "take you down a peg in my estimation".
I don't trust Google that much, I just trust the others far less — there are degrees of infinitesimals! Besides, an untargeted score on GA would be such a hueg firehose that y'all would be way down the list of people to sift through data for much less prewrite an exploit for.
Even you writing your own code to ship specifically detuned events to MixPanel makes me somewhat uneasy.
How you can not understand this and still work at a fucking bank? (even an affiliate one)