Highlighted

Sending a utag.link call from a custom tag container

Bronze Contributor
Bronze Contributor

Hi,

I've noticed the following output and wonder if there is some best practice I could follow when calling utag.link from within a custom container tag?


utag.loader.LOAD:70
SENDING: 70
utag.js:48 trigger:link
utag.js:48 Object {event_name: "xxx"}
utag.js:48 trigger:called before tags loaded
utag.js:48 Tag 30 did not LOAD
utag.js:48 Tag 35 did not LOAD
utag.js:48 Tag 52 did not LOAD
utag.loader.LOAD:30
utag.js:48 SENDING: 30
utag.js:48 send:30
...

Effectivelly all tags are loaded in the end, but I wonder if there are some concerns I should have around this?

Thanks,
Filipe

2 REPLIES 2
Highlighted

Sending a utag.link call from a custom tag container

Tealium Employee

I would be very cautious about firing a utag.link from within a tag, as you could easily get yourself into an infinite loop, (The utag.link calling the tag that fires the utag.link, etc. ) 

 

What is it that you're trying to achieve? You may be better off with a custom extension. 

Highlighted

Sending a utag.link call from a custom tag container

Bronze Contributor
Bronze Contributor
Hi Steve,

I do not intend to use it as a trigger, it's mostly so I get to have the custom event sent to redshift
I understand that ideally this would be hardcoded, but in the interim I would like the flexibility of having this call through Tealium.

Quick Example of what I'm trying to achieve:

Let's say after a succesful registration I would like to not only have a the normal page view, but also the custom event sent to redshift ( and GA for this matter )
Remaining registration tags will fire as normal, but since they won't fire for every registration I would have the above event as the baseline.
This would allow me to follow the paradigms of Pageview and Event instead of relying just on Pageview of confirmation pages.

I understand an extension would likely be a solution here, but if possible I would like to keep it within a custom tag container. Not really for any technical reason but mostly due to how I see tags being organized.

Interested to hear on what would be the reccomended approach though

Thank you
Filipe