I also came across this issue and Tealium adsives us that "The .cn domain you are leveraging for the main utag.js file is correct; however, you will also need to set up all individual utag.##.js (each individual tag has its own corresponding .js file) with the .cn path as well. Within TiQ, to update the path for the individual tags, we'll need to hardcode the Publishing URLs within the Publishing Settings to use //tags.tiqcdn.cn/utag/ACCOUNT/PROFILE/ENVIRONMENT/: If you're loading more than the China website in the TiQ profile, there is a way to override this based on a condition (i.e. domain contains .cn, etc.). If you wanted to use TiQ, you'd use a Pre Loader scoped JS extension with the code snippet below (adjusted to match the desired condition and path). //The following is a Preloader JS Extension to dynamically set the location of utag.X.js files based on a condition utag_cfg_ovrd = utag_cfg_ovrd || {}; if (location.hostname.indexOf("my.example.cn") > -1) { utag_cfg_ovrd.path = "//tags.tiqcdn.cn/utag/ACCOUNT/PROFILE/prod/"; } else { utag_cfg_ovrd.path = "//tags.tiqcdn.com/utag/ACCOUNT/PROFILE/prod/"; Because this is a preloader extension, we do not have access to which Tealium environment is loading in utag.data, but if you have Staging or Dev URLs, those can be used in an if statement to load the proper environment. Or your developers would load this directly on the page and skip using the JS Ext within TiQ. To learn more about utag_cfg_ovrd and how to implement it, please visit the link below: https://community.tealiumiq.com/t5/JavaScript-utag-js/Config-Overrides-for-utag-js/ta-p/14048 Thank you Chris Horme - Lead Engineer, Solutions Engineering
... View more