I know that utag.js use ".toString()" method (i.e. with load rules), but I also know that IE does not support that method, so I guess that in many cases utag.js stops running due to IE-error. Does it make sense on you? Do you have any evidence of that? Or am I wrong? Thanks,
IE does support the toString method. However, your load rule may fail if it attempts to do a toString on an undefined variable e.g. if your load rule says "page_name contains ignore case 'test'", then if page_name is not defined, you'll get an uncaught error:
"Cannot call method toString of undefined" or something similar.
To avoid this, it's best to add a check to the load rule that the variable is defined before trying to perform a comparison on it:
"page_name IS DEFINED
AND page_name contains_ignore_case 'test'".
I hope this helps to explain what's going on.
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.
Great, I see now...
So it's a good practice to add a "DEFINED" or "NOTDEFINED" condition at the beginning of any load rules? otherwise we occur in the following problem: