Skip to Content

Which Odata service to be used for Product Recommendations in Hybris Marketing?

Hi All,

We have tried using Odata Service - PROD_RECO_RUNTIME_SRV for getting Product recommendations. But the result is inconsistent with respect to counts or even the recommended products differ, when we compare the result between Manage Recommendation of Hybris Marketing(1702) and Products coming up in Hybris Commerce(6.3).

As per the link https://help.hybris.com/6.0.0/hcd/8c53034a86691014ad02c94f132140b1.html , PROD_RECO_RUNTIME_SRV is the service to be used for Hybris Marketing cloud environment and PROD_RECO_SRV is the service for Hybris Marketing On-premise. However we couldn't find any entity available in PROD_RECO_SRV that can be used by Commerce environment to get Product recommendations. As we have Out of the Box only Scenario ID to pass by Hybris Commerce.

While debugging Manage Recommendation in Hybris Marketing, we got to know that Entity - QuickChecks of PROD_RECO_SRV is used to preview the Product recommendations. Here Model type and Model ID is passed to get the product recommendations . But in our case while integrating with Hybris Commerce 6.3, Out-of-the-box solution can only pass Scenario ID.

Please let me know which Odata Service to use while integrating with Hybris Commerce 6.3 for Product Recommendations. Also, which entity to be used.

Regards,
Deepu Pankaj

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jan 30 at 10:32 AM

    Hi All,

    The issue was with respect to the configuration of algorithms classes. We have configured Collaberative-filtering and post processing algorithm classes as optimized algorithm. In fact we are only supposed to make association, item-mapping and query based algorithms as optimized others are non-optimized.

    Because of the wrong configuration, model generation procedures have wrongly generated scores and products were repeated irrespective of change in contact id or lead items for product recommendations.

    Initially we thought the issue was with respect to the Odata service because recommended products in Manage recommendation and Odata service Result was differing.

    Now by configuring algorithm classes properly as optimized and non-optimized, results are properly generated. Ensure to re-generate all the models after configuring changes.

    Please go ahead and use PROD_RECO_RUNTIME_SRV service for Hybris commerce integration..

    Regards,

    Deepu Pankaj

    Add comment
    10|10000 characters needed characters exceeded