# AI Powered Search

In modern e-commerce, search is no longer limited to simple keyword matching. Users expect a search experience that **understands intent**, **interprets context**, and **delivers relevant results even when queries are incomplete, ambiguous, or informal**. **AI Powered Search** is designed to elevate the in-shop search experience by leveraging artificial intelligence to meet these expectations.

With AI Powered Search, users can:

* Enter queries with **typos or misspellings**,
* Use **synonyms or alternative expressions** instead of exact product names,
* Describe their needs using **natural, free-form language**,\
  for example: *“I’m looking for a birthday gift for my nephew”*,

and still receive **accurate and relevant product results**.\
The AI analyzes these inputs to understand the **underlying intent**, rather than relying solely on exact keyword matches.

By combining natural language understanding with product catalog data, category structures, and semantic relationships, AI Powered Search delivers results that are aligned with what the user actually wants to find.

#### <mark style="color:red;">Monitoring, Control, and Continuous Optimization</mark>

AI Powered Search is not a black-box solution. Through **Omnitron**, teams can:

* Monitor **search queries and user behavior**,
* Analyze **frequently searched terms and phrases**,
* Identify **zero-result or low-performance searches**,
* Track **conversion and engagement metrics**,
* Configure and manage **AI search plans** that influence how results are generated.

This level of visibility allows brands to:

* Measure search performance using clear metrics,
* Fine-tune AI behavior based on business goals,
* Continuously improve the overall search experience.

#### <mark style="color:red;">Scope of This Tutorial</mark>

In this tutorial, you will learn:

* How AI Powered Search works at a conceptual level,
* How user search inputs are interpreted and processed,
* Which search results are collected and how they can be analyzed,
* How AI Powered Search–related screens in Omnitron are structured,
* How to configure and manage search plans and related settings.

In the next section, we will walk through the **AI Powered Search in Omnitron**, explaining how each configuration and monitoring tool can be used to manage and optimize the search experience.

***

## <mark style="color:red;">AI Powered Search in Omnitron</mark>

Omnitron provides a set of dedicated screens to **monitor, analyze, and configure** the AI Powered Search experience. These screens allow teams to understand how users search within the shop, evaluate search performance through search results, and fine-tune AI behavior using configurable search plans and keywords.

The AI Powered Search module in Omnitron consists of **four main screens**:

* **Dashboard**
* **Search Results**
* **Keywords**
* **Search Plans**

Each screen focuses on a different aspect of the search lifecycle—from high-level visibility to detailed configuration and performance analysis.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2F6hMRhkBquWwB7tStOPby%2Fimage.png?alt=media&#x26;token=f8c5b1c2-99eb-4c56-96ac-d001e4394a54" alt=""><figcaption></figcaption></figure>

We will start with the **Dashboard**, which offers a comprehensive overview of search activity at a glance.

### <mark style="color:red;">1. Dashboard</mark>

The **Dashboard** provides a high-level summary of how AI Powered Search is being used in the shop. It is designed to give quick insights into overall search activity, trends, and user behavior without requiring deep configuration or analysis.

#### <mark style="color:red;">Key Metrics</mark>

At the top of the Dashboard, three core metrics are displayed:

<mark style="color:purple;">**Today’s Searches:**</mark> Shows the total number of searches performed in the shop today.\
This metric also includes a **percentage comparison with the previous day**, displayed as *“Compared to yesterday”*, allowing you to quickly assess daily search activity trends.

<mark style="color:purple;">**Total Keywords:**</mark> Displays the total number of **defined Keywords** that are currently configured and used by the AI Powered Search engine.

<mark style="color:purple;">**Search Plans:**</mark> Indicates the total number of **configured Search Plans**, which define how search queries are interpreted and how results are generated.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FmhWbvTXDUv6k7g89A5ip%2Fimage.png?alt=media&#x26;token=1f5c2ad1-60e7-456d-ac2b-96a128ee88f6" alt=""><figcaption></figcaption></figure>

#### <mark style="color:red;">Search Distribution</mark>

Below the top metrics, the **Distribution** chart visualizes how search activity is spread over time.\
This chart allows you to analyze search behavior at different time granularities, including:

* Monthly
* Weekly
* Daily
* Hourly

By switching between these views, you can identify peak search periods, seasonal patterns, and user activity trends throughout the day.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FfKv1Dvhw1y4taAijlmWY%2Fimage.png?alt=media&#x26;token=6f91d706-068d-4cb9-9b73-1d03405d9254" alt=""><figcaption></figcaption></figure>

#### <mark style="color:red;">Popular Searches</mark>

The **Popular Searches** table lists the **top 10 most frequently searched text queries** across the shop.\
This section helps you understand what users are actively looking for and can be used to:

* Identify high-demand products or categories,
* Detect recurring search intents,
* Inform keyword definitions and search plan optimizations.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FHAsPsMKjMnJjqAwVsbo1%2Fimage.png?alt=media&#x26;token=84224c9f-62f4-4ec9-b455-e87481fda181" alt=""><figcaption></figcaption></figure>

#### <mark style="color:red;">Language Distribution</mark>

The **Language Distribution** chart shows the languages in which users perform their searches.\
This visualization is particularly useful for multi-language shops, as it enables you to:

* Understand language-based search behavior,
* Evaluate whether search configurations are aligned with active languages,
* Identify opportunities for improving keyword coverage or AI understanding in specific languages.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FMTrF8z2dOSBYaeuUjAou%2Fimage.png?alt=media&#x26;token=9e7e611e-4fa7-44cd-85e7-9df263cb8a2a" alt=""><figcaption></figcaption></figure>

***

### <mark style="color:red;">2. Search Results</mark>

The **Search Results** page provides detailed visibility into **what users search for in the shop and how often**. Every search query entered by a user is recorded by a **scheduled task that runs once per minute**, ensuring that search activity is captured continuously and consistently.

This page is primarily used to **analyze search behavior over time**, identify high-frequency queries, and evaluate trends that can be used to improve search plans and keyword configurations.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2Fo7muSxbN07iGy4AVhnqi%2Fimage.png?alt=media&#x26;token=28bac5eb-39b1-4cee-bd24-a7c1ca23fcee" alt=""><figcaption></figcaption></figure>

#### <mark style="color:red;">Search Results Table</mark>

Each record in the Search Results table represents a **grouped view of searched text**, enriched with time-based information. The table includes the following columns:

<mark style="color:purple;">**Search Text:**</mark> The exact text entered by the user in the shop search bar.

<mark style="color:purple;">**Count:**</mark> The total number of times the search text was queried within the selected time grouping.

<mark style="color:purple;">**Time Range Start:**</mark> Indicates the **starting point of the time range** from which the displayed count is calculated.

<mark style="color:purple;">**First Search Time:**</mark> Shows the **earliest time** at which the search text was queried within the selected grouping.

#### <mark style="color:red;">Time-Based Grouping (Group by)</mark>

The values in the **Count**, **Time Range Start**, and **First Search Time** columns are directly affected by the **“Group by”** filter located in the top-right corner of the page.

The **Group by** option allows search queries to be grouped into different time intervals:

* 1 minute
* 5 minutes
* 1 hour
* 1 day
* 1 month

This grouping enables flexible analysis of search data at different time resolutions.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FKOMWyPvecd3AXbdb6aVl%2Fimage.png?alt=media&#x26;token=b4bb40a4-a6e0-4443-b6c5-42687ea49b19" alt=""><figcaption></figcaption></figure>

**Example:**&#x20;

If the search text **“milk”** is grouped by **1 Hour**, the Search Results table will show:

* How many times *“milk”* was searched during that hour (**Count**),
* The first time it was searched within that hour (**First Search Time**),
* The start date of the month from which the count is calculated (**Time Range Start**).

By changing the grouping level, the same search text can be analyzed minute-by-minute, hourly, daily, or monthly.

#### <mark style="color:red;">Filtering and Sorting</mark>

The Search Results page also supports **advanced filtering and sorting** to help you focus on specific data points:

* **Filters** can be applied to narrow down search results based on search text and other available criteria.
* **Sorting options** in the table allow you to order records by:
  * **Count** (ascending or descending),
  * **Time-related fields** (ascending or descending).

***

### <mark style="color:red;">3. Keywords</mark>

The **Keywords** page is used to **convert real user search behavior into structured search intelligence**. Its main purpose is to transform the **search texts collected on the Search Results page** into reusable and configurable **Keywords** that can be leveraged by AI Powered Search and Search Plans.

By defining keywords based on actual user searches—such as misspellings, alternative expressions, or commonly used phrases—you can guide the AI to better understand user intent and return more relevant results.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FqyQPyZexdPeS8qxxyqO0%2Fimage.png?alt=media&#x26;token=42c95a79-c3ba-4f64-8de5-c810f45f3f22" alt=""><figcaption></figcaption></figure>

#### <mark style="color:red;">Creating a New Keyword</mark>

To create a new keyword, click the **+ Add New Keyword** button located in the top-right corner of the page. This action opens the keyword creation form.

**Keyword Form Fields:**

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2Fzh6DSm1KMtmsOhW3mPK5%2Fimage.png?alt=media&#x26;token=85858484-547d-482d-9d5e-13e94839b76b" alt=""><figcaption></figcaption></figure>

<mark style="color:purple;">**Keyword:**</mark> This field contains the keyword text itself. Typically, this value is derived from the **Search Results** page and may represent:

* A frequently searched term,
* A misspelled word,
* A commonly used alternative expression.

**Example:** Users may search for *“garden furniture”*, *“garden chair”*, or similar variations. These frequently searched texts can be selected from the Search Results page and defined as keywords.

They may also enter misspelled queries such as *“gardan furnitre”* or *“garden furnitur”*, or use synonyms like *“outdoor furniture”* instead of *“garden furniture”*.

By defining these variations as keywords, AI Powered Search can return relevant results even when users use different wording or make spelling mistakes.

<mark style="color:purple;">**Language:**</mark> Specifies the language in which the keyword is defined. This ensures that the keyword is evaluated correctly within multi-language search scenarios.

<mark style="color:purple;">**Type:**</mark> Determines how the keyword interacts with other keywords and search plans.

There are two available types:

**1) Normal**

* The keyword is evaluated independently.
* It is matched directly against search plans that explicitly include it.
* Suitable for specific, well-defined terms with limited contextual variation.

**2) Contextual**

* The keyword can be **combined with multiple other keywords**.
* The AI establishes a **contextual relationship** between this keyword and others that appear together in search queries.
* Especially useful for **generic or commonly reused terms**.

**Example:** *Consider* the keyword **“garden furniture”**:

* *There* may already be keywords related to **“garden”** and **“furniture”**.
* Separate search plans might exist for garden-related products and furniture-related products.

When **Contextual** is selected:

* The AI can associate this keyword with both garden-related and furniture-related search plans.
* Searches such as:
  * “garden lighting”
  * “garden soil”
  * “garden chair” \
    can still take this keyword into account.
* Similarly, for furniture-related searches, variations such as:
  * *“bathroom furniture”*
  * *“kitchen furniture”*
  * *“baby furniture”*\
    can also be evaluated using contextual relationships.

In this way, **Contextual keywords enable the AI to find relevant search plans for derived or combined search queries**, even when those exact combinations were not explicitly defined.

<mark style="color:purple;">**Term Quantity:**</mark> Represents the number of terms (words) that make up the keyword.

For example:

* *“*&#x66;urnitur&#x65;*”* → 1 term
* *“*&#x67;arden furnitur&#x65;*”* → 2 terms

This information helps the AI better interpret keyword structure and relevance.

#### <mark style="color:red;">Keyword List</mark>

Once keywords are created, they are listed in the Keywords table. In addition to the properties defined during creation, the table includes an additional column:

* **Search Plans:** Indicates **how many Search Plans currently include this keyword**.

This column helps you understand:

* The impact scope of a keyword,
* How widely it is used across search configurations,
* Whether a keyword is actively contributing to search logic or still unused.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FMfyw1BDDWvgBiFApQWDb%2Fimage.png?alt=media&#x26;token=a2b8c30d-5247-4bc0-9809-826204d394a7" alt=""><figcaption></figcaption></figure>

***

### <mark style="color:red;">4. Search Plans</mark>

The **Search Plans** page is where **keywords are turned into actionable search logic**. Using the keywords defined on the **Keywords** page, Search Plans determine **how a user’s search input is interpreted**, which query is executed, and which filters are applied to generate the final product results.

In short:

* **Keywords** represent *what users type*,
* **Search Plans** define *how the system searches*.

Search Plans can be created **manually by users** or **automatically by AI** based on real search behavior.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FXiu0PdcE9IsYWMozekA5%2Fimage.png?alt=media&#x26;token=60a6a717-53af-49fd-9a99-aa0309afbdba" alt=""><figcaption></figcaption></figure>

#### <mark style="color:red;">Creating a Search Plan</mark>

To create a new search plan, click the **+ Add Search Plan** button in the top-right corner of the page. This opens the Search Plan creation form.

**Search Plan Form Fields:**

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FXaS8pthhtqpTIRBadB18%2Fimage.png?alt=media&#x26;token=9060765b-6810-4484-9534-d4977292e07d" alt=""><figcaption></figcaption></figure>

<mark style="color:purple;">**Keyword:**</mark> Select one of the keywords defined on the **Keywords** page. The keyword can be searched and selected from the list.

This keyword acts as the **trigger** for the search plan.

<mark style="color:purple;">**Search Query:**</mark> Defines the **actual query** that will be executed when the selected keyword is detected.

This field can be populated in two different ways:

* **Manually**, by entering the desired search query directly.
* **Automatically using&#x20;*****Create with AI***, which analyzes the selected keyword and generates:
  * An appropriate **Search Query**, and
  * Relevant **Filters** based on the detected intent.

The Search Query typically represents the **corrected, normalized, or intended version** of the keyword.

**Examples:**

* Keyword: *“gadrn”* → Search Query: *“garden”*
* Keyword: *“gardenfurniture”* → Search Query: *“garden furniture”*
* Keyword: *“hoodie”* → Search Query: *“sweatshirt”*

The goal is to ensure that variations, typos, or alternative expressions are mapped to a clean and meaningful search query.

*<mark style="color:red;">**AI-Generated Search Plans (Create with AI):**</mark>* When **Create with AI** is used, the AI does more than generate the search query. It also **automatically adds filters** to the search plan by analyzing the structure and intent of the keyword.

**Example:** If a user searches for *“Black M T-Shirt”*, the AI may:

* Identify **“black”** as a color,
* Identify **“M”** as a size,
* Identify **“T-Shirt”** as a product category,

and automatically generate a search plan that includes:

* A filter for the **color attribute** with the value *“black”*,
* A filter for the **size attribute** with the value *“M”*,
* A filter for the **T-Shirt category**.

Search plans created using this method are listed with **Mode = AI** in the Search Plan List.

*<mark style="color:red;">**Manually Created Search Plans:**</mark>* If the Search Query and filters are **entered manually via the form**, the search plan is considered user-defined and is listed with:

* **Mode = Human**

<mark style="color:purple;">**Priority:**</mark> Determines the **execution priority** of the search plan.

When multiple search plans match the same user query, the plan with the **higher priority** is applied first. This allows you to control which logic takes precedence in overlapping scenarios.

<mark style="color:purple;">**Filters:**</mark> Filters allow you to **extend or refine search results** by applying additional constraints based on attributes or categories.

Each filter consists of:

* **Filter Key**
* **Filter Value**

These filters are applied alongside the search plan to produce more accurate results.

**Examples:**

* If the search query is *“garden”*, a filter can be added to search within the garden category by specifying the category key and value.
* If the Search Query is *“red shoes”*:
  * A filter can be added for the color attribute with the value *“red”*,
  * Another filter can target the shoes category.

## <mark style="color:red;">Conclusion</mark>

With the combination of **Search Results**, **Keywords**, and **Search Plans**, AI Powered Search in Omnitron provides a complete and controllable search optimization framework.

* **Search Results** enable you to observe real user behavior by tracking every search query over time.
* **Keywords** transform these raw search texts into structured signals that the AI can understand, including misspellings, synonyms, and contextual terms.
* **Search Plans** convert keywords into actionable search logic, defining how queries are executed, which filters are applied, and which results are prioritized—either manually by users or automatically by AI.

This layered approach ensures that:

* Users receive relevant results even when they make spelling mistakes, use different wording, or express intent in natural language.
* Search behavior is measurable through clear metrics.
* AI-driven decisions remain transparent, configurable, and aligned with business goals.

By continuously monitoring metrics, refining keywords, and optimizing search plans, teams can **iteratively improve the shop’s search experience**, increase discoverability, and ultimately drive higher engagement and conversion rates.

AI Powered Search in Omnitron is not just a smarter search—it is a **search system that learns, adapts, and evolves** with your users.