Event batching for the C# SDK

The Optimizely Feature Experimentation C# SDK batches decision and conversion events into a single payload before sending it to Optimizely. This is achieved through a new SDK component called the event processor.

Event batching can reduce the number of outbound requests to Optimizely Feature Experimentation depending on how you define, configure, and use the event processor. It means less network traffic for the same number of Impression and conversion events tracked.

In the C# SDK, BatchEventProcessor provides the implementation of the EventProcessor interface and batches events. You can control batching based on two parameters:

• Batch size: Defines the number of events that are batched together before sending to Optimizely Feature Experimentation.
• Flush interval: Defines the amount of time after which any batched events should be sent to Optimizely Feature Experimentation.

An event consisting of the batched payload is sent as soon as the batch size reaches the specified limit or the flush interval reaches the specified time limit. BatchEventProcessor options are described in more detail below.

📘

Note

Event batching works with both out-of-the-box and custom event dispatchers.

The event batching process does not remove any personally identifiable information (PII) from events. You must still ensure that you are not sending any unnecessary PII to Optimizely Feature Experimentation.

Basic example

using OptimizelySDK;

public static class Program
{
   public static void Main(string[] args)
    {
        var sdkKey = args[0];
        
        // Returns Optimizely Client
        OptimizelyFactory.NewDefaultInstance(sdkKey);
    }
}

By default, the batch size is 10 and the flush interval is 30 seconds.

Advanced Example

using OptimizelySDK;
using OptimizelySDK.Config;
using OptimizelySDK.Event;

public static class Program
{
    public static void Main(string[] args)
    {
        var sdkKey = args[0];
        
        var projectConfigManager = HttpProjectConfigManager.Builder()
            .WithSdkKey(sdkKey)
            .Build();

        var batchEventProcessor = new BatchEventProcessor.Builder()
            .WithMaxBatchSize(10)
            .WithFlushInterval(TimeSpan.FromSeconds(30))
            .Build();

        var optimizely = new Optimizely(
            configManager: projectConfigManager,
            // ... Other parameters
            eventProcessor: batchEventProcessor
        );
    }
}

BatchEventProcessor

BatchEventProcessor is an implementation of EventProcessor where events are batched. The class maintains a single consumer thread that pulls events off of the BlockingCollection and buffers them for either a configured batch size or a maximum duration before the resulting LogEvent is sent to the EventDispatcher and NotificationCenter.

The following properties can be used to customize the BatchEventProcessor configuration using the Builder class

For more information, see Initialize SDK.

Side effects

The table lists other Optimizely Feature Experimentation functionality that may be triggered by using this class.

Registering LogEvent listener

To register a LogEvent listener:

NotificationCenter.AddNotification(
    NotificationCenter.NotificationType.LogEvent, 
    new NotificationCenter.LogEventCallback((logevent) => {
        // Your code here
    })
);

LogEvent

LogEvent object gets created using EventFactory.It represents the batch of decision and conversion events we send to the Optimizely Feature Experimentation backend.

Dispose Optimizely Feature Experimentation on application exit

If you enable event batching, you must call the Close method (optimizely.Dispose()) before exiting. This ensures that queued events are flushed as soon as possible to avoid data loss.

❗

Warning

Because the Optimizely Feature Experimentation client maintains a buffer of queued events, you must call Dispose() on the instance before shutting down your application or whenever dereferencing the instance.