Tealium Learning Center

@gauravdani   The regular expression you enter into the input box will be used as is within the test() method.   So you can enter something like: /tealium/i Then, if case insensitive "tealium" is found within the variable you've selected to test, then the condition will evaluate to true. Otherwrise, if case insensitive "tealium" is NOT found within the variable you've selected to test, then the condition will evaluate to false.   Remember, the purpose of load rules is to evaluate to true or false so that iQ can determine which tags to fire.   Please let me know if you have any more questions! ... View more

@redfuel318 Please open a case for custom code:  https://community.tealiumiq.com/t5/custom/page/page-id/support-contact-form ... View more

Hi Kevin, I've given this a shot, and I'm not seeing this new variable in in the data layer. I'm using DataSlayer to debug. ... View more

Hi Craig, We were looking to scope a "join data values", extension, but it seems that this might be best addressed upstream. Cheers, Kevin ... View more

Thanks, Dan! ... View more

Hi Sriram, Apologies for the delay and thanks for this data. Looking at this, it looks as if Chrome 37 is loading Tealium much faster than 36: - If a user moves page without Tealium loading and the SiteCat tag firing its request then the page view will not be counted. - If Chrome 37 loads Tealium faster then we'll be getting more page views - An increased bounce rate and an increase in visits suggests to me that more of your first-time users are being tracked (the first page view will probably be a bit slower as none of the Tealium scripts will have been cached yet) - If Tealium can be loaded quicker then you'll be able to capture more of these first-time users than before It would be interesting to see if this is related to the update for Windows specifically: http://www.anandtech.com/show/8431/google-updates-chrome-to-version-37-with-directwrite-support It suggests that the increase should be much bigger on Chrome 37 windows vs Mac due to the 'Direct Write' support. If your utag.js call is low down the page then you would noticed this increase even more than usual (utag.js should really be at the very top of the header). I'd suggest you get in touch with your Account Manager and discuss with someone in your local Tealium Solutions/Services team to investigate further but to me this points to a much better performance from Chrome on Windows but it would really need someone in your region to investigate to confirm. Hope this helps! Roshan ... View more

Let's assume on your page your setting: product_id = ["foo"]; I would set the E-com Ext to use product_id as the List of Product IDs option. This will by default tell the tags to use "foo" as the product id. Then, because this is an array variable, you'll probably need to write some custom code to append "xBar" to "foo" for the product id. Lets again assume that you are outputting this value into a new variable called "marketing_product_id." Then you would map "marketing_product_id" to the product variable in the Marketing Tags. This will overwrite the E-commerce Extension value with the mapped value. Mock code to append "xBar" b.marketing_product_id = []; for(var i=0;i This will append "xBar" to the product ids. ... View more

Hi John, Thanks for the question. Not sure what's going on there for you so I'd recommend reaching out to your account manager to see if we can figure it out. ... View more