Tealium Learning Center

Hi @mitchellt. Thank you for your reply. I will implement Tealium without using document.write as your advice. ... View more

Hello @pgarri02pruebasPlease refer to this link. Thanks, Madhan  ... View more

Hi @pgarridopruebas - in Dev or Prod, I don't see any Tags firing at the link you provided.  Also Adobe Debugger shows nothing firing.  Ensure you have your tags enabled, and/or let us know which environment to invoke. ... View more

Hi @RohiniM - of course, the Tealium ecommerce extension takes care of all such minutia.  However it takes some advance planning to get it into your profile if you've never used it before.  Try to make some time to do so in the future because you'll find that it takes care of so much on almost every tag you'll ever use.   That said, you'll want to use an extension to append the leading semicolon to your product string.  You should be able to use a Set Data Values extension to do something like set   productStringName    to    JS Code   ";"+productStringName  or you could do similar with a long form JavaScript code extension.  ... View more

Hi @mitchellt many thanks for your help! It seems I possibly just wasn't being patient enough, as over 2 weeks after implementing the schema, Google seems to have rendered the JS tags in which the changes were contained and is now picking them up in Search Console just fine. Would love to experiement with the Pre-Loader / DOM Ready scopes at some point (or even simply using the Fetch as Google function) to see if it expedites the process at all - but for the minute I'm just pleased it's working! ... View more

Thanks @mitchellt. Good suggestion. Deleting it would be clean but at least labelling it will remind us not to pick it up for future versions. ... View more

@Donaldo you can use a Tealium Pixel Contains, setup instructions are available here: https://community.tealiumiq.com/t5/Tags/Tealium-Pixel-Container-Tag/ta-p/13388     ... View more

Hi @pmeyerdk - I agree running in an iframe is not optimal, but shouldn't be a total show stopper.  Several pages of the distributed application I work with are iframed, with Tealium running in the content iframe and sometimes in both frames. All this makes debugging a challenge, but we still get things done.  I was just reviewing our data to see if I could find a great disparity in data collection across browser types as you were suggesting, but I could not find a huge difference.   In most of our use cases, there's not a real technical reason to be iframed other than compartmentalization of developer code. As such, I'm pushing to get out of iframes going forward.   I think it'll just be a learning experience as you go - please share any interesting findings, and thanks for putting this on the radar, I'll share back any new findings as well.  Hope others here will chime in as well. ... View more

Hello @Jayakrishnaa, If its not many files, then you can use the lookup table and trigger link_name. Example: as per your code match the s_url in the lookup value and update the link_name with the output value (which is the friendly name) s.tl (true, 'e', b.link_name, null, null) ; Hope this Helps Thanks! ... View more

Ah very cool @Jayakrishnaa! Love this solution! Thank you for sharing. ... View more

Thanks @mitchellt - i had not even considered this was a option in Processing Rules. But i see it, and have tried to add it. Sometime the obvious solution is to easy to be considered.   In general i like to have the User Agent available in a analytics dataset for debugging.  ... View more

Hello @Jayakrishnaa, You gt it right, you need to create a JS variable and map it to SiteCatalyst s_account. Mapping Conflict - I believe currently you are using the Report Suite configuration option in the tag(left arrow in the below image). When you do a lookup extension make sure to give the defaut value as a production report suite You had mentioned that you will be using the URL in the lookup extension, please make sure that respective environment url's are matched exactly. Please deploy them stage by stage, I mean publish them to Dev environment first and test it, then to QA and then finaly to Prod. In this way we can test for traffic and make sure we are not messing up. After deplying to QA and testing it, before pushing it prodution try environment switching and test it in prod. Let me be more clear here -  Open production URL use the Tealium web companion or Tealium environment switcher to change the prod profile to QA profile and see weather the Sitecatalyst call is redirecting to SiteCatalyst production report suite. top arrow shows the current environment bottom arrow shows what needs to be selected, select QA and when refresh button appears click refresh. This will help you to make sure that your extension will work as expected in production as well. Hope this helps and please let me know if you need any help. Thanks! ... View more

Yes, I was not on the latest version of the Tag. Thank You all for the help.  ... View more

Great feedback @loldenburg! Thanks for sharing. ... View more

Thank you @mitchellt I did the same but it's not getting tracked in GA. Could you please where I need to make these changes "Don't forget that you need to configure your custom event(s) in Google Analytics Admin area before sending in the data you're collecting.". It would be great if you can provide me a step to step guide. Thanks! ... View more

@mvenkatesan done on http://tealiumfiserv.com/ ! ... View more

You've got a couple options,  @JoeBrown .... 1) fix the problem at the root - get your developers to remove the comma and use another character instead of comma (maybe dash?) 2) handle it with a Tealium "extension".  Remove/replace the comma within another Tealium extension using some hand-coded Javascript.   Let us know how it turns out, if you need more ideas, etc.  You always can ask your Account Manager to get you Tealium help too....   ... View more

Thanks for this write up @UnknownJ.  How can we mark it as a [possible] Solution to help other readers/users? ... View more

Hi @CesarFlorero - if I'm not mistaken, the gclid value is different for each visitor/click, so you probably want to map that to another Adobe variable.  I would recommend careful setup of your paid campaign values and to coordinate that with the Adobe settings in Report Suite administration. The standard s.campaign variable for Adobe Campaign tracking should be different from whatever tracking code you configure for paid search tracking or else suddenly all your marketing campaigns are considered to be "paid search" in your Adobe Reporting.  I would suggest using the "gclid" parameter as one of your "paid search detection" rules, then figure out a similar value and rule for Bing if you're using them too. Check out Adobe's Marketing Channels documentation as well.   ... View more

Thank you for that answer @mitchellt! You rock! @pavoldzavan I have let your account manager @dburgess know about this post. He should be in contact with your shortly.  ... View more

Just to close the loop on this, we ended up going with a custom JS extension and mapping it to the "SiteCatalyst AppMeasurement for JavaScript" tag, but we also manually set the s.prop and updated s.linkTrackVars within the extension. I guess the tag based variable mapping happens before extensions scoped to the "SiteCatalyst AppMeasurement for JavaScript" tag execute, so the mapping was happening before the variable was valued. I hate having to manually set an s.prop within an extension, but it works. Thanks for your help. ... View more

Hi @PansensoyI  -  are you using your browser's Inspect feature?   You won't see this in View Source, only in the browser Inspect Element feature (Chrome is easiest to use IMO). I can see "utag_443" calling your gtag.js tag.  Also can see some iframes, just can't tell which one is associated with your gtag.    See also the Inspector >  Network tag to detect any associated pixels for this gtag.   Good luck - let us know how it goes. ... View more

This is an interesting question, @AlanDuvall, I've not seen or considered before. Likely we'll need more info to solve, but below are a couple ideas. My first thought is to tread carefully because of potentional PII issues - indeed just a thought. Next, can you tell that a cookie has been created while the video ad was viewed? Can you see it in the browser inspector ? (check network and application tabs)  It is highly likely that the cookie domain will be different than the domain where your site (and your TiQ implementation) resides so it will be difficult (impossible?) to capture because of cross-domain browser security measures. Otherwise, perhaps it's possible to get this type of Audience information from a FB reporting interface associated with your video ad or access it via a FB API. Hope these thoughts give you some ideas to accomplish your goal....       ... View more

It's hidden due security issue @mitchellt. So i found that angular controller is loaded after script, so i can't add data after that, trying with utag.link(), Got in my UDO debugger some values . I am on right track, doing async calls on single page  ... View more