Rules

1

Rules Overview
Rules is a feature that allows you to pick specific queries, and fully tailor the results to show for them.

This can be used for specific use-cases that require you to always show a certain set of results, like when customers search for “mystery box” and you want to associate a particular product, category and explanatory blog post.

Target Query #

Searches can be configured to either apply when a query matches exactly, like a search for “mystery box”, when the query simply contains the chosen word(s) like “best mystery box adventures” or to manipulate the Omnisearch empty state before the user types a query.

...

FAQ

1

Running into issues with your custom integration? This FAQ covers the most common problems and their solutions, from single-page apps to tracking sales.

Single-page apps #

These are also called Progressive Web Apps (PWA) and generally load the site as a single page, rather than loading individual pages as normal.

When a page is loaded for the first time, the Clerk.js library automatically fires a function to render all Element blocks on that page.

...

FAQ

1

Product Data Uses #

Clerk.io relies heavily on product data to understand the structure of your catalogue. Below are the various uses that your product attributes have in Clerk.io’s AI.

Any texts that are sent for each product, will be indexed as keywords for that product.

This means that the more attributes you can send ( colors, sizes, brands, model-numbers, descriptions etc .), the better the search engine can become and the more it will be able to help your customers find the right products.

...

Redirects

1

Redirects in my.clerk.io

Redirects allows you to create a direct connection between a query or keyword and a specific url. When can you use it?

For example, you have a stand-alone product for one category, and you want to make it possible for your costumers to directly search for the product page from the search, without passing by the search page.

This guide will be divided into two sections. The first one is to show you how to create a Redirect for your store and the second part the additional steps you will have to follow if you have a custom API store.

...

Configuration

1

Search configuration

Search comes with several settings that allow you to adjust its behavior.

When you change a setting, it triggers an analysis of your data that must complete before changes take effect.

This process can take up to 15 minutes but may be faster depending on the size of your catalogue. You can monitor the status in Data > Configuration.

The settings require Search 3.0 to be enabled. Afterwards, you can access them in Search > Configuration.

...

FAQ

1

Hide Category slider #

When a Clerk.io Recommendation is added to a category page that contains a low amount of products, it will show the same products on the page.

To avoid this, you can hide the Recommendation on category pages, by adding an if statement to the Recommendation design code.

Change the number in the if statement to the minimum amount of products needed to show the Recommendation.

{% if products.length > 7 %}
 
 <!-- Recommendation code -->

{% endif %}

E.g.:

...

FAQ

1

This code is meant to be a starting point that can be tailored to your needs.

Many browsers support voice search natively, making it fairly straightforward for developers to implement into Clerk.io’s search features.

Below is an example script that can be used to transcribe text using a microphone. Specifically, it will insert text into Clerk.io’s Omnisearch input field.

It adds a button that, when clicked, triggers the browser’s voice recognition API and inserts the text into the input field.

...