Currently managing the current digital infratructure, and have current requirement addressing utag being evoked multiple times and filing all assicated tags a second time after orginal page load. The current understanding is that the web property has pages that collect user selection and input data, and pass it via a _trackLink call once we advance to the next page. During a meeting, a comment was raised that developers were using inconsistant and wrong function call considerations; using _trackLink, _EventTracker, or _PageView in different ways. It appears we are sending 'event' data that is collected during the page, and pushing it to Tealium for processing, in which utag is completeing processing itself again causing inaccurate hits, pageviews, and metrck information for the duplicate, or unwanted duplicated tag firing. We spoke about using session/cookie storage to indicate utag has already fired, and then upon _TrackLink, to simply send the data and use an extension/load rule (but extention may be more correct) to prevent the assocated tags with the session/cookie 'flag' to bypass or prevent subseqent firing. If you have comments on the different methods of sending pageData via the different calls I had mentioned, comment below on their proper use and resouces for examination. I want to know if utag requires to be evoked when sending EventData, and such, manage or prevent duplicate tag firing when advacing to the next page during user expeirence.
... View more
Expand/CollapseMenu
