Hi, Adobe Analytics noobie here. We are noticing that on some browsers the VisitorAPI.js, is occasionally being blocked (which is hard coded onto each page). It seems to be related to cookie settings in that browsers with strict cookie settings prevent it from firing, most often during checkout where users transition from our main site xyz.com to store.xyz.com, which is actually operated by our e-commerce partner. An artifact of this seems to be a large percentage of transactions being misattributed to our internal session refresh channel in Adobe Analytics. I think that updating the way we set cookies on the site may alleviate this issue, but I'm not positive. Does anyone have any guidance or advice on this issue?
Solved! Go to Solution.
Views
Replies
Total Likes
Double check that the cookieDomain, trackingServer, trackingServerSecure parameters are set correctly on both sites.
Could you share or DM a link to your website?
Just a quick check - are we sure we have VisitorAPI.js implemented on store.xyz.com as well? Also are you also seeing VisitorAPI.js or MID not generating on other pages of the site on xyz.com?
Views
Replies
Total Likes
Double check that the cookieDomain, trackingServer, trackingServerSecure parameters are set correctly on both sites.
Could you share or DM a link to your website?
Views
Replies
Total Likes
To add to the questions you've already been asked, are you confident that your internal domains are properly identified, and that your Marketing Channel Processing Rules are accurately defined? I ask because of this statement from your original question:
"An artifact of this seems to be a large percentage of transactions being misattributed to our internal session refresh channel in Adobe Analytics."
Are there other signs that point to this being a cookie/ECID issue, or is this the inflated Internal Session Refresh channel the only issue?
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes