false

html_restricted

Hi Andy You're correct that 30 days has often been the default, at least for marketing/advertising tracking online. However, I found out recently that Google Analytics' default is set to 60 days. It's the same with the length of a 'session' or visit which, by most web server standards, is usually set to 30 minutes. But what is right depends on your business, the way you wish to understand the data, or, just possibly, what you want to make the data say! For example: - If you want to make it look like you're getting more visits to your site just reduce the timeout value on your webserver and/or web analytics software. Bingo ! More visits. But probably also annoyed customers whose session data evaporated when they came back to your site having just gone to make a cup of tea. - If you want to pay your affiliates more, or less, then just adjust the cookie value up or down. - If you want to make various forms of online marketing look more, or less, effective, then just adjust the cookie expiry length up or down. Some might say that because (paid) search has often received the 'last click' (coupon sites now doing well here) then it is in Google's interest to set the expiry length default in GA as long as possible because it will probably make paid search look more effective? And, of course, with all the above, if you change your expiry length you'll have data / stats that don't quite match up for a while until the changes have worked through and you have new benchmarks to work with. I guess a lot depends on how you measure value, how you choose to reward others (affiliates etc.) for value creation, and your product/customer base e.g. if you're selling CDs then the consideration/purchase window is *much less* than if you're selling mortgages so your cookie expiry length would, presumably, be much shorter too. Crudely speaking I guess your cookie expiry length could be as long as the consideration/purchase window for, say, 80% of your customers?

Hi Andy You're correct that 30 days has often been the default, at least for marketing/advertising tracking online. However, I found out recently that Google Analytics' default is set to 60 days.  It's the same with the length of a 'session' or visit which, by most web server standards, is usually set to 30 minutes.  But what is right depends on your business, the way you wish to understand the data, or, just possibly, what you want to make the data say!  For example: - If you want to make it look like you're getting more visits to your site just reduce the timeout value on your webserver and/or web analytics software. Bingo ! More visits. But probably also annoyed customers whose session data evaporated when they came back to your site having just gone to make a cup of tea. - If you want to pay your affiliates more, or less, then just adjust the cookie value up or down. - If you want to make various forms of online marketing look more, or less, effective, then just adjust the cookie expiry length up or down. Some might say that because (paid) search has often received the 'last click' (coupon sites now doing well here) then it is in Google's interest to set the expiry length default in GA as long as possible because it will probably make paid search look more effective? And, of course, with all the above, if you change your expiry length you'll have data / stats that don't quite match up for a while until the changes have worked through and you have new benchmarks to work with.  I guess a lot depends on how you measure value, how you choose to reward others (affiliates etc.) for value creation, and your product/customer base e.g. if you're selling CDs then the consideration/purchase window is *much less* than if you're selling mortgages so your cookie expiry length would, presumably, be much shorter too. Crudely speaking I guess your cookie expiry length could be as long as the consideration/purchase window for, say, 80% of your customers?

2009-09-29T14:41:26+01:00

true

3547

12182

false

http://econsultancy.com/forums/best-practice/cookie-expiry-length

2009-09-29T14:41:28+01:00

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.195.21 Safari/532.0

77.89.154.226