Hi looks like we were using at.js 2.7.0 version and it doesnt support cross domain tracking. We had to upgrade to latest at.js version i.e 2.10.0 and had to add a custom code in the global target fire rule in launch like this window.targetGlobalSettings = { crossDomain:"enabled" }  after doing thi...

Actually it is a button inside a form which has an onclick event on it which has some function which which gathers all the fields from it and then takes some time to redirect to the other page

Hi All, I have setup a custom code in one of the activities to fire a custom mbox and I am trying to track that in the conversion settings as viewed an mbox and selecting the parameters passed in audience refinement and checking the value. But it does not increase any conversions for the clicks happ...

Implementation of target is on client side using latest at.js and also the cross domain tracking is enabled for both 1st party and 3rd party cookies. And my booking flow is on a different domain. I tried a simple counter profile script which was just increment the counter value and returning it as u...

Hi , What I am observeing is on the deeplink page the profile gets executed and I am able to check this in the before and after execution. Once I go to the booking flow pages the profile value is not there any more.   deepLink-page(domain A) -> Booking Flow1(Different Domain)(From here the profile i...