We have just started with the recommendation functionality in Target. We want to use the 'Most popular' algorithm on the page, but want to exclude the articles that are already viewed by the visitor. How can we set this up in Target for recommendations? With the exclusion functionality?
Solved! Go to Solution.
Views
Replies
Total Likes
Adobe Target handles this out of the box as long as you have entity.id parameter for the Target call set up on the product pages. There is also a checkbox in the criteria creation screen to allow/disallow recommendations to be previously purchased (I think). In order for purchase to populate for the user profile, an order conversion will have to take place.
Views
Replies
Total Likes
Adobe Target handles this out of the box as long as you have entity.id parameter for the Target call set up on the product pages. There is also a checkbox in the criteria creation screen to allow/disallow recommendations to be previously purchased (I think). In order for purchase to populate for the user profile, an order conversion will have to take place.
Views
Replies
Total Likes
Thanks for your feedback.
We have an entity.id parameter, so this means that no single configuration is needed in the recommendations? Already viewed pages are automatically filtered out? Is this real time?
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Dear Eric, we see in the output of the mboxTrace that the "user.endpoint.lastPurchasedEntity" has indeed all the ID's of the already viewed "articles". So that's already good news.
In the recommendations on the website however, only the "article" that is currently viewed is excluded, not all the already viewed "articles". We cannot add the "user.endpoint.lastPurchasedEntity" in the script (we receive an error) in orde to be used in the "exclusions" for example. Do you have a solution for that?
Thanks!
Kim
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Like
Replies
Views
Like
Replies