That feature list in paragraph two is pretty weak.
Put google analytics on the page being retrieved by the tag, and you've got frequency and macro-location.
'Dynamically changing data-source?', I assume they are suggesting that the content retrieved is dynamic. Yet if the code is static, than the variables for the dynamic content aren't coming from the tag. So, again, this can be accomplished with any webpage.
The 'customized look' of the microsoft tag is probably its greatest weakness. If you look at the examples they provide, they aren't instantly recognizable as scannable tags, and they look horrible.
Comments
That feature list in paragraph two is pretty weak.
Put google analytics on the page being retrieved by the tag, and you've got frequency and macro-location.
'Dynamically changing data-source?', I assume they are suggesting that the content retrieved is dynamic. Yet if the code is static, than the variables for the dynamic content aren't coming from the tag. So, again, this can be accomplished with any webpage.
The 'customized look' of the microsoft tag is probably its greatest weakness. If you look at the examples they provide, they aren't instantly recognizable as scannable tags, and they look horrible.
There is no way what they are talking about is a function of the tag. It is more akin to a physical URL shortened, I imagine.