> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/data-attributes.md).

# Data attributes

Switch search fields on or off, check their type and set how strongly they count for the order of results.

In the **Data attributes** area you see which product fields the search knows and how strongly each field counts for the order of results. Here you switch individual fields off or correct their type. Only active fields are available afterwards in the "Filters" area.

<figure><img src="https://923488348-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FebcjSiStaIxyVJ83vjsL%2Fuploads%2Fgit-blob-a40f8b15b39b6ea9f326fb11bbd81047a3213e80%2Fsuche-intelligent-und-ki-optimiert-datenattribute.png?alt=media" alt="Data attributes area with filters, core fields, type, weighting and active switch per field"><figcaption></figcaption></figure>

You create new fields from your shop under "Edit data fields". After the next "Re-import product data" they appear here.

## Layout

At the top you choose the **data source**. The first one is preselected. Next to it are "Edit data fields" (for an external feed, a note says its fields cannot be edited here instead) and "Refresh list". If the source is still empty, it says "No data attributes have been found for this data source yet."

### Search, counter and filter buttons

* In the "Search" field you find fields by technical name, readable name or type.
* The counter shows how many fields are active, for example "18 of 25 fields active".
* The filter buttons each show a count: "All", "Active", "Inactive", "Search weight set" and "Check type". Buttons without results are hidden.
* If nothing matches, it says "No fields match search and filter."

{% content-ref url="/pages/gwPJIHZL0Lc3ekLkAsPI" %}
[Edit data fields](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/feed-template-editor.md)
{% endcontent-ref %}

### Groups

The fields are in collapsible groups with a counter such as "12 of 15 active". While you search or filter, all groups are expanded.

| Group                        | Content                                                                                                  |
| ---------------------------- | -------------------------------------------------------------------------------------------------------- |
| Core fields                  | Name, price, brand, categories, availability. Every feed or push delivers these fields.                  |
| Properties and custom fields | Properties such as color or size and custom fields of your shop, ideal for filters and search weighting. |
| AI fields                    | Created by InsightSearch, for example product type or image features.                                    |

### Columns

Each row shows the readable name (bold) with the technical key below it, the **type**, the **weighting**, the **Active** switch and an action menu (...). Inactive rows are dimmed. The Active switch takes effect immediately and reports "Attribute was activated." or "Attribute was deactivated." The info icon next to "Type" and "Weighting" shows a short help.

## The action menu

In the menu (...) of each row you find:

1. **Edit search weight** (only with the add-on, see below)
2. **Change type**
3. **Deactivate** or **Activate**

## Edit search weight

The search weighting sets how strongly hits in a field count. The higher the number, the higher hits in this field rank. For example, a hit in the "Brand" field should count more than a hit in the description.

The "Edit data attribute" dialog shows "Field name" and "Type" read only. In the "Search weight" field you enter a whole number from 0. There is no upper limit in the interface. "Save" applies the change ("The data attribute was updated.").

{% hint style="info" %}
**Add-on "Individual search weighting":** Without this add-on the search uses a standard weighting for all fields. The action "Edit search weight (add-on)" is then grayed out, and a banner with the "More details" button appears at the top. It opens the purchase dialog of the extension in Shopware.
{% endhint %}

## Change type

The type determines how the search treats a field. In the "Change data attribute type" dialog you see the "Current type" and choose the "New type". "Save" only becomes active once you changed the type.

| Type in the selection                           | Purpose                                     | Example       |
| ----------------------------------------------- | ------------------------------------------- | ------------- |
| Text (text)                                     | Full-text search with partial matches.      | Description   |
| Selection value (exact) (keyword)               | Exact value, for filters with fixed values. | Brand, color  |
| Number (integer), Number (long), Number (float) | Numbers for range filters such as sliders.  | Price, weight |
| Yes/No (boolean)                                | Switch.                                     |               |
| Date (date)                                     | Time ranges.                                |               |

For numbers there are three entries for different kinds of numbers. "Number (float)" usually stands for decimal numbers, "Number (integer)" and "Number (long)" for whole numbers.

After saving, "Type was saved." appears with the note to re-import the product data.

### The "Check type" mark

A yellow "Check type" label appears if a field is stored as Yes/No but its name suggests a number, for example "price", "weight", "width", "amount" or "count". Range filters such as "from 20" then do not work. Change the type to a number and re-import the product data. With the "Check type" filter button you see all affected fields at once.

## When do changes take effect?

Changes to active status, type and search weight only take effect after you re-import the product data. After a change the note "You changed fields. For the change to take effect, re-import the product data once." appears with the "Re-import product data" button, which starts the import of the selected source directly.

{% hint style="warning" %}
Only active fields are available afterwards in the "Filters" area as filter attributes. If a field is missing there, activate it here and re-import the product data.
{% endhint %}

## Further reading

{% content-ref url="/pages/gwPJIHZL0Lc3ekLkAsPI" %}
[Edit data fields](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/feed-template-editor.md)
{% endcontent-ref %}

{% content-ref url="/pages/YEBvytB69E4Y4qAMmqvE" %}
[Filters](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/filters.md)
{% endcontent-ref %}

{% content-ref url="/pages/UKhMX3Zla832boJXFREa" %}
[Sources](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/indices.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/data-attributes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
