coopjakob
commented
4 years ago Oh, I forgot to mention that I created two "placements" in Rich Relevance. One with just a few product and one for many more products.
My solution is that "a few products" is loaded for everyone. Then, if you're on mobile, a button will be shown to display the full list. And on desktop this will be loaded automatically.
I like this flow because it's a very similar technical solution on mobile and desktop. Instead of building separate solutions for mobile and one for desktop.
- As an example we don't need to wait for screen size to get the first "few" products.
- Another benefit will be that mobile and desktop share the same stats.
But yes, duplicates needs to be removed before showing the full list, because the response from the first request is not automatically removed on the second one.
benjick
Rich Relevance (RR) gives us a personalised list of product recommendations. They have API for JSON data, and request URL:s for tracking. Coop aslo have API for product data.
RR have AI strategies that will need some tracking data from us. When they send a list every product in the list is marked as viewed, so we can't just get a list of 100 and show 4.
When someone click a product or add to cart another request should be made. The URL:s is received by the initial request.
This is an example of a request: https://www.coop.se/ws/v2/coop/users/anonymous/products/recommend-segmented?placements=home_page.2020_start_few&fields=DEFAULT&storeId=${this.storeId}&rrSessionId=${this.rrSessionId}&rcs=${this.rcs}`
storeIdmight be 016001 for Stockholm.rrSessionIdis the session (even if you're logged in)rcsis sent as a response of the first request and can be added to session storage.This will receive a ordered (sorted by rank) list from RR, and our Hybris API (coop.se/ws) will update it with updated (but cached) content.
We can also request data directly from RR: https://recs.richrelevance.com/rrserver/api/rrPlatform/recsForPlacements?apiKey=c5aa3f92242c950c&apiClientKey=182bc783b3c1fff9&returnMinimalRecItemData=true&rcs=eF5jYSlN9jBIMzI3M0lL000yTUvVNTG0SNY1TDUxBRKmyUCcmmZpmsiVW1aSmSJgaG5sqWuoawgApuYO1A&sessionId=daj0jpfe1p3xu3c&placements=home_page.2020_start_few&rid=016001
In this case I added
returnMinimalRecItemData=trueto show that we might have a problem with this data being old, and that it should not be used. But a list of ID is fine, because we also have an API that can receive specific product data...https://www.coop.se/ws/v2/coop/users/anonymous/products/2097522500000?fields=BASIC
My suggestion would be to only get a list of ID directly from RR and then populate each ID with data for specific products. Then the data, promotions etc, will never be wrong.