Highlighted

IBM Coremetrics: Can I use Tealium to load in eluminate.js only?

Rookie Contributor
We're currently looking to migrate our Coremetrics tagging implementation from being hard-coded on the site to using Tealium's TMS - however, due to the extensive tagging on our website I have suggested that we migrate the tagging in stages to minimise errors. I would like to confirm whether it is possible to use Tealium to fire the coremetrics eluminate.js tag that is currently held in the website header, but leave the current tagging in place on the site? This will allow us to migrate the tags over one by one, as opposed to completing a mass migration. Any help that can be given will be greatly appreciated. Thanks, Reuben
5 REPLIES 5
Highlighted

IBM Coremetrics: Can I use Tealium to load in eluminate.js only?

Tealium Employee
Hi Reuben, There shouldn't be any issues with this approach. Tealium loads the same eluminate.js file that would normally be loaded natively for the Coremetrics tag. Any natively implemented Coremetrics tags/function calls should continue to work as before. I'd advise testing any changes on the development site before pushing anything live, but there shouldn't be any problems with a staged approach to the migration. Thanks, Ian
Highlighted

IBM Coremetrics: Can I use Tealium to load in eluminate.js only?

Rookie Contributor
Hi Ian, thanks very much for clarifying. One follow up question if you can help; if we implement the IBM Coremetrics tagging via Tealium, will the order/shop data be automatically populated via the E-Commerce extension we currently have activated (whilst the migration is going on we would prefer that it did not as it could potentially duplicate our order tags). If it will, is there a way of disabling the E-Commerce extension from being picked up by the IBM tag? Thanks, Reuben
Highlighted

IBM Coremetrics: Can I use Tealium to load in eluminate.js only?

Tealium Employee
The biggest problem with this approach is that you need to guarantee that Tealium has loaded eluminate.js before your native code runs on the page. If your native code runs and tries to call functions which are only defined inside eluminate.js, then the functions will be undefined, and the calls will fail. If you have implemented utag.sync.js in the head of the page, it might be best to (temporarily) load eluminate.js here instead, as this will guarantee that the CoreMetrics functions are ready when the page loads.
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.
Highlighted

IBM Coremetrics: Can I use Tealium to load in eluminate.js only?

Rookie Contributor
Craig, I'm very interested in your response and wonder, why are you suggesting loading eluminate.js in the utag.sync.js in the page head as a temporary solution? I am very concerned about loading eluminate in the footer and missing tags firing. Can you explain a bit more please? Thanks! Adam
Highlighted

IBM Coremetrics: Can I use Tealium to load in eluminate.js only?

Tealium Employee
Adam, This was a response to a very specific use case, and is completely unnecessary in any other situation. Tealium's standard async CoreMetrics tag works just fine, and there's no need to put anything in utag.sync.js. You won't be losing any tracking as long as you follow our best practice and load utag.js at the top of the , or as close to the top as you can get it. I hope this clarifies things. Craig.
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.