3 ms·
Well my point is I guess there should be no cookie set for the read-only experience. Once you do something that requires tracking some state server-side, then t
by watt 14y ago
Well my point is I guess there should be no cookie set for the read-only experience. Once you do something that requires tracking some state server-side, then the session cookie might be set. For example if you are searching, or you submit some data (that might trigger the message flashed), I guess the page where you perform said action could contain the cookie notice and notify user that to perform such stateful action user will need to accept the cookie.
For example, if you visit a web shop, you shouldn't need to get any cookies when viewing a product page. If you decide to put it into shopping cart - then you would consent to getting a cookie. But no sooner!
- untog 14y ago...unless there is an A/B test running.
- jonknee 14y agoThat's a bizarre way to look at things. The good news is you can very easily make this your reality by changing a setting in your browser. There are tons of reasons why "read-only" could make use of cookies. Here are a few, using your ecommerce example: 1) A/B test 2) General site analytics, to see how many unique visits your shop gets 3) More detailed conversion analytics to figure out things like the value of a visit, how long someone takes before making a purchase, knowing the origination of all conversions, etc. 4) Remembering viewed items so they can be promoted on a future visit 5) Displaying a "Welcome back" message to second time visitors If you don't do these things you will be beaten by people that do. eCommerce might be the absolute worst example you could have come up with for situations where cookies are not needed.