Bundling and DOMContentLoaded

[john_mooney]

Can I get some clarification on the impact of bundling and the sending of any bundled tags? It appears that the actual HTTP requests for a tag asset to the vendor still waits for DOMContentLoaded for bundled tags. Is this correct? The Order of Operation paper mentions in step 5 that bundled vendor tags are "loaded". But, do bundled tags still wait for step 7 and "the Send Function" If I understand correctly, bundled allows for execution of tag prep/logic sooner? If bundling is turned on, are all tags qualified by load rules, bundled? thanks (from Order of Operation white paper . . .) The utag.js operations ï¬ ow in a very speciï¬ c order and understanding that order can prevent errors in your implementation. 1. Run Extensions scoped to â Pre-Loaderâ and set Privacy Manager cookie 2. Process Data Layer 3. Evaluate Load Rules 4. Run Extensions scoped to â All Tagsâ and the Privacy Manager Extension 5. Load Bundled Vendor Tags and Vendor Tags with their Wait Flag set to â Offâ 6. Load Vendor Tags, their Extensions, and Mappings 7. DOM Ready and the Send Function 8. After Page Load: utag.view() and Advanced Conï¬ gurations

[jared_hislop · Accepted solution]

John, Bundling on applies to tags that are set to load on All Pages. Tags that are bundled will load earlier in the order of operations and cut down on the number of http/s requests that are sent out from the page, which should give a performance boost. By default bundles tags still wait for DOM Ready due to the Wait Flag Setting in the Tag Advanced Settings. The Wait Flag determines when the tag will actually get fired. See this post: https://community.tealiumiq.com/t5/Tealium-iQ/Tag-Configuration-Advanced-Settings/ta-p/13600

[john_mooney]

Jared Thanks for clarifying and confirming my understanding.