We have not implement s_vi in our website instead we are using fallback method and using s_fid cookie ,so my question are as follows.
1. Is it necessary to include s_vi cookie or s_fid will do.
2. How we implement s_fid cookie and s_vi
3. does not including s_fid causes any inflation in our results?
What version of H code are you using?
s_fid is the fall back solution when s_vi can not be set. The situaion that is most common is due to locking occurring.
s_fid and s_vi, while not exactly interchangeable are still used as the u Kaur identifier for the row of data. So moving forward when you implement s_vi or ECID, etc it will still count the rows as unique rows and data would not have been lost. The new tracker will take the place of s_fid for users where it is currently set.
ECID or s_vi will take precedent over s_fid and no inflation would be seen.
Hey @chrism18776410
AMCV and AMCVS should take precedence over s_fid, so if your marketing cloud ID is being set properly, you shouldn't see the s_fid in a debugger, in my experience.
Sometimes this can happen if Appmeasurement.js loads before s.Visitor.js - you can check that in the console using the command "s_c_il":
Notice the order of the array: 0 = Visitor (s.Vistior.js), 1= Appmeasurement (Appmeasurement.js)
I'd give that a check quick to be safe 
Let me know how you get on and if you need anything else
That's awesome to hear! Hope it all works out
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
