Solutions - Retailer

Froomle can be used to personalize every aspect of your online interaction with your customers. Some examples are:

  • Personalized e-mail campaigns

  • A personalized homepage

  • Personalized search results

  • "You may also like" on product detail pages

Froomle incorporates as much of your data as we possibly can. The following is an overview of the required steps to set up an integration tailored to your retail use case.

There are three major steps:

Each will be discussed in detail in the sections below. After reading this you should have a clear overview of the steps required to integrate Froomle and some inspiration for your first use cases.

Metadata delivery

In a retail setting, Froomle needs at least your product catalog and up-to-date stock information to guarantee an optimal experience. Froomle provides an SFTP server to upload periodic data dumps. Reference information on the SFTP can be found here: Reference - Data Upload (SFTP). If the SFTP server cannot meet your needs, please contact your Froomle Solution Architect at support@froomle.com to discuss alternatives.

Froomle refers to your products as items. For a complete overview of how Froomle deals with metadata, see: Concepts - Items.

Product catalog

Your product catalog is used to apply certain business rules, such as: "Never recommend products under €20". Additionally, it is also used to interpret results during analysis, so that your recommendations can be improved further. Typically a product catalog contains at least the following information on products:

  • Product ID

  • Category

  • Tags

  • Brand

  • Price

  • Product model

The metadata you deliver to Froomle is by no means limited to the examples listed above. A product catalog is typically updated once a day.

Stock information

Stock information is essential to Froomle to decide what to recommend: Nobody likes being recommended a great product that turns out to be out of stock. Stock information is typically kept at the variant/size level, and not the product level, e.g. there are 10 sizes S and 15 sizes M of a certain t-shirt in stock. Even though Froomle identifies products at the product level, this is not an issue. It is however important to also supply a product identifier in a stock export, next to the variant identifier.

A typical stock export contains:

  • Product ID

  • Variant ID

  • Amount in stock online

Real-time tracking of browsing events

Froomle’s algorithms use your users' interactions with your website to make recommendations. We refer to your users' interactions as Events.

These events are communicated to Froomle using the Events API. This is a simple REST API that can be integrated both front-end or back-end depending on your needs.

Events for retail

Froomle supports a broad collection of event types to capture specific user behaviour. For retailers the most important event types are:

Tracking event types

Tracking events are events that can be used across all types of website or apps. The event types you can record as users make use of your website are:

User Event Name User Action

detail_pageview

Views an item detail page

group_pageview

Views a page containing multiple items e.g. categories, promotions

item_interaction

Interacts with an item e.g. product like, favourite, …​

group_interaction

Interacts with a group of items e.g. category like, favourite, …​

page_visit

Views a generic page not included in other pageview events

Integration event types

Integration events are all user interactions with recommendations on your website. These are the Froomle integration event types that you can record as users interact with recommendations on your website:

User Event Name User Action

impression

Views a personalised recommendation

click_on_recommendation

Clicks on a given recommendation

Retail event types

Retail events are all events specific to retail use cases. Froomle tracks the following events in the retail conversion funnel:

User Event Name User Action

add_to_cart

Adds item to cart

remove_from_cart

Removes item from cart

purchase

Completes a purchase

Examples

While we have listed all information required to integrate Froomle’s Events API, bringing everything together in an example use case might be more familiar. For such an example see: Integrating events on a retail website.

Requesting recommendations

Recommendations can be requested using the Froomle Recommendations API. For a full overview of the API specification see: Reference - Recommendations API. If you want more information on how to integrate this API in your webshop, go to: How To Guides - Requesting Recommendations.

Examples

If you are wondering what can be done with the Froomle Recommendations API on a retail website, look no further! Below are some examples of integrations for the most popular retail use cases:

Page Description

examples:retailer/recommendations/product_detail_page_integration.adoc

An example integration for a retailer’s product detail page