The VWO client class needs to be instantiated as an instance that exposes various API methods like activate, getVariationName and track.
Each VWO client represents the state of a project corresponding to the settingsFile. SettingsFile needs to be fetched before instantiating a VWO client. Read more on how to get SettingsFile.
SDK provides a method to instantiate a VWO client as an instance. The method accepts an object to configure the VWO client.
The only required parameter for instantiating the SDK is settings file. There are other optional parameters, which you could provide for overriding the default behavior or setting environment.
Below is the list of all parameters that can be used for configuring the VWO SDK.
|Object||Override default logger behaviour. Customise log-level, and implement your own log message.|
|Object||The JSON representing the User Campaign Data Map. Used for sticky bucketing and deciding when to call Activate API vs. getVariationName API.|
|Boolean||Flag for experimenting the SDK on test-app/staging so that no impression is sent to the VWO server for tracking.|
|Class||Fetched settings file|
|Object||For passing integrations callback, logging configuration, batching of events configuration. etc.|
An instance of the VWO class, which can be referenced later for calling out different API methods.
require 'vwo' vwo_client_instance = VWO.new(config['account_id'], config['sdk_key'], nil, nil, false, nil)
Updated 10 months ago