Tealium Learning Center

Hi @schampernowne,   An alternative would be to use the set data extension to set the evar to "D=mid" (without the quotes). When Adobe is processing the data it will replace the D=mid to the correct value. A second alternative is to use processing rules in Adobe to set the evar to the maketing cloud id. Both of these would have the advantage that you are not subject to race conditions or other javascript issues. The downside is that you are less flexible in defining fallbacks if the visitor would not have an mid... ... View more

Hi @PansensoyI. The first thing to check is to make sure the visitor api code is inserted before appmeasurment. If this is done than also check if you are getting the correct instance of the visitor api. eg. var visitor = Visitor.getInstance("016D5C175213CCA80A490D13@AdobeOrg") This makes sure that you are using the correct instance of the visitor object created by the script. If you type 's_c_il' in the developer console (without the quotes) you'll get an array of all the 'parts' that are instanciated. Hopefully this helps you in finding the solution for your problem ... View more

A quick hat tip to 'gain' up to 300 milliseconds is to do the click tracking on mousedown instead of on click. The time between the mousedown event and the actual click event can be enough to give the tags the time to get send.   This won't solve all issues but all little bits help right! ... View more

The only screenshot I can send is about the message I got when trying to run it but nothing re ally special to see about that though...   screenshot ... View more

The problem is not running it once as this can be easily done but the condition is more strict in that I need to know when utag is available but the soltion should not be scoped as an all tags extension. I guess i'll have to digg a bit deeper or rework the solution to not need the utag dependencie. Thanks anyways ... View more

@do_pham, I do not see any reference of preferring the use of context data over normal variables in any Adobe documentation/communication I have but the choice of either one depends on the strategy we as a customer are choosing. As we use Tealium we have chosen to have the image request contain the variables we need as it is easy for us to change in Tealium ( that is why tealium is therefore) context data/processing rules need a certain level of expertise from the team to get it right whilst Tealium is more accessible to the majority of the team. But that's a whole other discussion I suppose. I do see that long request do get properly POSTed but the available tools cannot decipher them which makes day to day work a lot more cumbersome therefore the need for the compression. I will look into adding it into the doPlugins so that I do not need to fiddle with the template no more. ... View more

@evelin, personlized events as you specified are things that your developer use to define the custom behavior on your site. the downloadpdf function might trigger a dialog which enables you to download the pdf. Within this function you can ask to add the utag.link code so that each time the downloadpdf funtion is called you will also trigger a request with tealium. The same principle applies to Ajax calls wherebye the utag.link call should be added into the success event handler of the ajax call. Using directly onclick (which you should never do!use addEventListeners!) is possible but not really for ajax calls. Check with the developer for a good solution. ... View more

@mitchellt, for Adobe specific you should check if you have the clearvars option set to yes (edit sitecatlyst tag and look for dropdown for clearvars) If set to yes, the first call will set the variables and after the request is done, all the variables are cleared. In subsequent requests you will have to send ALL the variables in the utag.view/link call in order to have them send again. Disable the clearvars option and check if this resolves your issue. Happy testing! ... View more

@EstherVG, if you have access to the html/js that defines the var utag_data you can add it there. This is perhaps only possible by IT or your pages developer. The advantage is that this is the easiest way to add a variable as the developer has to only say utag_data.new_variable='value'; and you are done with it. The downside is that you have to ask IT to do it and this might take some time, especially if you need to do this excercise for multiple pages. You could also use a set data extension in tealium which allows you to add a value to a variable based on a condition. The upside is that you can change this yourselve, downside being that if you have a lot of pages you will have an unmaintanable list of extensions in the long run. My advice, invest time in planning your 'standard' data layer, for specific pages,define the extra variables and plan with your IT POC to have them implement it ... View more

hi @guy_cowan, the scCheckout is an 'order' level event and should not go in the product string as per Adobe's definition. If you have a variable in the data layer that defines the shopping action eg. utag_data.shopping_action = 'checkout' then you could map this via tealium to the event scCheckout by simply using the Tealium UI. Check in the mapping dialog the events part and input the value of the shopping_action variable (eg. checkout) in the input field and select scCheckout from the dropdown. This should be working perfectly. Basically you are now telling Tealium that when the shopping_action variables value equals to checkout then the scChecout has to be set. Hope this is clear enough ... View more

I did the test myself by copying the code mentioned in my question in the tag template and the dynamic variable part is working again.   I pasted the code at about the same placeit was in version 1.5.2.   Hopefully this will make it into the next release of the tag template for SiteCatalyst ... View more

Thanks for the reply but I perhaps was not clear enough in explaining my question. We want to be 100% sure what we send to Google Analaytics. Therefore I would like to know how the request is being send to Google in case of a server to server setup. As the request is made from a tealium server I guess that the request headers will contain the details from that server (eg. the ip/useragent/referrer fields are different). I just want to verify if this reasoning is correct. If there would be a more detailed document or explanation available for the nitty gritty details regarding server to server I would be very happy to receive! thanks ... View more

when digging into the code I've seen the following in utag.js(line 707+708): else if(utag.cfg.load_rules_ajax){ // right now, load rules use utag.data (replace items in utag.data with items in b) if I set utag.cfg.load_rules_ajax to false the utag.data is kept intact but I am not sure what the side effects of this setting will have so I am not sure if this is a solution ... View more

I do not get the same result, see my test results below: Setup ------------------- -new profile -html page with code directly from 'code center' -1 tag added, Tealium custom container,loaded on all pages, where send function does only log the values of the a and b parameters and the mapped data object: //tealium universal tag - utag.loader ut4.37.##UTVERSION## u.send = function(a, b) { console.log('Start send'); console.log('Var a:',a); console.log('Var b:',b); ... mapping code from Tealium... console.log('U data:',u.data); -mapped three UDO variables: event --> ev, event_location-->event_location, event_detail-->event_detail; Use case 1: Page load ------------------------------- > utag.data = contains standard utag variables generated by tealium in tag: console.log(a) = 'view' in tag: console.log(b) = same as utag.data OK = Expected result Test 1: manual utag.link with mapped event parameter (event is mapped to ev) ---------------------------------- > utag.link({event:'foo'}); in tag: console.log(a) = 'link' in tag:console.log(b) = same as utag.data + variable event:'foobar' in tag: eventual mapped data = ev:'foobar' Mapping is ok BUT > utag.data = standard utag.data + variable event:'foobar' so basically the same as variable b NOK == not expected this result Expected result is that utag.data does not contain the event variable. Using any other parameter exhibits the same behavior: utag.view({notmappedparam:'should not be there'}), the variable notmappedparam is afterwards also in utag.data AND utag_data plus the event parameter is now set to view. ... View more

Hi Fiann, That was indeed the link I was looking for. Thanks for that. Indeed a good idea to dive into third party monitoring. I'm sure we have someone in house who can check that out for me. Thanks for the reply. Best regards ... View more