I'd like to build an extension that calls Webtrends dcsMultiTrack. Do you have some examples I can reference? My assumption is on Tracking Event, I'll select 'custom' and write the dcsMultiTrack.

[kris_irizawa]

example: dcsMultiTrack('parameter1', 'value1', 'parameter2', 'value2');

[ty_gavin · Accepted solution]

Hi Kris, Your example should work if you want to use the "custom" option and call Webtrends functions directly. If you call "utag.link" then the template will call multiTrack for you. Just make sure to map "parameter1" in Mapping. Anything that is mapped and has a value will get sent along in a multiTrack function call. // manual call to utag.link // requires parameter1 mapped to WT.something in mapping utag.link({"parameter1" : "value1"}); NOTE: If you choose "link" option (instead of "custom") in the jQuery onHandler Extension then the extension will call utag.link.

[kris_irizawa]

Interesting, thanks. I'm a bit confused on the jQuery onHandler Extension has the scope only allows 'Dome ready', and not allow to set scope to Webtrends. That means using "link" in this jQuery onHandler Extension, we have to make sure we selectively choose data sources that are unique to Webtrends? Another thing, regarding utag.link invokes multiTrack, is that documented some where? I think knowing such use case makes a huge difference in our set up practice. Or is utag.link smart enough to recognize WT parameter passed and make decisions to invoke tracking event unique Webtrends?

[ty_gavin]

All analytics tools support utag.link tracking. And the process is the same for each: 1) Set the data points (name/value pairs) in the tracking call 2) Map these in the Tag setup The reason the jQuery onHandler is scoped to DOM Ready is to make sure that the DOM has generated the item where jQuery will attach the listener. The Webtrends tag itself may fire before the DOM Element is in place. We also want to make sure this listener is only attached once. DOM Ready extensions will only run once. Webtrends Extensions will run with each utag.view or utag.link call. I agree we need more tag-specific documentation for these more complex analytics tools. The concepts are shared. It is just a matter of calling utag.link or utag.view and setting up mapping to pass the data along. We're attempting to "abstract" the specifics of the tag vendor. You would not need to know about the "s.tl()" function for SiteCatalyst or the "multiTrack" function for Webtrends. You only need to know about utag.link and you can use any analytics tool.

[son_hoang]

Just to expand a little on what Ty stated, some analytics do require specific data points to fire utag.link tracking. For example, Google Universal Analytics will not make any call with utag.link if you do not map some data points. If you wanted to do a hit type of 'event' you would have to map data to Event Category and Event Action as GUA requires these: https://developers.google.com/analytics/devguides/collection/analyticsjs/events#overview If you wanted utag.link to do a hit type of 'social interaction' you would have to map Social Network, Social Action and Social Target: https://developers.google.com/analytics/devguides/collection/analyticsjs/social-interactions For each hit type, if you only mapped 1 of these data points (i.e. Event Action is set to 'clicked' but Event Category is not set), utag.link will not fire for that intended instance. If you set all 5 of these data points, it would actually make two separate GUA calls, one for 'event' and one for 'social interaction.' Some analytic tags don't require any special data to fire, though. So utag.link will send to all analytics tags, but the only ones that fire are the ones that have their requirements met (some of which have no requirements and will thus always fire).

[kris_irizawa]

Thanks Ty and Song. These details are very helpful. I guess my concern originates from Son's late comment "utag.link will send to all analytics tags, but the only ones that fire are the ones that have their requirements met (some of which have no requirements and will thus always fire)." But it seems getting the parameter and making sure the data mapping address uniquely right for each analytics tool will do the job well enough.