When returning to a Searchspring powered PLP from a PDP the result set can be completely different due to personalization parameters changing and the result set being personalized; this can often lead to cases where the result that was just clicked on is no longer in the results - which is very confusing to the customer and bad UX.
One solution would be to rely more heavily on our network cache in these situations - however the cache is currently keyed by all of the request "cache" parameters (which currently includes personalization parameters 'shopper', lastViewed and cart). We could remove these from the cache key to potentially resolve.
When returning to a Searchspring powered PLP from a PDP the result set can be completely different due to personalization parameters changing and the result set being personalized; this can often lead to cases where the result that was just clicked on is no longer in the results - which is very confusing to the customer and bad UX.
One solution would be to rely more heavily on our network cache in these situations - however the cache is currently keyed by all of the request "cache" parameters (which currently includes personalization parameters 'shopper',
lastViewedandcart). We could remove these from the cache key to potentially resolve.https://github.com/searchspring/snap/blob/v0.61.5/packages/snap-client/src/Client/apis/Legacy.ts#L23