Skip to main content
Each of these platforms has an adapter that loads the recommendation widget and feeds it context from the storefront: the product a page shows, the category being listed, the search term, the basket, the signed-in customer and the completed order. The adapters load the widget and describe what the visitor is looking at. They also report completed orders when the platform exposes a stable order id; the BigCommerce script may not find one on every checkout theme. The adapter preview packages are publicly downloadable for staging evaluation. The Magento ZIP also has a dedicated release.
On Shopify? Use the app instead — it covers the same ground with theme and checkout extensions.

​
Magento 2

Download the Magento Composer ZIP into a directory outside your Magento project, then:
Then connect the store:
1

Connect

In Magento Admin, open Stores → Configuration → NeuronSearchLab → Recommendations and select Connect to NeuronSearchLab (or run bin/magento neuronsearchlab:connect). This creates the store’s NeuronSearchLab workspace and embed key, switches the storefront integration on, and sends the catalogue. You need no NSL account to connect.
2

Wait for the import

Recommendations appear on home, product, category, search and cart pages once the catalogue is imported, usually within a few minutes. The connection panel shows how many products are being recommended.
3

Open the console

Select Open NeuronSearchLab console in the connection panel, then sign in or create a free account. The store’s workspace is added to your account, where you configure placements, rules and analytics.
The catalogue syncs every hour through Magento cron, and on demand with Sync catalogue now or bin/magento neuronsearchlab:catalogue:sync. Each sync sends enabled, visible products with their URL, image, price, categories and stock; products that are disabled, hidden, deleted or out of stock stop being recommended. The module sends the catalogue rather than NSL fetching it, so staging and development stores work the same way. A connected store starts on the free plan. The Magento guide covers cache, theme and checkout checks, and disconnecting. Place a strip by adding the block to any layout handle:

​
Shopware 6

Download the Shopware ZIP and extract NeuronSearchLabRecommendations. Copy the plugin into custom/plugins/, then:
Set the key in the plugin’s configuration. Place a strip anywhere in Twig:

​
PrestaShop 1.7 and 8

Download the PrestaShop ZIP. Upload the module under Modules → Module Manager, install it, and paste your embed key in its configuration. SKUs come from the product reference, falling back to the product id where reference is empty, as it is in many catalogues.

​
WooCommerce

Download nsl-woocommerce.zip, upload it under Plugins → Add New, and activate it alongside WooCommerce. In WooCommerce → Settings → Products → General, enter a publishable embed key and allow the storefront origin in the NSL console. Classic product and cart templates receive automatic placements; custom pages can use the [nsl_recommendations] shortcode. Import the catalogue separately. Browser checkout and block-theme receipt flows still need staging verification.

​
BigCommerce

BigCommerce gives an app no template hook, so this adapter is a storefront script rather than a plugin. Paste it under Settings → Advanced → Script Manager, in the header, on all pages, with your key filled in. Download the BigCommerce ZIP and copy the script inside it. It reads the basket and the order from BigCommerce’s Storefront API, which is same-origin and unauthenticated, so there is no API account to create and no token in the page. Two limits are worth knowing before you install it:
  • Categories come from the breadcrumb. BigCommerce category URLs carry no marker, and nothing else is reliable across themes. Where a theme has no breadcrumb, no category is sent.
  • The order id is not in a consistent place. The script looks in the query string, session storage and the URL path. If none of them has it, the sale is not reported, because a sale that cannot be keyed would be counted again on the next page reload.

​
What every adapter sends

These are your own identifiers throughout. A SKU is resolved against your catalogue server-side, so there is no id mapping to maintain.

​
Conversions

Orders from an adapter arrive as the order_reported signal, bound to a zero-weight event, because a browser cannot prove a sale took place. They are used for attribution. Every adapter reports the same signals — product views, basket additions, recommendation impressions and clicks, and orders — and they land on the event types created when you made your embed key. A Magento order and a Shopware order are therefore the same event, whatever either platform calls it. See Events for the full list and how to point a signal at an event you already track. The Shopify order connector can reconcile a verified order against the pixel’s report when their canonical order ids match. Verified server-side order connectors for Magento, Shopware, PrestaShop and BigCommerce are not yet provided by these adapters; do not use browser-reported orders as a verified sales ledger.
These adapters have not completed the full merchant checkout and cache-isolation acceptance matrix on live staging stores. Some install and runtime paths pass against disposable platform builds in CI. Adobe Marketplace manual QA and marketing review for Magento are pending; until then, install Magento from the GitHub release above.