Tealium Learning Center

Hi Charis, I too use an extension for some doPlugIns code but it works fine. For clarity, how are you doing the mappings?  From your post, am I correct in assuming the code for your doPlugIns is in an extension and the mappings in the Tag? If so, move the mappings to the doPlugIns extension and it should work. Here's a screenshot in case it's helpful ... Regards, JK ... View more

My client deploys Target through a Sync template change. Everything else re the configuration is mananged through the Target UI. Seems to be working well. ... View more

I use thius plug-in. Make sure you only use the data as a guide. For proper page load measurement, use a dedicated tool such as Site Confidence or Gomex etc. ... View more

Are you sure that you only want to count a unique campaign value once per visit? If your prospects are likely to go back and forward to your site several times in the same session, perhaps because they are comparing your offering with your competitors, then you may wish to count each genuine campaign click because your top paid search term may be clicked multiple times. Therefore, it would be simplest to use Marking Channels and Marketing Channel Processing Rules in the Adobe Analytics interface. The Paid Search Detection Rule should take care of PPC and for others, such as display or email, make sure when you set up your rules that you tick the box, â ignore hits matching internal URL filtersâ . In Tealium you can create an extension to do similar should you wish to mimic the Adobe campaign and Marketing Channel Processing Rules, for example to make use of the Tealium Channel Extension to set up your channel stacking. ... View more

Hi Kevin, I'm also using the Channels extension, though found the extension needed a lot of bespoke work to get working as I want (trying to mimic the Adobe Analytics "channel stacking" report that Adobe Consulting configure). I'm almost there with some great help from Tealium's support team. I wanted to record the channel in a stack each time a visit starts (PPC, display, natural search, affiliate, social, redirects, email etc) and also record the channel each time someone goes to another site and then back to my site within the same visit. Eg, I may start a session using PPC and check out a competitor site a few mins later and then come back to my site again via PPC (perhaps using the same or a different adword click). To do this I needed: - An extension for a list of social site referring domains - Another for natural search (Adobe Analytics is great here as it maintains a list for you) - A campaign code syntax per managed channel (similar to Dan's comment above) - A cookie to determine if the page view is the 1st page view in a visit; which is then used to stop unwanted channel values from firing on each page view - Set the "channels" hierarchy rules in the Channel Extension. This is very messy / horrible process as you can't add rules in the position you want without deleting and starting again (I believe an update may be offered to allow drag-and-drop) I should have it properly working next week. Let me know if you need any more help. If it helps, the cookie extension code is: if (typeof utag.loader.RC('first_page_view') === 'object') { var browserName=navigator.appName; var expirydate= "expires=0"; if (browserName=="Microsoft Internet Explorer") { expirydate=''; } document.cookie = "first_page_view=false" + ";path=/;domain=" + utag.cfg.domain + ";"+ expirydate; b.first_page_view='true'; } ... View more

Hi - my client had an issue with a slow SiteCat tag last week. Upgrading to the latest uTag code and also moving the SiteCat tag to the top of the list (so it was called first) made a huge improvement. ... View more

Hi Dan - that would be great. More detail the better. Thank you ... View more

Great - thanks Craig. I'm on site next Tue - Thur so will pick up with you next week. JK ... View more

Hi Mark I tend to pass different variables each time the form is submitted so I can measure form attempts in micro detail - a different approach to yours which I would use 'as well as'. Basically: - each form submission generates a new server call with a unique pageName value; eg including "...attempt_1", 2 n etc - pass the number of errors in to a variable - pass the fields throwing errors in to a variable; eg "title", "email" etc - set up pathing etc on the above, pass to eVars, Props and Events as appriopriate etc So I can see that people tried a form on average 3 times, the average numbers of errors was 2 and the most common error fields were 'email' and 'dob' and combinations thereof. Be wary about field data tracking if the page isn't submitted and the user hasn't opted-in / out? Are you passing to any system all field data, personal data, data that you're are not allowed to process etc? ... View more

Sure - you can get my email for the UK team. Have a great weekend. ... View more

Oh ... In the exentions page, add line numbers to each entry so you don't get as lost when scrolling up an down a page and moving extensions around. Also, perhaps each entry needs an ID which remains static. And finally, add sortation and search funcationality to each column header in this report. ... View more

Hi Clint, Initially my challenge is familiarity and training - so user not interface related. I don't write JS so need support in these areas - hence Craig and Adrian being invaluable and again user not interface related. Initial interface confusion is when I need to jump around a data sources, tag, mapping, extension screen etc. May be aspects of the product could have a wizard or links to other components of the tool that I'm likely to have to have to configure next. Familiarity will help me here. â Savingâ a version is my biggest current concern: 1) If I'm working on a change I want an ability to ensure that my changes cannot be picked up and published by anyone else. Eg, to get my Channel Stacking and related reports to work as intended may take me several hours work over several days and what happens to my work if someone wants to make a separate 2 mins change? The Adobe Tag Manager interface very clear and easy to use in this regard with clear sections to keep versions in dev, staging or prod (perhaps because the product is quite basic). 2) I would expect that every change is auto saved rather than having to do a â save asâ . And (3) a rollback button would be useful too perhaps. The web companion wasnâ t clear re which mode Iâ m in, eg dev or prod, but I can see this has been updated this week - great. Related to this, Craig did a neat extension to auto populate the version no and a reference (eg â devâ or â prodâ ) which was mapped to an Adobe Analytics Prop meaning I always know the version and environment status of every server call when using a debugger or the reports. I suggest you make this a standard extension available to everyone. Finally (for now), the Channel extension could be easier to use; perhaps this is familiarity again. I mentioned my initial ideas to Adrian yesterday but in summary Iâ d like to create the following outputs to replicate / replace what Adobe Consulting would have to do using custom code for the s_code: 1) Stack my channels; eg â PPC > SEO > Emailâ etc 2) Stack keywords; either SEO only, PPC only or either (eg â ppc|keyword-1,seo|keyword2,|ppc,term3â etc 3) Stack time between Channels; eg â 0 > 1 > 5 >0â etc where â 0â indicates the same day 4) Stack channel and time in the same report 5) Have versions of the above that I could configure to reset each day (to see how many channels are used in a single day when there is a conversion), and also set a custom date range etc 6) Look at attribution weighting perhaps sometime in the future Right now Iâ m tackling (1) above with the extension. My client has many ways that people track a campaignâ s channel and campaign tracking code (the tracking syntax isnâ t consistent across brands and countries for the QSP or the tracking code itself), so setting the Extension rules will probably take me a lot of trial and error. Therefore, I would like to see an ability to drag channel rules higher and lower in the hierarchy rather than recreating them each time I need to make a change to anything but the bottom rule. Also, I would also like to see an ability to add another level to each condition; similar to how the Adobe Analytics works re Processing Rules etc. Eg, â query string >> contains >> abc >> and value >> contains >> xyzâ . I hope the above makes some sense. Loving the product and actively recommending it. ... View more