Track multiple events on page load view (e.g. user_register and purchase)

Gold Contributor
Gold Contributor


is there any new solution to the problem "how to track multiple events at the same time"?

Ecommerce website, payment step. The user tick the "register as a new user" checkbox and confirm his purchase.  The user lands on the ThankYou page where we get the confirmation both user_register and purchase events.

As far as I know tealium_event property doesn't allow multiple values so, how can I trigger:

  1. Adobe only once with view and fill event1 and purchase at the same time;
  2. Another random tag like Conversant two times with link events?

We've solved the first point by adding a lot of custom javascript to our Adobe tag but we'd like to avoid such a "patch". We have no idea on how to solve the second point.



Track multiple events on page load view (e.g. user_register and purchase)

Tealium Employee

Most of our tags are designed to fire once per view/link. There are a few tags that can be fired multiple times per utag.view call, but those are the exception, and that information should be specified in the TLC documentation for those tags.  So in general, if you want a tag to fire twice, the easiest way is to make an additional or utag.view call, either coded onto your page or in a JavaScript extension.  

To avoid unnecessary double-firing, it is possible to fire a view/link call that only triggers a certain tag(s).  To do this, you simply include the UID for the desired tag(s) in the utag.view() call.  The documentation for this process can be found here:

Including the uid_array parameter will ensure that the specified tag(s) - and only those tags - are fired during that call. In your case, you could use the default utag.view to trigger the first round of events, and then use this method to specifically call the tags that need to fire an additional event.  That is probably the easiest solution for this type of scenario.  

(Please note that this will bypass any load rules on the tag, so you will need to be sure of your logic if you hardcode the UID's into the view/link call in this way.  Also note that you will need to ensure any required data is included as the first parameter in the view/link call, as the page data will not be passed by default.)