Analyzing Data from Cookies
If a user does not allow cookies, and you have implemented AuthManager to encode the ticket onto the query string, then the ticket data is placed in an encoded URL string. The URL string can be used to pass user information between pages.
Cookie data might be inaccurate. For example, the first time a user initially visits a Commerce Server site, the site issues the user an anonymous ticket with a GUID as the key. After the user registers on the site and enters profile data, the anonymous (profile) ticket is re-issued to the user by using the user login ID as the key.
After a Commerce site reissues an anonymous profile ticket updated with the profile key (login user ID), the updated profile ticket is re-persisted for that user as the persistent cookie for the site. Reissued profile tickets can cause inaccuracies in the Web log file data imported for the site. The cookie will work the next time the user visits the site, except if the user deletes cookies or visits the site from multiple computers, or multiple users (with individual user IDs) visit the site from the same computer.
See Also
Copyright © 2005 Microsoft Corporation.
All rights reserved.