Hi, I have a site with SiteCatalyst and Tealium: vfcz2.vodafone.projects.mediafactory.cz/onenet-express/ where is loaded utag script for Omniture too late, that page calls of s.t(); produce Referrence error. How to accelerate the Sitecatalyst tag load.

[jonathan_kay]

Hi - my client had an issue with a slow SiteCat tag last week. Upgrading to the latest uTag code and also moving the SiteCat tag to the top of the list (so it was called first) made a huge improvement.

[stan_racinsky]

Hi, I made SiteCat tag upgrade last week. The SiteCat tag is the top, but the related part of code loads too late.

[son_hoang]

Looking at your site there a couple things you can do. Since utag.js is loaded synchronously, you can also either: 1. Turn 'bundling' on in your configure publish, assuming SiteCatalyst is set to load on all pages 2. Or set SiteCatalyst to load synchronously in the tag's advanced settings. Either (or both together) should work. Note though we generally don't encourage users to call s.t() directly (it's preferred to do utag.view() which will call s.t() ), and an s.t() call should already be done on initial pageview.

[jared_hislop]

Hey Stan, Looking at your page, I'm a little confused. There is the utag.js file on line 35 and SiteCatalyst data at the bottom of the page. As Son points out, loading the utag.js file will automatically call the s.t() function for SiteCatalyst, but at the bottom of the page this function is getting called again. However, looking closer I think what is trying to be accomplished is Tealium is supposed to pick up the "s" object variables (pageName, channel, heir1, prop5, and prop20) and re-purpose them as Tealium variables (page_name, page_channel, etc) and they are getting mapped to the SiteCatalyst Tag in Tealium. So you don't necessarily need the Tealium SiteCatalyst code to run sooner, the page code that sets the s object variables needs to run before Tealium runs so that those values are defined before Tealium tries to read them. However, if Tealium code is moved towards the bottom of the page then there will be a duplicate page view server calls made because of the s.t() function at the bottom of the page. There will need to be some custom stuff done to define the s object in time so the page variable can be added to that object. Then either the s.t() function will need to be removed so there aren't duplicate page view calls. Since the site is tagged with the synchronous version of the utag.js, I'm not sure how the "s" object variables will get defined in time for Tealium to digest them without moving the utag.js lower on the page or the s object variables higher.. I would reach out to your Account Manager to have one of our Solutions Engineers reach out and get the specifics around what is trying to be accomplished and advise on an appropriate plan. Thanks

[stan_racinsky]

Hi Jared, I removed the s.t() call. But it still persists the problem, how to define the "s" object. Originally is this object defined in the s_code.js file. Grabbing of "s" object variables is defined in Extension of SiteCatalyst tag. But the remaining of "s" object for data in page source code is essential. But "s" object is defined in the SiteCatalyst tag itself. Adobe solves this by defining of "s" object in their Tag manager loader. And later is this variable overwritten by second instance of "var s=" at report suites definition in the loaded code. How to keep the "s" definition in the source code together with "s" definition in the SiteCatalyst Extensions? Kind regards

[jared_hislop]

Hey Stan, I played with your site a little bit and the methods Son pointed out above is the way to get this done. You will need to do two things. In the Advanced Configurations section of the SiteCatalyst tag you will need to set the Wait Flag to No and set Load Synchronously to Yes. You can view a post about Advanced Configs here: https://community.tealiumiq.com/posts/644178 This will load the SiteCatalyst library completely before allowing the page to move on. Anytime you're loading things synchronously it should be noted that there are risks involved.