Tealium Learning Center

James, We received your ticket and will respond once we've had a chance to look through your implementation. This is a pretty custom implementation so it will take a little digging through. Stay Tuned! Thanks ... View more

Hey Larry, You could use something like this the attached below. I can't get Bloomfire to upload the code. This will loop through each value in the t_product_name array and clear out any character that is contained in the square brackets. This will then set the variable back to the b object so it can be used by the Ecommerce and other extensions as needed. The Scoped vars and Output lines are deprecated pieces of functionality that are no longer needed, it just has not been removed. We used to have to declare variables that were used in the JS extension so that the syntax of the code could be validated. Using b.variable would have thrown an error so "b" would have needed to be declared. This field can be left blank. ... View more

Hey James, Your assumptions are correct given that the mappings are in place for these js_page variables. The events update that was suggested above should not have affected any of your other variables or mappings so it seems like something else has changed. This is getting really specific to your use case. It would best be handled by reaching out to your Account Manager and one of our Solutions Engineers can take a look at your profile and provide greater insight. ... View more

James, Can you just change the condition of the extension triggering the event to be more granular? Only fire when page EQUALS "somevalue" You can also all an "AND" statement AND page DOES NOT EQUAL "thisvalue" Or you can use the first option and use mappings. In the value box of the events tab put "LFG:Visualizer:Variable Annuity:visualizer main" then in the event will only get triggered when screenName.fname equals that value and it won't fire any other time. ... View more

Hey Sean, The is populated condition will check if the variable is defined then it will check and make sure that it contains a value and does not equal an empty string. The is defined condition will only check if if the variable is defined and not worry about what the value is. variable_1 = "" -> is defined returns true, is populated returns false variable_2 = "foo" -> is defined returns true, is populated returns true ... View more

Essentially yes. :) ... View more

Chaitanya, There is a chance something was missed when copying and pasting. The best thing to do in this situation is to reach out to your Account Manager with the account / profile you are implementing this for. Also, include a URL where this can be tested. Our support staff will be able to quickly look into this and formulate a helpful response. ... View more

Hey Chaitanya, In order for mappings to work you'll need to place the variables you create in the JS Extension into the "b" namespace / object. So instead of declaring your variables like: var foo = "bar" You would do: b.foo = "bar" Then you can go into the Data Sources tab. Create a new Data Source called "foo" and leave it as the default "Data Object" type. Now you can use "foo" in the mapping section of the SiteCatalyst Tag and assign it an eVar or prop as needed. It can also be used in any other tag if needed. Hope this helps. ... View more

Tomas, I may have misunderstood your original question. linkTrackVars and linkTrackEvents are set to "None" on page load because on page load they are not needed. linkTrackVars and linkTrackEvents are only used for link tracking. When utag.link or s.tl() is called, Tealium will only set linkTrackVars and linkTrackEvents to "None" if there aren't any values. The clearing of the variables happens *after* each server call that is made so every time SiteCatalyst gets called the server call is starting with a clean slate. So to answer your question, Tealium already does what you suggest, but with the addition of clearing the variables after each server call to ensure data isn't being sent when it shouldn't. If linkTrackVars and linkTrackEvents were set to "None" before the server call was made then no variables would get sent to SiteCatalyst. In your specific case, eVar11 is populated with a cookie value. Tealium does not clear cookie values after each server call, only SiteCat variables. Because that cookie has a value that is persisted, it contains a value each time SiteCat is called. Because it contains a value, our mappings will pick it up and populate eVar11 with the value of the cookie. Then because eVar11 has a value Tealium will auto populate linkTrackVars with eVar11. Hope this helps clear things up. Cheers! ... View more

Ahhh, it's becoming clear now. I love dev sites :) eVar11 is being set from a cookie value, which is being persisted in this case. The functionality to clear eVars and props does not clear the cookie values. So if you want to not pass this value then you'll need to do an extension that will clear the cookie when the link_name equals a value or from some other condition. Here is an example: ... View more

The functionality to clear the variables does not clear the page name. This is by design. Also, whenever you call s.tl() (which is the utag.link function) even though the page name shows up in the server call SiteCatalyst will *not* capture this value and count it as a page view. SC recognizes the "click" server call and disregards the pageName value. In your profile, I only see eVar2 mapped. I am assuming this is the one that is firing. For eVar1 you'll need to either map url to eVar1, which would send the url into eVar1 on each server call. Or you'll need to add a variable called link_url and add it to the jQuery click handler extension like: Set: link_url To: Variable - then select url from the drop down. Then map link_url to eVar1 in the mapping toolbox. This will fire eVar1 and eVar2 along with event5 as you outlined in the original question. Are there more variables that should fire? ... View more

It is set to None after the server call is made so that the next server call starts with a clean slate. Tealium will automatically set linkTrackVars and linkTrackEvents based off of the mappings and what is defined in the extensions. Are you saying that when you click on this button all the variables from the previous server call are also firing? What acccount / profile is this for? I'd like to check the SiteCatalyst template to see if it has the latest update that clears the variables after the server call. Thanks ... View more