Settings

In Commerce Studio’s settings, you can configure what the Editor displays for each search profile. Some of these settings require the names of data fields in Fusion, but you can type to search for the fields you need. In your site on Lucidworks Platform, navigate to Commerce Studio > Settings to access these settings. Start by selecting a search profile to configure. Search profiles represent different predefined search results that you can display on different pages of your customer-facing site, such as new items, seasonal items, sale items, and so on. You might also have experimental search profiles for testing different configurations. The configuration you create here determines how the item cards are displayed in the Editor when the same search profile is selected.

​

Configure Search Results

In the Search Results section, you can configure the fields displayed for each result item in the Editor. Once you configure these settings, you can turn different display fields on or off while you’re working in the Editor using its Preview Settings.

​

Layout

The Layout section lets you select to display search results in a vertical list or a grid pattern. Select the option you want, click Save, and then verify the list displays on the Editor screen. This demo explains the Layout options and how each displays search results.

​

Fields Style

Under Fields Style, you can select and format the fields that the preview cards display in the Editor.

• To add a field, click the button.
• To change a field, click the field and type to search for another one.
• To change a field’s display style, click the dropdown and select the style that best matches the field’s data type.

​

Variants

When you enable Variants, you can select the fields that contain data about different variants of your products. To enable product grouping in Commerce Studio, follow the procedure for your configuration.

​

Inline Analytics

When you configure and use the signals beacon and Analytics Studio to collect and display signal information, you can also enable Inline Analytics in Commerce Studio Settings, which lets you select the metrics to display in Commerce Studio Editor search results cards.

Enable Commerce Studio Impressions metrics

To enable metrics to display in Commerce Studio, complete the following steps:

1. Navigate to Inline Analytics and click the toggle on.
   IMPORTANT: This setting is required to display the Metrics option in Commerce Studio Editor Preview Settings. If the toggle is off, you cannot display any metrics on search results cards in Commerce Studio Editor.

   

2. Select a default option in the Metrics Duration field. This is the default duration for the Commerce Studio Editor Preview Settings Metrics section. Options include Last Hour, Last 24 Hours, Last 7 Days, Last 30 Days, and Last Year.
   The timeframe selected in the Metrics Duration field is the default. But you can override this duration by selecting a different timeframe in Commerce Studio Editor Preview Settings Metrics.
3. In the Document ID Field, enter the name of the search result document field used as the document ID when retrieving metrics from the Signals Store. The default is id.
   This is the Solr field that corresponds to the product identifier that your signals beacon logs for each item. The default value of id matches the Solr uniqueKey for most catalogs. However, use the value your catalog uses. Another example of the value used is sku_s.
   This value is used to calculate the search result’s Impressions, ATC, Orders, Sales, RPV, and CVR data on the result card.
   If the Document ID Field doesn’t match what your signals beacon records as the product identifier, the metrics cannot be calculated and a -- placeholder displays on the result card.
4. Optionally, if you want to build a preview of how metrics display on the search result card before you deploy it in Commerce Studio Editor, you can select the metrics checkboxes for Impressions, Add-To-Cart (ATC), Orders, Sales, Revenue Per Visit (RPV), and Conversion Rate (CVR). In this example, all of the checkboxes except Impressions are checked, and the Settings Preview Result Card indicates how that displays:
   
   
   IMPORTANT: When you select these options, they only display on the Preview result card in Commerce Studio Settings. To select metrics to display on search result cards in Commerce Studio Editor, you must navigate to Commerce Studio Editor > Preview Settings > Metrics and select metrics options. For detailed information, see Commerce Studio Editor Impressions metrics.

​

Category

The Category field you select is the name of the Fusion Solr field that contains indexed values you use to categorize search results. The Solr field is populated during Fusion indexing using the connector field mapping or an index pipeline stage configured with Field Mapping, JSON, or Script. The field name can be any Solr field such as title_s or category_s. For a Solr field with multiple values, the field has a ss at the end. For example, title_ss or categories_ss. The category values indexed in this field can be selected in the Commerce Studio Editor Conditions Manager, and apply to all of the following Editor features:

• Display category-specific results to users
• Mark specific rules that apply to that category and not the entire site
• Display search metrics for only the selected category

Guidelines and best practices for categories

These are the guidelines and best practices to consider when selecting the Solr field to use.

• Use a dedicated string field that is a stable canonical value that reflects a category ID or a normalized breadcrumb path. Do not use a raw display label, an analyzed text field, or a free-text field. The Commerce Studio Editor’s Category condition entered in the Condition Manager matches the literal indexed value, so exact matching is required. For example, in a B2B organization, category names may be updated to match procurement terminology or regulatory standards, so the underlying IDs should remain stable even when display labels change.
• The field must be multivalued if items can belong to more than one category, for example, categories_ss. For example, a B2C product like a wool running jacket might belong to Running, Outerwear, and Sale simultaneously. In a B2B organization, a part might appear under both a product-type tree and an industry-application tree. And a knowledge article might be tagged under both a department and a content type.
  IMPORTANT: A single-valued field drops secondary category assignments, breaking both rules and facet counts.
• In the Facet Fields section of the query pipeline, add the field to make category-level filtering available to users and drive Commerce Studio’s per-category product-performance metrics.
• For hierarchical categories where documents belong to a multi-level taxonomy, you need rules and facets to work at any level of that tree. For example, Electronics > Computers > Laptops. For this type of multi-level taxonomy, use a depth-prefix convention on a multivalued ancestor-path field, indexing each level as a separate value:
  • 0/Electronics
  • 1/Electronics/Computers
  • 2/Electronics/Computers/Laptops
  This lets Solr use facet prefix queries to retrieve only nodes at a given depth, and enables breadcrumb navigation and parent-child drill-down in your UI. Rules scoped to a parent node, such as Electronics, automatically apply to all child nodes.

Configure a Fusion pipeline for categories

To configure a Fusion pipeline with categories that can be used in Commerce Studio, complete the following steps:

1

Add depth-prefixed values

In your index pipeline, add a JavaScript Index Stage or Field Mapper to generate the depth-prefixed values and write them to a multivalued string field. For example, category_path_ss.

2

Add leaf-level category

Add a second field for the leaf-level category for rules that target only the most specific node. For example, category_leaf_s.

3

Set facet field

Set category_path_ss as a facet field in your query pipeline in the Field Facet stage.

4

Set tree depth

In your query pipeline, set the facet.prefix parameter to {depth}/ to retrieve only one level of the tree at a time. For example, 1/.

5

Add optional companion field

Optionally, add a companion field such as category_parents_ss, listing only non-leaf nodes. When a facet value displays in this field, your UI renders an expand control. Otherwise it renders a leaf link, avoiding extra Solr round-trips.

Configure categories in Commerce Studio

To configure categories used in Commerce Studio, complete the following steps:

1. In the Category field, select the identified Fusion Solr field name.
   This setting is per search profile. If you have multiple search profiles, configure the category field for each one that serves category pages.
   
2. Verify the values in the Examples section reflect the values you need for categories.
   When you select a value in the Category field, Commerce Studio accesses that Solr field using the read-only introspection endpoints granted to the lwp_user and lwp_service_account roles, and retrieves a sampling of values for the Examples field. It doesn’t retrieve all of the field values.For the values that display in the Commerce Studio Editor screen, see Use category conditions.

​

Configure typeahead

Typeahead, also known as autocomplete or autosuggest, is a feature that provides real-time query and phrase suggestions as you type in the Editor’s search bar. In the Typeahead section, you can configure the fields to use for typeahead for this search profile.

• To add a field, click the button.
• To change a field, click the field and type to search for another one.
• To change a field’s display style, click the dropdown and select the style that best matches the field’s data type.