10-29-2017 02:58 AM - edited 10-29-2017 02:59 AM
we need to have available the tealium version (for instance what you place as comment at the begging for utag.js: "ut4.0.201710271217") within preloader extension. There is any placeholder of yours (similar to this syntax ##UTGEN##) that we can use for that?
By the way... other side question, do you have a full list of ##UTGEN## placeholder we can use?
Solved! Go to Solution.
##UT## variables are generated/evaluated during publish, but they must exist within the template code in order to be generated/evaluated. I'm sure you've seen that if you put a
##UT## declaration in a pre-loader it won't evaluate.
We are always very hesitant to touch templates because it makes upgrading to newer versions rather tedious and can become difficult. However, you could always add a line of code
myversion="##UTVERSION##"; directly to the uTag Loader template before/after
##UTLOADEXTENSIONS## to output the version.
What I'd like to know is what you're trying to accomplish such that this is needed so soon in the library. Pre-loader extensions are rather uncommon, it's typically better to configure a standard extension and set it to execute before load rules. At this point, utag.cfg.v would be available in a very simple configuration:
If you're able to provide a bit more detail then I will be glad to provide more insight.
11-03-2017 01:38 PM - last edited on 11-03-2017 01:45 PM by kathleen_jo
technical replies like your are always extremly apreciated.
We use preloader exts to load a sort of libraries we can easily call at every tracking loop.
At the beginning of preloaders we push to browser console some information and hilighting the version of Tealium currently loaded is something really important during our test/development.
Thanks for the idea you shared.