The tag template does a few things, it does the extensions, mappings and any specifically required tag set up before firing the actual tag. Extensions run before mappings, but the rest of the sequence can change depending on which tag it is. Basically it does everything necessary to translate the Tealium UI/UDO information into what each tag vendor needs. That's why each tag has its own template, because each can be quite different. The JavaScript extension supports a tag by doing some kind of data manipulation usually that other extensions can't do. If you can do it in another extension, we recommend that as it makes it easier to maintain for non-technical users. You wouldn't normally use it to actually fire a tag. If you were to make your own custom tag, you should still use a custom tag container or other similar "tag" from the Tealium marketplace.
Not yet but we are constantly looking for ways to improve things. Note that when there are new versions, your version remains unchanged. We don't update anything for you automatically as we don't make changes to your profiles without your knowledge and permission.
We always recommend getting assistance from your account manager when needing to customize a tag template. Some example use cases of needing custom or modified work is you need a feature for a tag that just came out that Tealium doesn't support just yet. This happens sometimes with Google Universal Analytics which is constantly rolling out new features.
Anytime a template is customized, whether it is by you or Tealium, these changes are not preserved if you decide to update your tag template. This is why it's important to make sure you note in your tag's "notes" area the template is in fact custom, and to keep backups of your templates any time you do a change. Once you update, and if the customization is still necessary, it will need to be added to the updated template.
... View more