SmartBridge1. Check your site and access
The current package targets Optimizely CMS 12.22.1 or later in the CMS 12 series and Commerce Connect 14.44.1 or later in the Commerce 14 series, on .NET 8. It is not a connector for Optimizely Configured Commerce.
Start on a test site. Your developer installs the packages and prepares the database; the guided screens then handle connections and supported field mappings.
- An inriver SaaS tenant with its REST API URL and an API key.
- An Optimizely catalog with the product and variant fields you want to populate.
- Your Azure OpenAI endpoint, deployment name and key for AI mapping suggestions.
- The languages and shop hostnames you plan to use.
2. Install SmartBridge in your Optimizely site
Add the connector and admin packages to the web project, using the package source configured for your SmartBridge release. Install matching versions of both packages.
Register the SmartBridge services and prepare its SQL tables as described in the developer reference below. If the site cannot create tables, your database administrator can run the SQL script supplied with the package. Restart the site and open SmartBridge from the CMS menu.
dotnet add package SmartBridge.Optimizely.InriverConnector
dotnet add package SmartBridge.Optimizely.Ui3. Create and save a test key
Create an account in the customer portal, verify your email and choose Test key. Add the hostnames for your shop and its test environments. The test key is valid for 60 days from issue and does not require a payment card.
Copy the key from My licenses into SmartBridge → License in Optimizely. Check that the License screen allows sync for the site. Keep the key private.
4. Connect inriver and choose what to sync
Open Setup and enter the inriver API connection. Test it before continuing, then connect your Azure OpenAI service for mapping suggestions. Choose the channel, destination catalog, product and variant types, and languages.
The connector copies products, variants, categories, relationships, attributes, images and documents. Price and stock updates remain with your existing systems. Product data moves between your inriver tenant and your Optimizely site; AI suggestions use field names and types.
5. Review the field mappings
AI proposes connections to review. You can also pick or drag an inriver field onto a shop field. The editor identifies compatible connections and shows when conversion settings are needed.
Preview the examples loaded from inriver. Check number formats, list values and languages before choosing Use for sync. A preview reads sample data without writing to your catalog. The field mapping guide explains conversions in more detail.
6. Run the first sync and inspect the result
Run the first sync from the guided setup and inspect the result on Home. Open representative products and variants in Commerce: check their languages, categories, text, images and documents.
Later runs fetch changes since the previous completed run and retry failed items. This is scheduled synchronization, not an instant event-driven feed. Choose a schedule appropriate for your catalog size and update frequency.
If something needs attention
Read the specific error on Home and correct the connection or value. Recovery lets you preview values, retry selected items and request a full re-check. An interrupted run can replay work, so verify that restarting the job produces the expected catalog state.
Before using a live shop, test representative data and failure recovery on your own environment. Setup time and throughput depend on your catalog, its mappings and the host site.