That's a very good point - one that I've thought about but not done anything about as of yet. A "product view" could be negative as much as it could be positive from a user reco standpoint - but from an item similarity standpoint if you're shopping for plumbing widgets than everything you looked at is probably likely to be somehow related to plumbing widgets.
One thing I also have not done is remove items that were ordered and then returned. Is anyone willing to share some thoughts on other web-store inputs that might be good? Or maybe things that might appear good but backfire? --Matthew Runo On Feb 16, 2011, at 8:07 PM, Ted Dunning wrote: > My experience is that there is a very small number of events that indicates > real engagement. Using them in the form of Boolean preferences helps results. > A lot. > > Using all of the other events that do not indicate engagement is a total > waste of resources because you are simply teaching the machine about things > you don't care about. > > Moreover there are probably some kinds of events that vastly outnumber > others. Events that are less than 1% of your can matter bit often not. > > The valuable secret sauce you will gain is which events are which. Which make > your system sing and which ones just clog up the drains. > > Matthew wrote: > users can do.. "view", "add to cart", and "buy" which I've assigned > different preference values to. Perhaps it would be better to simply > use boolean yes/no in my case?
