Originally Posted by
pshuang
A 10 minute timeout would probably suffice to explain my experiences. It's pretty easy for something online or offline to take me away from interacting with Hyatt.com for that short a period of time; and most other Web sites I deal with that have login sessions don't expire my session that quickly, the only ones that do that come to mind are online banking sites.
Digging through logs to determine the frequency of users hitting the 10 minute timeout and have to re-login to continue what they were doing can be a tricky business. How sure are you that your log files data mining is doing a good job of characterizing this rate? For example, based on my FT username, you can figure out what my Hyatt GP account number is. Does your log data mining show that my Hyatt.com session timed out on me a couple of times today and I had to re-login to continue what I was doing?
Bill from E-Commerce here.
We're doing some work on session management that will make it practical to set longer session timeouts. This will take some time however.
Most people move through their interaction with Hyatt.com fairly quickly. As you might expect, a very large number are there for something very specific like getting a phone number or address and then they immediately leave. However, if you're one of the people that the session timeout hits, this is cold comfort. We're going to look at increasing the session timeout and apologize for any inconvenience.