3 ms·
Thank you! That's a very valid point and we've seen this with customers quite often: the thought of changing the whole underlying layer can (understandably) sca
by yoavm 6y ago
Thank you! That's a very valid point and we've seen this with customers quite often: the thought of changing the whole underlying layer can (understandably) scare people.
We've built a (soon-to-be-completely-)automated process of converting Google Tag Manager containers to Zaraz, and that helps a lot with convincing customers because everything Just Works without them needing to do anything (we also hook to their dataLayer events). For other tools it's still a work in progress, but in general we convert whatever stack a customer has to Zaraz as part of the onboarding process. Honestly that's one main reason why we don't yet offer a free tier.
- onassar 6y agoYep that all makes sense. I'm sure it's a tough job. For some context, our front end manages just 7 different libraries, but it's a pain to deal with so many edge cases. The worst and trickiest one was definitely ad blocking. We deal with a lot of edge cases whereby we're loading external resources that are not ads, but depending on browser/extension settings, were getting blocked. This would naturally cause bugs due to our assumptions. So centralizing this logic, I think, could have a direct correlation to revenue. eg. Stripe JS getting blocked, without us realizing it was for a small % of users.