Hi,
I was wondering if anyone can clarify if 's_fid' is the visitor cookie if the visitorAPI.js first-party cookie tracking is adopted.
If it is then is the 's_vi' cookie used at all in visitor identification.
Thanks,
Sid
Solved! Go to Solution.
Views
Replies
Total Likes
Hi Sid,
If you have not enabled a grace period, new visitors are given only an AMCV cookie which is now used instead of s_vi. If a visitor already had an s_vi cookie from a previous visit though, it will continue to be used instead of the AMCV cookie.
The table at the bottom of this topic has more details: http://microsite.omniture.com/t2/help/en_US/mcvid/mcvid_analytics.html
Views
Replies
Total Likes
Hi
When cookies are rejected, Adobe uses a fallback method to determine a unique visitor. The fallback method varies depending on the analytic code version implemented on your web site. Broadly speaking, there are three possible fallback methods, the original method using IP address and user agent string, the new fallback method using the s_fid first party cookie, and finally, the option to go with a true first party cookie. (refer :http://microsite.omniture.com/t2/help/en_US/sc/implement/visid_fallback.html)
Regards
Devinder
Views
Replies
Total Likes
Hi Sid,
If you have not enabled a grace period, new visitors are given only an AMCV cookie which is now used instead of s_vi. If a visitor already had an s_vi cookie from a previous visit though, it will continue to be used instead of the AMCV cookie.
The table at the bottom of this topic has more details: http://microsite.omniture.com/t2/help/en_US/mcvid/mcvid_analytics.html
Views
Replies
Total Likes
Hi Devinder,
Thanks. What will be first cookie that will be looked for visitorAPI.js visitor identification by Adobe before using the fallback cookie 's_fid'? Is it 'AMCV_' or 's_vi' cookie?
Thanks
Sid
Views
Replies
Total Likes
Hi
JavaScript 1.x and JavaScript H.25.3 (released January 2013) contain a new fallback visitor identification method for visitors whose browser blocks the cookie set by Adobe’s data collection servers (called s_vi). Previously, if a cookie could not be set, visitors were identified using a combination of the IP address and user agent string during data collection.
With this update, if the standard s_vi cookie is unavailable, a fallback cookie is created on the domain of the website with a randomly generated unique ID. This cookie, named s_fid, is set with a 2 year expiration and is used as the fallback identification method going forward. This change should result in increased accuracy in visit and visitor counts in situations where the primary cookie (AMCV_ or s_vi) cannot be set.
Visits total includes all visitors that are identified by the s_vi cookie or by using a fallback method.
Regards
Devinder
Views
Replies
Total Likes
Hi Devinder
I understand the 's_fid' fallback cookie but imagine we're setting the first-party cookie using visitorAPI.js (the new recommended solution by Adobe for setting visitor cookie) rather than subdomain solution, and the browser accepts the cookie as this is set on the domain by visitorAPI.js. What will be the cookie in this case - 'AMCV_' or 's_vi'?
Thanks
Views
Replies
Total Likes