Facets are the filter options shown to visitors on product listing pages and search result pages. Examples include color, size, brand, price range, and in-stock status. They help shoppers quickly narrow down their choices and find relevant items faster.
What distinguishes Elevate in terms of facets is the extensive customization it offers. As a retailer, you can tailor filters to align with the complexity and structure of your catalogs, resulting in faster, more relevant experiences — and ultimately, higher conversion rates and customer satisfaction. This article covers how facets are defined and how they appear in your e-commerce store.
Where do facets come from?
Facets are built from product attributes in your product feed. This includes:
- Standard fields like size, color, and price
- Custom attributes you've added to support your business logic
To work with a facet in Elevate, the corresponding attribute must be present in your product feed. Ensure your feed includes all relevant data you want to expose as facets. Refer to the Admin API documentation for detailed steps on importing and formatting your product feed.
How to set up a facet
Facet settings can be managed at different levels. You can use the same facet configuration everywhere, create regional variations, or customize how facets are used on individual pages using overrides.
1. Create a facet from an attribute
Facets are created and managed in the Facet configurator, located under Experience > Pages > Settings > Facet Settings. This is the source of truth for all available facets — here you can see and manage properties such as display type, sort order, and units. These settings are universal and apply to all markets. Learn more in the Facet configurator article.
2. Define the default settings for each market
Once a facet has been added, you can configure local facet settings for each market. These settings apply to all pages with a primary product list and the search results page. Go to Experience > Pages > Settings > Default settings, then scroll down to Primary product list where you'll find the Facets settings. Read more in the Settings article.
3. Overrides
The default settings apply to search results pages and primary product lists, but you can override them manually:
Override search result pages
Go to Experience > Pages > Settings > Auto-complete & Search settings > Search Result Page > Override Facets. This overrides default facets for search results only. Use it to provide more relevant filters based on user intent.
Override primary product list on local pages
Go to Experience > Pages > Category & Landing pages, open the specific page, and select List settings > Override facets. Use this to fine-tune product visibility based on local preferences.
Overrides can also be applied within Default Settings at the individual facet level — for example, to change the sort order of values for a specific facet. You can restore facet overrides to default values here as well.
When used, overrides take precedence in their specific context — allowing for flexibility while maintaining overall consistency.
Facet templates
If you have several landing pages that should use the same facet logic, Facet templates are a better alternative than setting up overrides on each page individually. Read more in the dedicated Facet templates article.
Facet types & properties
If you need an attribute added or want to change how properties are set up in the product feed, ask your integrator for assistance. Full configuration options are available in the Schema Documentation in the API docs.
When communicating with your integrator or developer, it helps to understand how facet types work. A facet type in Voyado Elevate refers to the format or behavior of a product filter, based on the data attribute it represents. Different types determine how a filter is displayed and interacted with on the frontend — for example, whether it's a checkbox, a color swatch, or a range slider.
| Type | Display As | Sort | Unit | Attributes |
|---|---|---|---|---|
| Boolean | Checkbox | n/a | n/a | in stock |
| Measurement | Range | n/a | mm, cm, dm, m, in, ft, yd, ml, cl, dl, l, oz, gal, mg, g, hg, kg, lb | length, width, height, depth, volume, weight, customLengths |
| Value | Values | Alphabetic, Relevance | n/a | brand, department, pattern, name, series, gender, age, customLabels |
| Range | Range | n/a | n/a | price, items, rating, customNumbers |
| Color | Color | n/a | n/a | color (for example, red, blue, green) |
| Size | Size | Alphabetic | n/a | size (for example, S, M, L, 36, 38, 40) with automatic size cleaning |
Integration
For detailed guidance, refer to the API documentation, which covers key topics such as:
- On-site visibility
- Storefront API integration
- Preview and testing
- Implementation examples