Product Finders are not a standard Searchspring Product offering. Talk to your Customer Success Manager to discuss adding this feature to your plan.
Product Finders are a tool to help your shoppers quickly find the products they are looking for - think of it as a way to easily navigate into a more narrow, filtered Product Results set. Commonly implemented as a set of Attribute drop-down selectors, these Finders can exist on your Home Page, globally across the Header of your website, or even on a single Category Page or Landing Page.
Basic Product Finder
The most basic version of a Product Finder allows the shopper to choose their options in any order. The options of each drop-down selector would be populated by any individual Filter Attribute Field found in your core Product Feed.
Hierarchy Product Finder
A more advanced version to a Product Finder would force the shopper to select their options in sequential order. The most common example of this would be for Vehicle Finders, forcing shoppers to select a Year > Make > Model in that order before hitting a Results page. The options for a Hierarchy Finder would be sourced from a single Attribute Field, though following a specific data pattern.
To achieve a Hierarchy Finder, your Attribute Data must exist in as a single field, following a hierarchical format. Consider the Year>Make>Model Vehicle Fitment examples list below:
1967>Ford>Mustang
2006>Chevy>Malibu
2013>Chrysler>300The paths within this attribute field will determine the path selections of our Hierarchy Finder. If you want your shoppers to instead select in a Make>Model>Year order, then that's the order in which to provide your data: Ford>Mustang>1697
If a product has multiple applicable Hierarchy Paths, you must include all of those assignments within one field, separated by some delimiter such as a Pipe "|" - consider a Product that has multiple applicable Vehicle Fitments:
2009>Chevrolet>Traverse|2010>Chevrolet>Traverse|2011>Chevrolet>Traverse|2012>Chevrolet>Traverse|2013>Chevrolet>Traverse|2009>GMC>Acadia|2010>GMC>Acadia|2011>GMC>Acadia|2012>GMC>Acadia|2011>Honda>Accord|2012>Honda>Accord|2013>Honda>Accord|2014>Honda>AccordWith Vehicle Fitment data, rather than listing each Year individually, you can use a Year Range on each applicable Make>Model combination - we would then expand this out into individual Year Options within the Finder selections for you:2009-2013>Chevrolet>Traverse|2009-2012>GMC>Acadia|2012-2014>Honda>Accord
You are not required to use ">" to split the Path Levels, nor required to use "|" as the Path Separator. However, the delimiters you choose must be consistent and must not be found within the Path assignment itself. For example, with a Vehicle Fitment of 1978
GMC C/K Pickup 1500, you would not be able to use "/" to separate the Year/Make/Model since the Model value itself contains a slash character already.
Comments
0 comments
Please sign in to leave a comment.