> 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/shopware6/fact-finder-web-components-for-shopware-6/configure-the-plugin.md). # Configure the plugin Configure FACT-Finder connections, exports, uploads, imports, and category pages. ### Main settings Configure **Server URL**, **Channel**, and **API key**. The server URL needs a protocol and FACT-Finder endpoint, such as `https://example.com/fact-finder`. Configure Channel per sales channel. Save before testing the connection. Clear the store cache after changes. ### Field roles Use **Update Field Roles** after changing FACT-Finder column names or when using a custom feed. The update covers every sales channel. Default roles map `brand` to `Manufacturer`, `deeplink` to `Deeplink`, `imageUrl` to `ImageUrl`, `price` to `Price`, and product names and numbers to their matching columns. Override `factfinder.field_roles` in your application `services.xml`. ### Advanced settings Enable **Use Proxy** only when server-side response processing is needed. Requests then pass through `ProxyController`. Subscribe to `EnrichProxyDataEvent` to enrich the response. This adds HTTP and Shopware processing to every request. Use **Add cart button** for product lists. Define one `query=url` redirect mapping per row. The first matching query wins. URLs may be relative or absolute. Atlas AI support creates a persistent Atlas AI user ID. It replaces previous logged-in `userId` values. Enable SSR to pre-render `ff-record-list` on category and search pages. This improves crawler access to products. The single-result product redirect requires SSR. It does not run for client-side Web Components searches. **Disable FACT-Finder Web Components** works per sales channel. Never assign FACT-Finder category pages to disabled channels. ### Export, upload, and import Ignore selected product properties and custom fields during exports. Configuration properties of variants remain exported. Enable all-currency prices to create columns named `Price_`, such as `Price_De`. Configure FTP or SFTP with protocol, host, port, credentials, and root directory. The default port is `21`. Private-key content and passphrases are optional SFTP authentication values. For automatic FACT-Finder imports, enter dashboard credentials and choose Suggest, Search, and/or Recommendation. These credentials only start imports. Automatic export is disabled by default. Choose a sales channel and language to enable it. It runs every 48 hours by default through Shopware Scheduled Tasks. Override `ExportScheduledTask::getDefaultInterval()` to change the interval in seconds. ### Category pages Shopping Experiences provides **Search Result**, **Campaigns**, and **Filters** blocks. Search Result contains record list, ASN, filter cloud, pagination, and sort box. Campaigns supports feedback text, advisor, redirect, and pushed products. Use LandingPage layouts. CategoryPage validation still requires a default Product Listing block. Find all components under **Commerce**. Elements support **Subscribe**, **ID**, and a **Dom Updated** listener. ASN also supports a vertical layout. Campaign settings configure labels, flags, redirects, and pushed products. Extend block templates from `Resources/views/storefront/block` and element templates from `Resources/views/storefront/element` with `sw_extends`. Assign the completed layout to intended categories. The default category field is `CategoryPath`. Override `factfinder.navigation.category_path_field_name` in `services.xml` when your FACT-Finder category field differs. --- # 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/shopware6/fact-finder-web-components-for-shopware-6/configure-the-plugin.md?ask=&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.