{"id":5623,"date":"2019-05-02T13:33:45","date_gmt":"2019-05-02T11:33:45","guid":{"rendered":"https:\/\/www.recolize.com\/?p=5623"},"modified":"2019-05-02T14:29:29","modified_gmt":"2019-05-02T12:29:29","slug":"optimize-recolize-recommendations","status":"publish","type":"post","link":"https:\/\/www.recolize.com\/en\/blog\/optimize-recolize-recommendations\/","title":{"rendered":"How to Optimize Recolize Recommendations?"},"content":{"rendered":"
\n \n
<\/div>\n\n
\n
\n
\n

One of the central questions of our new customers is, how to optimize Recolize Recommendations in their daily business, to get a better performance? As Recolize offers a totally different approach compared to competitors to integrate recommendation widgets into a page, the analysis of the recommendations also differs from fixed positioned widgets.<\/p>\n

The Recolize Difference<\/h2>\n

In the Recolize Tool<\/a>\u00a0you are very flexible to define your recommendation widget positions based on existing CSS elements on your website. So you are free to integrate the recommendations without any developer resources, for every landing page etc. Furthermore you define your recommendation rules completely URL based and not<\/strong> widget based.<\/p>\n

Flexible Widget Positions Through CSS Selectors<\/h3>\n

Let’s make an example from our Magento 2<\/a> demo system:<\/p>\n

\"\"<\/h2>\n

The Recolize widget in this case of a product page is defined as:<\/p>\n

.product.info.detailed:after<\/pre>\n
This CSS selector simple means: display a Recolize widget on every page which has the element .product.info.detailed<\/strong> after this specific element. So you are free to use every<\/strong> existing CSS element on your website. Anytime, very flexible, as many widgets as you want per page and the widgets are displayed instantly.<\/p>\n
URL Based Rules for Very Specific Recommendations<\/h3>\n
In difference to other less flexible systems, in Recolize you define your recommendation rules URL based. As there can be multiple widgets on a single page, you define the URL and the position of the widget as base for the rule. For determining the position, you simple count through the displayed recommendation widgets from top to bottom.<\/p>\n
We’ve decided to offer URL based recommendation rules, because marketeers work with URLs in all performance marketing channels to generate traffic to a website and we want to improve the conversion of this traffic onsite also URL based to make it easier. Therefore it is e.g. possible to display different recommendations based on a campaign parameter in an URL.<\/p>\n
E.g. the URL<\/p>\n
http:\/\/demo.magento2.recolize.com\/hero-hoodie.html?utm_campaign=Blue Jeans<\/pre>\n
can then display different recommendations in the same widget\/position, based on the utm_campaign<\/strong> parameter compared to the URL<\/p>\n
http:\/\/demo.magento2.recolize.com\/hero-hoodie.html<\/pre>\n
without a campaign parameter.<\/p>\n
1. Integrate Your First Widgets<\/h2>\n
The first step after you start with Recolize is to define the CSS selectors to display recommendation widgets on your website. The CSS selector system was described above.<\/p>\n
It’s much better to start with several widgets than to start with only a single widget on e.g. product pages. Many customers tend to start small and extend later. But you will get much more relevant results for your analysis, if you use our USP to add as many widgets per page as you want to.<\/p>\n
2. Define the Cycle for the Analysis<\/h2>\n
Very important for a reasonable analysis is to define a time cycle for the analysis. The cycle should mainly depend on the traffic of your website. Traffic either means unique users or page impressions.<\/p>\n
Start with the following base cycle:
\n\n
\n    \n    \n\n    \n\n        \n        \n\n\n                    wdt_ID<\/th>        Traffic (Page Impressions)<\/th>        Cycle (Days)<\/th>    <\/tr>\n<\/thead>\n        \n\n        \n        \n\n        \n                    \n                    \n                    \n                    \n                    \n                    \n                    
1<\/td>\n                    10.000<\/td>\n                    60<\/td>\n            <\/tr>\n            
2<\/td>\n                    50.000<\/td>\n                    50<\/td>\n            <\/tr>\n            
3<\/td>\n                    100.000<\/td>\n                    40<\/td>\n            <\/tr>\n            
4<\/td>\n                    200.000<\/td>\n                    30<\/td>\n            <\/tr>\n            
5<\/td>\n                    500.000<\/td>\n                    21<\/td>\n            <\/tr>\n            
6<\/td>\n                    1.000.000<\/td>\n                    14<\/td>\n            <\/tr>\n            
7<\/td>\n                    5.000.000<\/td>\n                    7<\/td>\n            <\/tr>\n    <\/tbody>        \n\n        \n        \n        \n\n    <\/table>\n\n<\/div>