Jonas Bergqvist
Oct 20, 2017
(6 votes)

Using Personalized Find

Episerver recently released Personalized Find (PF), a new product that delivers improved relevancy to visitors thereby helping to increase conversions on your website. Specifically, when used with Episerver Commerce, PF uses each individual's browsing and purchase activity to boost search results.

Without personalization, everyone gets the same Find experience. Yet every visitor is different and is looking for different things on your website. Moreover, each user's behavior changes depending on their wants and needs at that time.

How Personalized Find works

Every click and action on a website is used to build a visitor's profile. For example

  • traffic source
  • search query
  • categories visited
  • selected facets: color, size, brand, and so on 
  • use of ratings and reviews 

This data is captured, analyzed then visualized to determine a personalized search relevancy. The relevancy logic for each individual is based on everything PF knows about the visitor: preferences, previous purchases, current behavioral interactions, and so on. 

Ranking and weighting can also consider a merchandiser's business rules or strategies. So, best-selling items, high conversion rates, most revenue, or most units sold can be used to affect search results. The result of this processing is an optimal ordering of search results for every user.

Benefits of Personalized Find

  • Increased sales. Optimizing the search experience has been shown to produced increased revenue.
  • Better engagement. Improved experience encourages customers to keep shopping.
  • Better conversion rates. Easier for customers to find products they are looking for.
  • Better retention. Customers who have a positive experience are more likely to return to your site.

Using Personalized Find on your site

The Developer Guider article "Using Personalized Find" provides the technical details about using PF. This post provides a quick introduction to a few PF functions.

  • Fetching site visitor information. 
    using EPiServer.Find.Personalization;
    namespace EpiserverSite.Controllers
        public class MyController : PageController<MyPage>
            private readonly IClient _client;
            public MyController(IClient client)
                _client = client;
            public ActionResult Index(MyPage currentPage)
               return View(currentPage);
  • Implementing UsingPersonalization() to boost a query with site visitor information.
    var result = _client.Search<FashionProduct>()

Note: At this time, site visitor information is only captured for Commerce content. While you can use .UsingPersonalization() on any query, it only boosts Commerce content properties.

Example of implementation

Here is an example, where a user has viewed several expensive puma products. The developers has created a recommendation ordering view, to help the visitors.

Oct 20, 2017


Magnus Eriksson
Magnus Eriksson Jan 15, 2018 02:42 PM


Any idea when Personalized FIND will be available for normal CMS content?

regards /Magnus

Alex Do
Alex Do Feb 6, 2018 08:22 AM

Hello @Maguns, what do you mean about "Normal CMS Content"? For more details about Episerver Find and how does it work, you can see here:

Best /Alex

Son Do
Son Do Apr 9, 2018 09:23 AM

Hi @Magnus,

As I read in World blog post, it means recomendation for CMS content is ready and Personalized FIND will be available for CMS content pretty soon IMO. 

Thank for your patience :)

/Son Do

Please login to comment.
Latest blogs
How Optimizely Web Experimentation enables fast validation of design and UX changes

Ever wondered how to increase conversion rates and quickly validate design/UX alternatives to find the most impactful changes? I wrote a practical...

Jacob Pretorius | Jan 31, 2023

What’s next after Google Optimize’s sunsetting?

Google has announced that it is sunsetting the Google Optimize and Optimize 360 services, forcing customers to explore new platforms and invest in...

Ynze | Jan 31, 2023 | Syndicated blog

What’s next after Google Optimize’s sunsetting?

Google has announced that it is sunsetting the Google Optimize and Optimize 360 services, forcing customers to explore new platforms and invest in...

Ynze | Jan 31, 2023 | Syndicated blog

Migrating from Providers to CMS 12 ASP.NET Identity with cookie tweaks

Notes on migrating a multi-site from Membership and Role Providers to ASP.NET Identity and changing cookie options dynamically.

Johan Kronberg | Jan 30, 2023 | Syndicated blog

Integrating generative AI in Optimizely CMS: A quick test with OpenAI

Some of the new AI services have received a lot of attention recently. Can you integrate them in Optimizely CMS? Of course, you can!

Tomas Hensrud Gulla | Jan 30, 2023 | Syndicated blog

When best practice isn't the best - Dependency Injection and Optimizely CMS

Some people live and breath 'best practice' development. I am not one of them. Risk is, in-experienced developers (or sometimes experienced) might...

Allan Thraen | Jan 29, 2023 | Syndicated blog