Launch
The Wingify client class needs to be instantiated as an instance that exposes various API methods like activate, getVariationName and track.
Each Wingify client represents the state of a project corresponding to the settingsFile. SettingsFile needs to be fetched before instantiating a Wingify client. Read more on how to get SettingsFile.
API Description
SDK provides a method to instantiate a Wingify client as an instance. The method accepts an object to configure the Wingify 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.
Parameter Definitions
Below is the list of all parameters that can be used for configuring the Wingify SDK.
| Parameter | Type | Description |
|---|---|---|
| logging Optional | Object | Override default logger behaviour. Customise log-level, and implement your own log message. |
| user_storage_service Optional | Object | The JSON representing the User Campaign Data Map. Used for sticky bucketing and deciding when to call Activate API vs. getVariationName API. |
| is_development_mode Optional | Boolean | Flag for experimenting the SDK on test-app/staging so that no impression is sent to the Wingify server for tracking. |
| settings_file Optional | Class | Fetched settings file |
| options Optional | Object | For passing integrations callback, logging configuration, batching of events configuration. etc. |
Returns
An instance of the Wingify class, which can be referenced later for calling out different API methods.
Usage
require 'vwo'
vwo_client_instance = VWO.new(config['account_id'], config['sdk_key'], nil, nil, false, nil)Updated about 1 month ago