In our product implementation, we don't want to keep loading the utag.js file every time for usage capturing (Abode SiteCatalyst), though we are using Async way of loading the utag.js file, since it is not going to change, we don't want to load the file in every page, we are looking at triggering a method.
We are currently have it on our roadmap to allow new tags to be loaded based on values passed to a utag.view function call. Please get in touch with your Account Manager to make sure you are notified when this feature is released.
I get the impression you're asking if you can load just the Adobe SiteCatalyst tag as a standalone file, without loading the main utag.js code at all. If that's what you mean, then no, it's not possible.
All the utag.x.js files interact with the main utag.js to form the complete solution, and it is the main utag.js that triggers both the send functions inside each of the tags, as well as the page view request. If you were to load just utag.1.js for example (assuming this is your SiteCatalyst tag), nothing would happen.
Might I ask what the reason is that you don't want to load utag.js on every page? Are you concerned about performance?
There is a feature that may be appealing to you called "bundling". This forces all tags that have an "All Pages" load rule to be included in the utag.js file, rather than being published into separate utag.x.js files, thus reducing the amount of individual requests made by the browser and slightly increasing overall performance. This option is available in the "Configure Publish Settings" option inside the save/publish dialogue box.
Hope this helps. Please do let us know what the exact problem is you are trying to solve, and perhaps we can come up with some other suggestions for you.
Check out our new Swift integration library for iOS, macOS, tvOS and watchOS: https://github.com/Tealium/tealium-swift with updated documentation https://community.tealiumiq.com/t5/Swift/tkb-p/swift.
Yes! This is what I want too! We have a modal signup confirmation which could show on any page, but we would rather not have all the tags have to load on every page in all circumstances. Instead we would rather fire a "Signup confirmation" pageview on demand.
To expand on Craig's great answer, also note that after the visitor's initial page visit, utag.js should be cached so utag.js' impact subsequent page visits should have minimal impact.
I believe we have a call scheduled with you tomorrow regarding other issues, so if you'd like to go over this in more detail at that point please let us know.