Here we referenced the most common Strategy Use Cases

Product Attribute Promoter

This use-case is used to either filter or boost a specific range of products based on a product attribute. For example, you can create a strategy to only show products, which are made in Switzerland or make sure that products from a specific brand appear first in the search results.

The use-case can be configured like this:

Field: The field you want to set the filter on

Values: The values you want to filter or promote

Amplify: Promote the values to higher positions or filter all other values out .

In the fourth tab (advanced) you can choose the operator (equals, contains, does not contain, …).

The boost weight is the value which defines how much the products should be amplified.

The Options and Settings tabs are explained further below. When you are satisfied, you can click Save & Test and then go to the test-view to see if the behaviour is like what you wanted.

On the left side you have the products without the use-case active and on the right side you have the use-case active as a promoter. The Products, that have the attribute Hiking in the Field are promoted to higher positions and the products, which don't are displayed lower. If the use-case is configured as a filter, the products, which don't have the attribute Hiking, are not displayed at all. To see the values in the fields, you have to add the fieldname in the advanced-tab of the test-view

under display-fields

Newsletter Campaign Parameters

A different case where this use-case us used, could be with newsletter campaigns.

For example, you want to send out a promotion e-mail, for the Brand LÖFFELER. First you navigate to the widget you want to use for the newsletter images, in this case we will use the widget newsletter.

Add the Product Attribute Promoter to the configuration and select the field you want to filter on. For this example, we will use the field products_brand. After clicking on the - button and selecting the desired value (LÖFFELER), you can untick the amplify-button to filter out all the other products.

The next step is adding the campaign parameter. Go to the settings-tab and click on the - button to open the quick segment creator. In the first field select REQUEST_CONTEXT_PARAMETER and in the second, you can write your desired parameter. (It can be whatever you like.) Then click add.

When you're done, click on Save&Test and then make sure that the correct products appear in the test view by adding the parameter in the context-tab in the test view.

Check if the products, that appear are the correct ones and if they are, publish the account. You can also add the brand-field in the advanced-tab to make sure of this.

The newsletter link could therefore look like this:

https://api.bx-cloud.com/p13n.rest/img?user=account_name&

indexId=account_name&apiKey=1234567890&

profileId=abcd&customerId=abcd&choiceId=newsletter&

lang=en&offset=0&rc_campaign=LÖFFELER 

 Random Promoter

This use-case is used to randomize the products that appear. There is nothing to configure in this use-case, you just have to drag the use-case into the widget configuration and click Save&Test.

It is quite simple to test the behaviour. You can just keep refreshing the products and it should be different products every time. Refresh by clicking this icon:

Article-based Repeater

This use-case is used to promote articles with the same value as the item you are looking at. For example, you are looking at a product, that is made of nylon and polyester and you want the products that are recommended also to be made of the same material. In this case you need to use this use-case.

In the use-case configuration in the values-tab there are two options. The first option is the field you want to base the similarity on and the second option determines if you simply want the similar products to be boosted to higher positions or all the other

products to be filtered out.

= Boost

= Filter

In the fourth tab (advanced) you can choose the operator (equals, contains, does not contain, …).

The boost weight is the value which defines how much the products should be amplified.

The Options and Settings tabs are explained further below. When you are satisfied, you can click Save&Test and then go to the test-view to see if the behaviour is like what you wanted.

As you can see this product has the ID 36 and has the values Plastic and Rubber.

To test the use case, you have to emulate being on the product detail page of this product. To do this you have to add the ID in the context-tab in the enter and item id-field. In the advanced-tab you can add the field you're promoting in the display fields-field, so you can see if the use-case works correctly.

On the left side, you can see the products normally, on the right, the id is added in the context menu. You can see, the products with the values plastic or rubber in the field products_material are promoted. Also, the products with both of the values in the field are promoted more than the products with only one or the other.

Add Return Field

This use-case adds any field you want to the response. So, for example, you want to access the value from the field products_image, you can add it in the strategy and then retrieve it in the response.

The only thing you need to configure, is the field, you want to be returned.

After clicking Save&Test you can see that the field is displayed automatically in the products in the test view. On the left you can see the products without the use-case active. On the right side the use-case above is enabled.

 Add Hit Field Name

This use-case is used to add a field to the products which is created by combining various inputs. Often it is used to create a URL, where the final name of the target is the id.

You have five different fields:

finalFieldName: The name of the new field

field: The name of the field, of which you want to use the value.

prefix: What should come before the fieldvalue.

midfix: What should come between the prefix and the fieldvalue. (usually the language followed by an underscore)

postfix: What should come after the fieldvalue.

So, in this case, where the ID of the product is 1, the field would be displayed like this: