Highlighted

How do I NOT persist SOME Webtrends parameters when consecutive utag.link calls with different parameters happen?

Rookie Contributor
I asked this related question and could solve it already: https://community.tealiumiq.com/questions/141703 But now I am facing the opposite challenge: I have a page where user click on filter causes an event where Webtrends parameter "eventPar1" gets set to value "clicked" (set via utag.link UDO variable) . Now on the same page, another event is triggered; also via utag.link, but with a different parameter (eventPar1 is not used, instead it is eventPar2). However, Webtrends now always sets eventPar1 = "clicked" with this second event as well. In a traditional WT implementation, I would do something like this: Webtrends.multiTrack({ argsa: ["DCS.dcsuri", "/home/help", "WT.i_custom", "12345"], finish: function (dcsObject, mtrackObject) { dcsObject.WT.i_custom = ""; } }); The part after "finish" resets the Variables used for Event Tracking. But setting the eventPar1 UDO variable to "" on the second Event Call does not help unfortunately. Can someone help here?
2 REPLIES 2
Highlighted

How do I NOT persist SOME Webtrends parameters when consecutive utag.link calls with different parameters happen?

Tealium Employee
Hey Lukas, We'll need to look into your implementation to address this exact case. Please contact your Tealium account manager with this issue. Thank you, Seth
Highlighted

How do I NOT persist SOME Webtrends parameters when consecutive utag.link calls with different parameters happen?

Rookie Contributor
I did contact my AM in the meantime and we are trying to solve this together. Anyhow, I think this must be an issue that comes up with ANY Webtrends implementation (because the WT standard is to always persist variables generated on the initial pageview). That's why I would be grateful for some experiences in this field. How did Tealium implementors solve this problem in the past?