If you are using the Display Recently Viewed action in your Web Activity and your store has a custom command for ProductDisplay or CategoryDisplay you are at the right place.

To determine the catalog entries or categories a customer has recently viewed, the server uses either the categoryId value on the CategoryDisplay URL or the productId value on the ProductDisplay URL. If your store uses page view names or URL parameter names that are different from the default, then the recently viewed list will not work unless a developer performs some customization steps.

Custom Commands: Recognize customer browsing behavior when the URL is not the default URL ProductDisplay or CategoryDisplay

If you have a custom command to implement ProductDisplay with the name MyProductDisplay the "Command name to match in the behavior rule" will have to be changed to support the custom command name.

This can be done by using the following steps:

1. Create a new folder at the following path: WC_eardir\xml\config\com.ibm.commerce.marketing-ext\.

Since by default the server uses either the categoryId value on the CategoryDisplay URL or the productId value on the ProductDisplay URL to determine the catalog entries or categories a shopper has recently viewed, you may add the following customization to the marketing engine to recognize items by not using the default parameters they will need to perform the following steps:

Example on how to add customization so that the engine looks at catEntryId instead of productId.

The following link provides high level instructions on how to customize the behavior template:

You will need to repeat the procedure 3 times as there are 3 templates that refer to productId. So for step 3, the name_of_template you need to used are: 'recordedCustomerBehaviorProductBrowsed', 'currentCustomerBehaviorProductBrowsing' and 'recentlyViewedProducts'.

1207 is the new ID. As in the documentation, we just add 1000 to the original ID of 207. But this ID can really be whatever they want. The highlighted 207 are the ID's of the rule we're copying. The only thing we're changing is the catEntryId parameter in the behaviourxml field.