# How search as you type works

> What search as you type does on your shop, how Releva picks and ranks the products, how filters, synonyms and blocked words change the results, how clicks are attributed and what the statistics tiles count.

Search as you type puts a panel of product results under your shop’s search box while the shopper is still typing. Releva ranks the products, builds the filters and tracks what happens next. You set it up once under **Personalization › Search As You Type**; see [Set up search as you type](https://releva.ai/documentation/guides/search-as-you-type/set-up-search-as-you-type/).

## What the shopper sees

1. The Releva snippet on your page asks Releva for the page’s configuration. When search as you type is on, a layout is chosen and the shopper is in the **treatment** group of your A/B test, the answer contains the search settings. Shoppers in the **control** group get nothing and fall back to your theme’s own search, which is what the test measures.
2. The snippet finds every element matching **CSS Selector for Search Bar**, turns the browser’s own autocomplete off and adds a hidden panel under it.
3. On each keystroke, after a 200 ms pause, the snippet sends the typed text to Releva and renders the answer with your **Search** layout. An empty box hides the panel; a click outside closes it.
4. The panel shows up to **Number of Products to Show** products and the filters you configured. A click on a filter value re-runs the search with that value selected.
5. Every product link in the panel carries `rlv_aid` and `rlv_apid` parameters. When the shopper lands on the product page, Releva records a **Product Click** and attributes later cart additions and purchases to search.

Add `?rlv_mode=debug` to any shop URL to see the panel even when the feature is off or you are in the control group.

### Rendering inside your theme

**Where to Render Results** has a second option, **Intercept the theme’s own search**. It is for platform connectors that replace the theme’s native results with Releva’s inside the theme’s own container, using **CSS Selector to Render Into**, **CSS Selector to Hide**, **Requests to Intercept**, **Search Term URL Parameter** and **Response the Theme Expects**. In this mode the snippet does not attach to the search box itself. Set it up with Releva’s integration team.

## How results are chosen

For each request Releva:

1. Removes **Blocked words** from the text and, when **Use locale defaults** is on, the common words of the page’s language (the English list for `en`, the Bulgarian list for `bg`; any other page locale falls back to the English list).
2. Expands **Synonym Pairs**: a search for one word in a pair matches products that contain any other word of the pair.
3. Searches only products that are **available** and in the page’s language. Product **name** counts most, then **categories** and attribute text such as colour, size and material, then **description** when **Include “Description” Field in Search** is on. Typing a SKU matches it directly.
4. Ranks up to 100 matches. With **Use Product Feed** on, the ranking starts from that product feed’s query for this shopper, so the order is personalized. See [How product feeds work](https://releva.ai/documentation/learn/product-feeds/how-product-feeds-work/).
5. Returns the first **Number of Products to Show** products, the total number of matches, and for every configured filter the five most common values among the matches. For **Categories** these are the five most common deepest categories. Filters with no values are left out.

Products are found by the language of the page. If your catalog is in a different language than your shop’s default locale, make sure your integration sends the page locale, or searches return nothing.

## Synonyms and blocked words

| Setting                  | What it does                                                                                          | What it does not do                                          |
| ------------------------ | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| **Custom Synonym Pairs** | Treats all words in a pair as the same word. Up to 21 pairs. Applied to searches as soon as you save. | Does not change product names or rank one word over another. |
| **Use locale defaults**  | Drops stop words (“the”, “a”, “and”) in English or Bulgarian from the query.                          | Not available for other locales.                             |
| **Blocked words**        | Drops the listed words from the query before searching.                                               | Does not hide products that contain the word.                |

## Turning it on and off

* The first time you open the page there are no settings. Turning the switch on creates them with defaults (6 products, description on, no filters) and goes live immediately. **Set up without turning it on** creates the same defaults switched off, so you can configure everything first.
* With the switch off, settings can be edited and saved; the hint “Search is not running for shoppers” stays until you turn it on and save.
* **Save** writes every tab at once. It reads **Saved** when nothing changed.
* There is one configuration per shop. It cannot be deleted or copied.

## What the statistics count

The tiles at the top of the page cover the selected period (last 30 days by default; the date button opens presets from **1 week** to **3 months**).

| Tile               | Counts                                                                                                             | Share shown next to it |
| ------------------ | ------------------------------------------------------------------------------------------------------------------ | ---------------------- |
| **Interactions**   | Searches answered for an identified visitor. One per request, so a shopper typing “shirt” can count several times. | none                   |
| **Product Clicks** | Visits to a product page that came from the panel.                                                                 | of Interactions        |
| **Conversions**    | Add-to-cart actions attributed to search.                                                                          | of Product Clicks      |
| **Purchases**      | Purchases attributed to search.                                                                                    | of Conversions         |
| **Revenue**        | Value of those purchases in your shop’s currency.                                                                  | none                   |

A period with no data shows `0 | 0%` in every tile.

## Next steps

* [Set up search as you type](https://releva.ai/documentation/guides/search-as-you-type/set-up-search-as-you-type/): Connect Releva to your search box, choose a results layout and switch the feature on.
* [Search as you type API overview](https://releva.ai/documentation/reference/search-as-you-type/overview/): Call the search from your own front end and render the results yourself.
* [How your catalog gets into Releva](https://releva.ai/documentation/learn/catalog/how-your-catalog-gets-into-releva/): Learn how availability and locale decide which products can appear in results.
* [Events API overview](https://releva.ai/documentation/reference/events/send-search-events/): Track the searches shoppers make; this call records a search and returns no results.