We currently have a process in place to download our Tealium utag files into our source control, but we have discovered that when we have whitelist load rules, this can prevent the automated job from seeing certain tags. Can you set and define global load rules... or scope multiple load rules to a tag?
Or is the best practice to just add an exception for this automation job to any whitelist load rules?
Kevin, is it a fair description to say that you are scraping the pages of your site in order to find and download the utag js files?
The reason I ask is that it would probably be easier to enable the distro.zip, grab that file, unpack it into your source control.
1. Click Save/Publish
2. Click Configure Publish Settings
3. Put (make sure there is) a check mark on "Generate distro.zip file"
4. Apply Changes
the file will be available at tags.tiqcdn.com/utag/[your_account_name]/[your_profile_name]/[target_environment]/distro.zip
Alternatively, you could
1. Go to the Versions tab in Tealium iQ
2. Expand the details of the published version you are interested in
3. Click on any of the versions of utag.js listed there
4. From the new pop-up, click on Download distro.zip file
1. Not sure what "global load rule" means in this context
2. Multiple load rules can be applied to a tag BUT that always uses an 'AND' operator so mutually exclusive load rules applied to the same tag would always evaluate to false and the tag won't load or the allowable scope for the tag will be severely limited because the 2 load rules will only evaluate to true under very specific conditions.
Caught sight of this question.
Clint, when I download the Distro.zip from the versions tab, I only see what looks like our template IDs of 20-24, plus utag.js, utag.sub.js and utag.footer.js
I don't think we're using utag.footer.js, but was wondering why the other dozen or so code-files per our template IDs aren't present?
Seeing if there's value or need to use this to grab the code libraries from Tealium to our source repository too.