how to prepare the behavior data for those OOTB templates in Recommendations Criteria? | Community
Skip to main content
practitioner-pin
practitioner-pin
Level 2
May 9, 2022
Solved

how to prepare the behavior data for those OOTB templates in Recommendations Criteria?

  • May 9, 2022
  • 1 reply
  • 1240 views

Hi, I'm curious about how to prepare the behavior data for OOTB - "Most Viewed Products within a Visitor's Favorite Category." According to the documentation - Pass behavioral information and context, I can't find any practice or sample code mentioning to pass a Visitor's Favorite Category. If the related data isn't available, I guess this OOTB Criteria couldn't work correctly.

 

In addition, I found that many OOTB templates seem to have required behavior data in place before adopting the templates. Does anyone know any elaborated document to describe those preparation work or if any required data should be passed to AT first?

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by kchaitanya

Hi @practitioner-pin , 

Favourite category is defined by Adobe Recommendations through a backend algorithm. You will have to pass the entity.categoryId value when user navigates to a product page that belongs to a particular category (NOT when user adds a product to my favourites - that could be defined as a custom key to be used in other Recommendations algorithm) using the sample code format you shared. 

The rest of calculations to define the favourite category is handled by Target Recommendations at the backend. Think of a simplified logic as the category that gets maximum page views by a visitor becomes the favourite category for that visitor.

Hope this helps!

1 reply

kchaitanya
kchaitanya
Level 3
May 10, 2022

Refer to this document for the information you are looking for specific to the favourite category (entity.categoryId has to be passed in mbox calls): https://experienceleague.adobe.com/docs/target/using/recommendations/criteria/base-the-recommendation-on-a-recommendation-key.html?lang=en#:~:text=search%20results%20pages.-,Favorite%20Category,-The%20recommendation%20is

practitioner-pin
practitioner-pinAuthor
Level 2
May 10, 2022

Hi @kchaitanya,

 

Thank you for your information. May I explore more about this approach?

 

The document mentions that "When this option is selected, the entity.categoryId value must be passed as a parameter to the display mbox." Do you know when / where to pass it? Does it mean setting a Launch rule to track a visitor's click behavior on the "Add this product to my favorite" icon with the targetPageParams() method? 

 

The document doesn't elaborate on the "Favorite Category." Back to the page of "Pass behavioral information and context, " the "Item views/product pages" section provides the sample code. It's the same to pass entity.categoryId. But what's the difference from the Favorite Category? 

Could you help to solve the puzzle?

 

Thank you,

 

 

 

practitioner-pin
practitioner-pinAuthor
Level 2
May 12, 2022

Hi @practitioner-pin , 

Favourite category is defined by Adobe Recommendations through a backend algorithm. You will have to pass the entity.categoryId value when user navigates to a product page that belongs to a particular category (NOT when user adds a product to my favourites - that could be defined as a custom key to be used in other Recommendations algorithm) using the sample code format you shared. 

The rest of calculations to define the favourite category is handled by Target Recommendations at the backend. Think of a simplified logic as the category that gets maximum page views by a visitor becomes the favourite category for that visitor.

Hope this helps!


Hi @kchaitanya, 

Thank you so much for clarifying the "Favorite Category," which is handled by Target Recommendations at the backend. And point out the approach of a custom key if needed to specify the behavior.

It helps me to figure out the logic behind the official document. Thank you again.

Terms & ConditionsAccessibility statement

Loading footer...