Execution order for dynamic events triggered within Tealium

[ahrasch]

Hi,

I would like to know in which order events will be processed within Tealium, when they are dynamically triggered in an extension. I have the following questions:

1.) When a link event is triggered during the initial view event caused by the script load, will it only be processed after all tags have fired for the view event?

2.) Does extension scope play a role in this? Is the order the same for an after tags and a preloader extension?

3.) Does it matter if the dynamic event is a view or link?

Best regards,

Andreas

[dsavvy]

Hi

Have you had a look at this page https://community.tealiumiq.com/t5/iQ-Tag-Management/Order-of-Operations/ta-p/326#toc-hId-683779567

1. You have some control over that, and there is a beta out there where you can re-order what is fired in what order
2. Yes if you do pre loader scopes for instance, if you read the information on that page you can determine for yourseld which is the best coure of action for your scenario
3. Yes because some view is triggered on pageload and some tags actually depend on that and only work on that for pageviews, esepcially in anayltics. the link tags are useful if you wanted to fire specific stuff or create more complex analytics and eventstreaming data. It really depends on the situation, then you can decide what to use.
Generally in the extension i would you the link, and view i would use rarely possibly just for 1 page websites for instance where there isn't a page refresh.

Hope this helps, 

[ahrasch]

Hi,

thanks for your answer. But I think it relates more to the order of extensions. This is clear for me based on the documentation by Tealium you also provided.

My question is in regards to order of execution for the Tealium events (view/link) in the case they are dynamically triggered. As most of our pages are single page websites, almost all Tealium events are triggered dynamically (either external by the page code or internally via extensions).

If it helps, I have one specific example in mind, where order would be important. Google Analytics provides an event queue feature, which ensures the ga object can be called even before it is loaded. It essentially looks like this:

window["ga"] = window["ga"] || function(){(
  window["ga"].q=window["ga"].q || []).push(arguments)
}

If we would emulate something like this with Tealium, we would have to process this event queue and trigger them dynamically with utag.view()/utag.link() on the intial view event of Tealium after the script load. Thus it is important to know the exact order this events wil be executed.

[dsavvy]

I think i understand what you are getting, The only think i can say is that in extensions, the order you put the extensions on that view, it will execute in that order for instance.
Otherwise if you want something to fire in sequence you might have to put a lot of scripts in one place and order them in the order you want.
Do you have any examples of what you are trying to achieve?