This is no problem at all. You can add as many development, test and staging environments as you need to. Completely for free.

Just add additional domains in the Recolize Tool under “Domains”.

If you have a publicly reachable product feed for you development environment, then add it to your new domain. If not, no problem at all: enter the domain of your local development environment as feed url. We will import a demo feed then and you can completely integrate Recolize by using the demo products.

And if your test- and staging systems are password protected, then check out this FAQ. It explains, how to add a password protected feed url to your domain.

And the best: configure your recommendation rules beginning with the URL placeholder “*/”. Then the rules will also match for all your development, test and staging environments, you don’t have to configure these rules multiple times and you can really test the rules equally in all environments.

A common problem for product recommendations e.g. in the fashion market is to filter the recommendation carousels for the size of the user.

Given that we have a shoe online shop and the user is able to specify his shoe size in his account settings, we can use the following steps to filter the recommendations for that specified shoe size:

• Save the user shoe size either in the session, browser cookie or browser local storage and define the appropriate Recolize parameters via JavaScript on every page before the general Recolize JavaScript snippet is defined:

var RecolizeParameters = RecolizeParameters || {};
RecolizeParameters.Context = RecolizeParameters.Context = {};
RecolizeParameters.Context.CurrentUser = RecolizeParameters.Context.CurrentUser || {};
RecolizeParameters.Context.CurrentUser.available_sizes = '#### PUT THE COMMA-SEPARATED LIST OF CHOSEN USER SHOE SIZES HERE ####';

• Assure that in your Recolize product feed you provide the information of the shoe size either as a specific value (e.g. size = 36) or as a list of comma-separated values (e.g. size = 34,36,38). For now we assume that you have an additional column called “available_sizes” in your feed that contains a comma-separated list of shoe sizes that are available for the shoe.
• Now go to the Recolize Tool and define a new Recommendation configuration with the following filter combination:
  

The interesting part here is the %CurrentUser.available_sizes% variable that gets filled with the chosen shoe sizes of the user.

The cool thing is basically you can define any attribute that you like, i.e. the whole JavaScript array below RecolizeParameters.Context is available in the filter of the recommendation configuration.

We have made extensive research and evaluated user feedback on what is the best format and style of the product recommendations. And the result was our product carousel that you get with Recolize out-of-the-box. So for the huge majority of cases we recommend our customers to use this carousel and the presented elements as it is.

In most of the cases it is not necessary to change the structure of the Recolize Carousel HTML. You can use the CSS pseudo classes ::before or ::after to nearly do anything you want without changing the structure.

Therefore we do not recommend to change the HTML structure.

If you really still want to change the structure, you can do this in our success callback:

var RecolizeParameters = RecolizeParameters || {};
RecolizeParameters.Api = RecolizeParameters.Api || {};
RecolizeParameters.Api.successCallback = function(resultObject) {
    for (var widgetPosition in resultObject.widgets) {
        // add your structure changes here in resultObject.widgets[widgetPosition].content[0] 
    }

    Recolize.Recommendation.Api.render(resultObject);
}

Recolize supports several ways to provide us with your product data that we need in order to generate personalized product recommendations.
Next to the Magento feed format, Google product or Billiger.de feeds we have a custom Recolize feed format that you can use.

Definition

Format: CSV
Encoding: UTF-8
Important: CSV file may not contain a BOM
Delimiter: semicolon (;)

Mandatory Fields:

• id
• name
• url

Optional Fields:

• image_url
• brand
• categories
• price
• special_price
• price_currency
• updated_at

Additional Fields:

Next to the mandatory and optional fields you can add as many additional columns to the feed as you want to. All fields will then be available in the Recolize Tool for filtering.

Example

id;name;url;image_url;brand;categories;price;special_price;price_currency;updated_at
1;"Recolize Testproduct 1";http://www.recolize.com;http://www.recolize.com/image_url.png;Recolize;"Kategorie 1,Kategorie2";1.99;0.99;EUR;"2018-08-01 12:45:21"