|
|
|
|
|
|
by ashray
5005 days ago
|
|
|
Interesting, so as I understand this - it allows 'marketers' to insert javascript code into a website when they want to do something 'new'. (maybe they want to put crazyegg on there, or do something else.. ?) I see where this is trying to help out. But allowing marketers/non-tech-folks to inject copy-pasta javascript into production isn't really a solution I would be comfortable with. Having experienced how small snippets of seemingly inconsequential JS can cause 'ads to fail on IE8' (and this is through DFP, no less!) and thus cause thousands if not millions of dollars of losses makes me nervous about having marketing dudes insert them codes and then go "hey I didn't know it'd break something!". However, on a positive note, I would definitely use it personally to asynchronously load up stuff on my own projects. But on the other hand, I could do that manually myself and actually take care of caching aspects and expires headers, etc. Sorry but I don't see the whole 'speed-up load times' thing as a big bonus unless it's for small projects where you can't afford to deploy on S3/Cloudfront/etc. but on that note, those people won't have 'someone in marketing' wanting to insert their code during runtime. Maybe you should change the marketing angle including explaining the phrase 'tag manager' better ? |
|
|
I think that for complex sites you have a good point on letting anyone publish tags. Fortunately, it's possible to allow users just to view and edit tags - and not publish them. This leaves the testing and publishing to IT - our testing interface is pretty good - perhaps you could test it :)
The speed up is really around asynchronous firing of tags and for that it may not matter where code is hosted. This should help in situations with either synchronous or poorly designed code (in some situations it may not lead to a measurable improvement).
You've got a good point - we've got more work to do explaining this topic. Thanks for the feedback!