> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/magento/sdk-v5.x/backend-configuration.md).

# Backend configuration

After activating the module, open **Stores → Configuration → Catalog → FACT-Finder**. Configure the FACT-Finder connection, web components, and export settings there.

## Main settings

Enter the shop connection and authorization details. Activate the integration, then select **Save Config**. You may need to clear the cache through **System → Cache Management → Flush Magento Cache**. Select **Test Connection** to verify connectivity.

> The channel name, server URL, and API key must be correct.

You can enable FACT-Finder category-page rendering here. See [using FACT-Finder on category pages](https://github.com/FACT-Finder-Web-Components/magento2-module/tree/release/5.x#using-fact-finder-on-category-pages).

**Show 'Add to Cart' Button in Search Results** adds a cart button to search-result products. It works only for simple products. Configurable products redirect to the product page. The feature identifies products through `MasterProductNumber`. Import that field to the FACT-Finder backend.

**Activate Logging** saves communication exceptions to `var/log/factfinder.log`. This affects server-side communication only.

[![Main Settings](https://github.com/FACT-Finder-Web-Components/magento2-module/raw/release/5.x/docs/assets/general-settings.png)](https://github.com/FACT-Finder-Web-Components/magento2-module/blob/release/5.x/docs/assets/general-settings.png)

### FACT-Finder version

Version 5 supports only the `NG` FACT-Finder version. For earlier versions, use the [4.x SDK](https://github.com/FACT-Finder-Web-Components/magento2-module/tree/release/4.x).

### Server-side rendering

This option enables server-side rendering for `ff-record-list` on category and search-result pages. Pre-rendered product content improves crawler visibility. The module uses [Handlebars PHP](https://github.com/salesforce/handlebars-php) for template processing.

See the Web Components [server-side rendering guide](https://web-components.fact-finder.de/documentation/5.x/server-side-rendering).

## Advanced settings

[![Advanced Settings](https://github.com/FACT-Finder-Web-Components/magento2-module/raw/release/5.x/docs/assets/advanced-settings.png)](https://github.com/FACT-Finder-Web-Components/magento2-module/blob/release/5.x/docs/assets/advanced-settings.png)

Advanced Settings holds additional Web Components parameters. Each setting has a default value and explanatory text.

**Atlas AI support** handles Atlas AI requirements automatically. It creates and persists a dedicated Atlas AI user ID. Enabling it overwrites existing logged-in user IDs.

### Currency and country settings

No module-specific currency or country setting is required. The module passes the active store values to `factfinder init` as `currency-code` and `currency-country-code`.

* [Configure currency](https://docs.magento.com/m2/ce/user_guide/stores/currency-configuration.html)
* [Configure country](https://docs.magento.com/m2/ce/user_guide/stores/country-options.html)

## Optional custom elements

[![Optional Custom Elements](https://github.com/FACT-Finder-Web-Components/magento2-module/raw/release/5.x/docs/assets/optional-custom-elements.png)](https://github.com/FACT-Finder-Web-Components/magento2-module/blob/release/5.x/docs/assets/optional-custom-elements.png)

Some custom elements require additional FACT-Finder modules. Disable those elements when you do not use the related functionality.

Feedback campaigns support only the **above search result** label. Paging is redundant when `ff-record-list` uses infinite scrolling. Landing-page campaign IDs use the Magento CMS page identifier.

## Custom elements options

[![Custom Elements Options](https://github.com/FACT-Finder-Web-Components/magento2-module/raw/release/5.x/docs/assets/custom-elements-options.png)](https://github.com/FACT-Finder-Web-Components/magento2-module/blob/release/5.x/docs/assets/custom-elements-options.png)

Configure element-specific attributes here. The module passes stored values into their matching templates.

## Export settings

[![Product Data Export](https://github.com/FACT-Finder-Web-Components/magento2-module/raw/release/5.x/docs/assets/export-settings.png)](https://github.com/FACT-Finder-Web-Components/magento2-module/blob/release/5.x/docs/assets/export-settings.png)

Choose whether attributes export as individual fields or a multi-attribute field. **Multi-Attribute: No** adds attributes to `FilterAttribute`. **Yes** exports separate columns.

Supported attribute types:

* boolean, price, select, and multiselect
* all scalar values

### Numerical attributes

A numerical multi-attribute exports to the `NumericalAttributes` column. This simplifies FACT-Finder filter configuration. Configurable attributes always export to `FilterAttributes`.

## CMS export settings

You can export CMS pages for suggest results.

[![CMS Export Settings](https://github.com/FACT-Finder-Web-Components/magento2-module/raw/release/5.x/docs/assets/cms-settings.png)](https://github.com/FACT-Finder-Web-Components/magento2-module/blob/release/5.x/docs/assets/cms-settings.png)

**Pages Blacklist** excludes pages from export. Use it for pages such as `404 Not Found`.

Contact your assigned FACT-Finder representative or Service Desk to start using CMS export. CMS export is available only through a console command.

## Data transfer settings

Configure FTP or SFTP connections here. The module generates and transfers shop data to FACT-Finder. FTP uses a username and password. SFTP supports a key or password.

Magento's uploader requires key files to have an extension. Add one, such as `.rsa`, when needed. Enter a key passphrase when the key is protected.

Enter the upload server, then select **Test Upload connection**. The generated CSV uses double quotes (`"`) as its enclosure and semicolons (`;`) as delimiters.

Before selecting *Generate Export File(s) now*, select **Save Config**. **Test Connection** always uses the fields' current values.

[![Data Transfer Settings](https://github.com/FACT-Finder-Web-Components/magento2-module/raw/release/5.x/docs/assets/data-transfer-settings.png)](https://github.com/FACT-Finder-Web-Components/magento2-module/blob/release/5.x/docs/assets/data-transfer-settings.png)

### Updating field roles

When field roles change in FACT-Finder, update the Magento tracking values with **Update Field Roles**.

### Automatic import

After uploading a feed, FACT-Finder must import it. Enable automatic import to trigger that step after each upload. Choose one or more data types:

* Search
* Suggest
* Recommendation


---

# 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.fact-finder.com/magento/sdk-v5.x/backend-configuration.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.