Backend configuration
Backend configuration
Once activated, open Extensions → Modules → FactFinder Web Components | Omikron Data Quality GmbH → Settings.
Main settings
This section contains the configuration required for the module. Web Components and server-side communication use these values.
Server URL — The FactFinder instance URL. Include a protocol, such as
https://, and end withfact-finder.Channel — The channel that provides data. Configure one channel for every active application language.
Username for the FACT-Finder Import — Your account username. Required for automatic imports.
Password for the FACT-Finder Import — Your account password.
FACT-Finder API key — Used to fetch FactFinder data. Required for Web Components.
Buttons
Update Field Roles
Update field roles after changing them in FactFinder. By default, they match module-exported columns. If you rename a role column, such as Master or ProductNumber, update the roles.
Export Feed
Export a feed manually. See Export methods for details.
Test Connection
Verify your FACT-Finder API key and the SDK connection. This test uses form data, so you do not need to save first. It uses the de channel value.
Test FTP Connection
Test whether your shop can connect to the configured FTP/SFTP server. It uses request parameters, so you do not need to save first.
Test Push Import
Verify your FACT-Finder username and password. This test uses form data, so you do not need to save first. It uses the de channel value.
Advanced settings
Anonymize User ID?— Send an anonymized user ID with tracking requests.Use Proxy— Send each Web Components request through the module controller. See Proxy.How to count single click on "Add to cart" button?— Choose how to count one Add to cart click.Send the SID as userId when user not logged in?Atlas AI support— Handles Atlas AI requirements automatically. It creates a dedicated user ID and persists it across sessions. Enabling it overwrites existing user IDs for logged-in users.Add cart button for product list— Shows Add to cart in product lists.
Server-side rendering
This setting enables server-side rendering for ff-record-list on category and search pages. The initial HTML contains pre-rendered custom elements. This improves SEO because crawlers can scan product data.
See the FactFinder Web Components documentation for server-side rendering details.
Proxy
The proxy adds an OXID controller between Web Components and FactFinder. It lets you customize requests and responses. You can enrich incoming data with EnrichProxyDataEvent or implement fallback logic.
Enable the proxy with an HTTP-server rewrite rule. OXID uses cl and fnc query parameters and does not route URL parts.
Note: Routing requests through OXID reduces performance. Enable the proxy only when needed.
Feature settings
Use FactFinder for category pages?— Uses Web Components on category pages.Category Path field name— Defaults toCategoryPath. Change it when your FactFinder instance uses another category field.Campaigns— Enables product, feedback-text, and shopping-cart campaign elements.Recommendations— Enablesff-recommendationon product pages.Similar products— Enablesff-similar-productson product pages.Pushed products— Enablesff-campaign-pushed-productson cart pages.
Category pages
The module keeps standard OXID routing to preserve category URLs and SEO. It sends custom parameters with the FactFinder search request. Opening a category page emits a search event.
Feed settings
Choose attributes to export. To export an attribute in a separate column, select it and set Multi-Attribute to No. With Multi-Attribute set to Yes, the attribute is added to FilterAttributes. Selection attributes always use FilterAttributes.
Export settings
Configure these fields to export a feed file to your FTP server:
FTP host, port, user, and password
SSL-enabled, for secure FTP connections
Automatic import of product, to import after upload
Import Data, Suggest, and Recommendation
Basic Auth user and password for HTTP exports
Log path and export-on-error behavior
Note: Automatic import requires an FTP server. Basic Auth protects HTTP exports.
Last updated
Was this helpful?





