Getting Started with Personalized Recommendations

Miso's Personalized Recommendation Engine uses deep learning to recommend products your customers will love, based on their interests, preferences, and site interactions.

Example for Getting Started with Personalized Recommendations

Introduction

In this guide, we’ll discuss:

  • The importance of personalized recommendations
  • Choosing the right API for the job
  • Implementing personalized recommendations using APIs
  • Customizing personalized recommendations using Recipes

Why are personalized recommendations important?

Put simply, personalized recommendations drive conversions. Your customers are all unique; they have their own brand affinity, price sensitivity, lifestyle and aesthetic preferences that shouldn’t be addressed with a one-size-fits-all approach. By recommending products to your customers that you know they’ll love instead of only the most popular options, you are more likely to keep them engaged with your site, instead of encouraging them to shop elsewhere because they’re frustrated.

What makes Miso’s Recommendation Engine so unique?

Miso’s Recommendation Engine uses a deep learning, predictive model to determine the likelihood that a particular customer will purchase a particular product in their current session, next session, or in the next 30, 60, or 90 days.

Miso’s Recommendation Engine will select the products from your product catalog that are relevant to your customer and rank them by likelihood to be purchased. These recommendations are constantly changing in real-time, based on the insights collected from the customers’ interactions with your site (starting with just a single click, even with anonymous users).

The recommendations can be used to populate various product carousels, shelves, or ribbons on your site, such as “Products For You”, “Editor’s Picks”, and “You May Also Like”. Additionally, the Recommendation Engine supports a full suite of merchandising tools, such as boosting, pinning, and anchoring to tailor the recommendations to your unique business objectives.

Choosing the right API for the Job

Currently, Miso’s Recommendation Engine can be utilized via five APIs. Depending on your use case, you may use one or all the APIs to provide personalized recommendations on your site.

  • User to Products API

    • Purpose: For a given user, return a ranked list of products they are most likely to purchase, based on their past behavior.

    • Recommended for: “You May Also Like” ribbon, “Picked Just for You” ribbon, email marketing campaigns

  • User to Categories API

    • Purpose: For a given user, return a ranked list of categories (and products within each category) they are most likely to engage with.

    • Recommended for: category shelves (e.g. Outdoor Equipment, Fresh Produce, Coming-of-age movies)

  • User to Attributes API

    • Purpose: For a given user, return a list of attributes within your product catalog’s metadata that are relevant to that user.
    • Recommended for: category shelves (e.g. The North Face, organic, Michael Cera)
  • User to Trending API

    • Purpose: For a given user, return a ranked list of trending products that they are most likely to purchase, based on their past behavior.

    • Recommended for: “Trending Products” ribbon

  • Product to Products API

    • Purpose: For a given product, return other products that are suitable alternatives for (or complementary to) that product.

    • Recommended for: “Frequently Bought Together” ribbon, cart up-selling, cart cross-selling, email marketing campaigns

Implementing Personalized Recommendations using APIs

Basic Usage

Although there are several different APIs that utilize Miso’s Recommendation Engine, they all have a similar call pattern. In this example, we’ll use the User to Products API, but the instructions for calling the other APIs can be found in our API documentation.

As we mentioned in the previous section, the User to Products API returns a rank-sorted list of recommended products for the given user, based on their historical and real-time behaviors with your site. To call the User to Products API, we simply need to provide the user_id or anonymous_id of the customer in the request body:

POST /v1/recommendation/user_to_products
{
    "anonymous_id": "visitor-123"
}

This API will respond with the recommended products for the specified user:

{
  "message": "success",
  "data": {
    "took": 37,
    "miso_id": "517452b0-0ccf-11eb-948d-66359cf29022",
    "products": [
      {
        "product_id": "tmdb-475557",
        "_personalization_score": 0.91
      },
      {
        "product_id": "tmdb-299534",
        "_personalization_score": 0.89
      },
      ...
    ]
  }
}

If it seems too simple, that’s because it is! Our APIs are designed to be implemented as effortlessly as possible, but robust enough to handle any customizations or fine-tuning necessary for your business. We’ll discuss how to do that in the next section.

Customizing Personalized Recommendations using Recipes

As we discussed in the previous section, implementing a Recommendation API is very straightforward, and only requires a single parameter (the user_id or product_id) to get started. However, there are many additional parameters that can be added to the request body for more advanced recommendation feeds.

All these features can be integrated to provide comprehensive product recommendations. Recipes are a great way to familiarize yourself with how Miso’s Recommendation Engine can be leveraged on your site. Here are some recipes to get started:

Additional Resources

For more information on Miso’s Recommendation API, check out the official API Documentation.

For more recipes like this, visit the Recipes page on our Docs site.

Published Date: April 15th, 2022

Icon/Activity Icon/Add Icon/API Icon/Arrow/Down Icon/Arrow/Left Icon/Arrow/Right Icon/Arrow/TopRight Icon/Arrow/Up Icon/Bento Icon/Billing Icon/Bin Icon/Book Icon/Bookmark/Default Icon/Bookmark/Filled Icon/Calendar Icon/Caret/Down Icon/Caret/Up Icon/Chavron/DownIcon/Chavron/LeftIcon/Chavron/RightIcon/Chavron/UpIcon/Checknox/CheckedIcon/Checknox/Unchecked Icon/Checklist Icon/Chip Icon/Clipboard / Copied Icon/Clipboard/Default Icon/Clock/Stopwatch Icon/CMD Icon/Data/Catalog Icon/Data/Engine Icon/Data/Group Icon/Data/Interact Icon/Data/Users Icon/Dive Icon/Docs/Key Icon/Dojo Icon/Email Icon/Env/Development Icon/Env/Playground Icon/Env/Prod Icon/Folder Icon/Fullscreen/Collapse Icon/Fullscreen/Expand Icon/Guides/Multiple Icon/Guides/Single Icon/Hashtag Icon/Heart/Outline Icon/Heart/Solid Icon / Cart z Icon / Click Icon / Clock Icon / Data Icon / Doc Icon / EmptyCart z Icon/Social/Facebook Icon / Genome Incognito Icon / Money Icon/Social/ProductHunt Icon / Search Icon/Social/Twitter Icon / User Icon/Info/Error Icon/Info/Info Icon/Info/Question Icon/Info/Warning Icon/Interact/Download Icon/Interact/Edit Icon/Interact/External v2 Icon/Interact/External Icon/Interact/Filter Icon/Interact/Logout Icon/Interact/Options Icon/Interact/Re-order Icon/Interact/Reload Icon/Interact/Remove Icon/Interact/Replace Icon/Interact/Search Icon/Interact/Shuffle Icon/Interact/Undo Icon/Interact/Upload Icon/Interact/Video Icon/Invoice Icon/Loading Icon/Loading Icon/Lock/Locked Icon/Lock/Unlocked Icon/Lock Icon/Mapping Menu Icon/Notification Icon/Overview Icon/Person/Team Icon/Person/User Icon/Plan/Enterprise Icon/Plan/Growth Icon/Plan/Startup Icon/Plan/Trial Icon/Recipe Icon/Rocket Icon/Settings/App Icon/Settings/User Icon/Settings Icon/Shrine Icon/Sidebar/Close Icon/Sidebar/Open Icon/Slideout Icon/Sort/Ascending Icon/Sort/Default Icon/Sort/Descending Icon/Star/Filled Icon/Star/Outlined Stopwatch Icon/Support Icon/Tag Icon/Interact/Thumb/Dislike Icon/Interact/Thumb/Like Icon/Tick Icon/Trend/New Icon/Trend/Trending Icon/Tutorial Icon/Lock/Unlocked Icon/View/Grid Icon/View/List Icon/Watchlist/Add