Configure the C# SDK event dispatcher

2 min

The Optimizely Feature Experimentation SDKs make HTTP requests for every decision event or conversion event that gets triggered. Each SDK has a built-in event dispatcher for handling these events, but you should overriding it based on the specifics of your environment.

The C# SDK has an out-of-the-box asynchronous dispatcher. You should customizing the event dispatcher you use in production to ensure that you queue and send events in a manner that scales to the volumes handled by your application. Customizing the event dispatcher lets you take advantage of features like batching, which makes it easier to handle large event volumes efficiently or to implement retry logic when a request fails. You can build your dispatcher from scratch or start with the provided dispatcher.

The examples show that to customize the event dispatcher, initialize the Optimizely client (or manager) with an event dispatcher instance.

using OptimizelySDK;
using OptimizelySDK.Event.Dispatcher;
using OptimizelySDK.Logger;

var datafile = "YOUR_JSON_DATAFILE";

var optimizely = new Optimizely(
    datafile: datafile,
    eventDispatcher: new DefaultEventDispatcher(new DefaultLogger()));

The event dispatcher should implement a DispatchEvent function, which takes in a LogEvent argument created by the internal EventFactory class. In this function, you should send a POST request to the given endpoint URL using the event payload as the body of the request (be sure to stringify it to JSON) and {content-type: 'application/json'} in the headers.

Important If you are using a custom event dispatcher, do not modify the event payload returned from Optimizely. Modifying this payload will alter your results.