Tealium Learning Center

lars_rothberg_h · ‎11-04-2014

Thanks for the feedback Clint, So what's the process around getting a template updated? I am guessing that the job of adding a template is some how anchored within the organization that the tag is created for. Will Tealium be reaching out to them if we put in a request? Also while on the topic of managing templates, now that it's become clear to me that these are indeed managed by Tealium. It seems like there is huge variation on how very similar tags are executed. We almost always need to use the "Manage Templates" and check the implementation in order to figure out how mapped variables are taken as input and what hoops we need to jump through in order to potentially override any of them by the use of extensions.

lars_rothberg_h · ‎11-03-2014

For well over a year, my office have supported a site with Tealium on a client site. The different departments within the client organization are now aware of this installation we get quite a lot requests. Since this is a global site we get requests for working with different affiliate networks display partners around the work. Here after simply referred to as "partners" Often we notice that of course many of the partners do have a Tag available in Tealium and we always encourage using it when it's available, but then it begins to get really interesting. 1. We will often get a tracking pixel, jscript embedded, but the behavior implemented in the template deviates. Either the Tealium template is deprecated, or the tag that the partner want to have implemented is. That leads to the question, who creates these templates? who specifies them? Often I would very much like to have the dialog with whoever ordered the template and fix it, instead of continuously deploy workarounds by fixing it through extensions or directly modify the partners templates. 2. Does someone have a crash course "What is Tealium?" that one can send out to partners. After the initial delivery, we often gets challenged by someone from the partner that they cannot see their tracking pixel in "view source" and would like to know when we intend to add it. After that point, long email chains or conference calls starts. Having a crash course for a person who is used to use "view source" and get the basic understanding of Tealium or TMS for that matter would greatly help.

lars_rothberg_h · ‎10-08-2014

Thanks, I just upgraded to 4.33 just to test it out. Massive upgrade compared to previous view behavior and I can easily use it for the simple cases, however there is one problem still. Lets say I have an original UDO object utag_data1 = {'pagename':'page1','type':'frontpage'} Before the view, I prepare a new UDO utag.view({'pagename':'contact'}; The second tag I expect to be executed has one rule in it saying something like "type is not defined" This second rule will never be executed, since the type value has been set in the original UDO object for the page. Any ideas are greatly appreciated

lars_rothberg_h · ‎10-07-2014

I've been reading up on using utag.view(variables) whenever the UDO changes as part of an event, not sure if it's the right solution. I am looking into a scenario where we're when clicking on a navigation, the page changes dramatically, since we're essentially pulling in an entire new page, but keeps the outer template in place. We do some tricks so our customers gets the smooth transition you get when only replacing partial content, however from a Telium POV, this really is a completely new page and all rules should be evaluated again. 1. The URL is updated to a new vanity url the customer can share (I except any tags matching this rule should be executed) 2. UDO data from the new page is loaded. I'm assuming what I need is the ability to force Tealium to accept my new UDO data as well as force a re-evaluation of all rules based on the new URL Any ideas?

lars_rothberg_h · ‎09-20-2013

Thanks for the hint Craig, I did test it out, but there was still a gap in what it provided and what I wanted to achieve. A scenario is, that we have some tags, we only allow these to be fired when the policy is accepted. This tag will be fired on a specific URL when the user enters the platform the first time. The user is presented with the Cookie Policy, for all users that accepts it the tag is immediately fired, since it has been queued via our JavaScript component. It seems like the Privacy Manager simply drops a cookie and when the user visit another page or reloads the page, this cookie is consulted. In the above scenario, that would result in my tag never getting again, unless the user manually reloads the page. /Lars

lars_rothberg_h · ‎09-19-2013

We have in place an EU Cookie Control policy in place, so visitors get an optional dialog to accept cookies, which allows the customer to actively select if he accepts cookies or not. We have tags that is allowed to be executed not taking into account the selection, and we have tags that's only allowed to be executed once a customer accepts the policy. We have set up a datasource indicating if cookies are accepted, this is being added to the datalayer before the utag.js is being loaded, so it's not a problem to manage as soon as the selection has been made on a previous page, however the problem is only on the first visit. While testing we simply loaded utag.js and when a customer accepted cookies, we would send a utag.view(), however any tags that supports and has executed once will execute again based on this. Ideally I would like to solve it by being able to send some kind of event through, which would trigger these tags to be executed, since that is what we're capable off from within our cookie policy component. I can probably fix it by modifying the templates, however I also want to make it simple for the users of the interface to easy add new tag rules. Thanks in advance /Lars

Date Registered	‎09-22-2015 07:24 PM
Date Last Visited	‎08-17-2016 08:27 AM
Total Messages Posted	6

Tealium Learning Center

Thanks for the feedback Clint, So what's the proce...

Explaining Tealium and contacting template develop...

Thanks, I just upgraded to 4.33 just to test it ou...

Dynamically reloading utag.js

Thanks for the hint Craig, I did test it out, but ...

How to make sure a tag is only fired once?

Products

Company