Target Standard and Adobe Analytic integration - best practice in Tealium. Where to place VisitorApi.js?

[alla_omelchenko]

One option is to place VisitorAPI.js into mbox.js in the very beginning of the code. What is the best practice to do it in Tealium?

[jonathan_kay]

My client deploys Target through a Sync template change. Everything else re the configuration is mananged through the Target UI. Seems to be working well.

[alla_omelchenko]

We also deploy Sync template. I wonder how your client deployed Marketing Cloud Visitor API if they have integration with Adobe Analytics.

[Seth]

Hey Alla, The Visitor API file is included in both Tag templates. The templates are designed to check for the VisitorApi.js file in cache before calling it. So, if the Target Tag calls the Visitor API, then the Analytics Tag should use the same file instead of calling it again. What both you and Jonathan have described is a common implementation. Was there something specific you wanted to do? Thanks, Seth

[alla_omelchenko]

Yes. I need VisitorAPI fire before mbox.js which is currently deployed via utag.sync.js. If I use built-in VisitorAPI I don't get data into Target Standard as AppMeasurement fires in my case after mbox.js.

[alla_omelchenko]

I received a reply from Adobe that currently VisitorAPI fires after Target Standard and therefore our integration doesn't work. Is there any way to fire it before Target Standard call?