A connector is an interface that connects your application to external/third-parrty providers. Adding the Optimizely connector to your application will allow you to connect an existing Optimizely account to your application and will allow you set up and run experiments on your pages

Note: Before Adding

To use the Node Optimizely Connector v1.0 you will have to deploy the Optimizely Retail Server Extension to your Retail Server. The extension will expose a new endpoint on your Retail Server which the Node connector will use to fetch the list of experiments

Read here for detailed documentation on the Optimizely Retail Server Extension.

Future versions (v2.0) and greater of the optimizely-connector requires your Retail Server version to be 10.0.14 or greater and corresponding retail-server-proxy to be 9.24.2 or greater.

Setting up your Connector Settings

The connector requires the following config information in connector.settings.json (found under src/settings)

1. sdkKey: A sdkKey is a key associated with an environment in the project to instantiate a client. This information is requried.

2. refreshTime: refresh time controls the update interval of the Optimizely SDK how often to poll for the latest changes made to your features is measured in seconds. The refreshTime should match the cache settings provided for the datafile to keep your server and client instances in sync.

3. projectId: The project id of your Optimizely project

4. oun: The operating unit number of the online store. This is used to retrieve the opttimizely access token from the Key Vault.

Provisioning an Optimizely API Access Token in Retail Server

Along with configuring the above in your connector.settings.json you will also need to create a secret key with the name 'OptimizelyAccessToken' in your Retail Server keyvault. The value should be a valid Optimizely personal API access token, that can make requests to the project id being used.