Accessing Product Campaigns

There are several types of product campaigns, depending on the display location. Product detail page and shopping basket are predefined but there is also a placeholder definition. It can be used to define campaigns for custom display locations (e.g. homepage).

These campaigns must be fetched explicitly by invoking a FACT-Finder API call. The parameters to fetch detail-page campaigns are the channel and article number of the product being displayed. The parameters for the shopping-basket campaigns are the channel and a list of the article numbers of the products in the shopping basket. The call to fetch the placeholder campaigns needs the channel and the id of the page, for which the campaigns should be fetched. All endpoints possess a parameter named sid which contains the session identifier of the user for whom to personalize pushed product sets. If the session parameter was absent such product sets are returned unpersonalized.

XML

$stringEscapeUtils.escapeHtml($body)

JSON

$stringEscapeUtils.escapeHtml($body)

JSONP

$stringEscapeUtils.escapeHtml($body)

REST

FACT-Finder 7.3 adds a REST-API. The search application contains the technical documentation and can be accessed via this URL:

$stringEscapeUtils.escapeHtml($body)

The interface offers not only the parameter documentation, but also the option to test a query and review the result. The documentation was created with Swagger, you can use Swagger Codegen to generate a client for it and use it for your code.

To access product campaigns, use the campaign method.

Webservice / SOAP

The methods getProductCampaigns(), getPageCampaigns() and getShoppingCartCampaigns() can be used if you want to use web service calls. They are provided by the following end point:

$stringEscapeUtils.escapeHtml($body)