Optimizely will be sunsetting Full Stack Experimentation on July 29, 2024. See the recommended Feature Experimentation migration timeline and documentation.

Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideLegal TermsGitHubNuGetDev CommunitySubmit a ticketLog In

Log event notification listener

This topic describes the LOGEVENT notification listener which lets you know what data was sent to Optimizely in a given event batch and when the batch was sent.


The LOGEVENT notification listener is similar to the TRACK notification listener, but provides more granularity. It lets you know what data was sent to Optimizely in a given event batch and when the batch was sent. For more information about event batching, see the corresponding topic for your SDK language. You can use this notification listener to inspect and audit what data you are sending to Optimizely.


The following tables show the information provided to the listener when it is triggered:

log eventLog EventWhenever the event processor produces a batch of events, a LogEvent object will be created using the EventFactory.
It contains batch of conversion and impression events. For more information, see the following table.

Log Event

The Log Event object is created using EventFactory. It represents the batch of impression and conversion events that have been passed to the Event Dispatcher to be sent to the Optimizely backend.

http verb
Required (non null)
StringThe HTTP verb to use when dispatching the log event. It can be Get or Post.
Required (non null)
StringURL to dispatch log event to.
Required (non null)
DictEvent Batch. It contains all the information regarding every event which is batched, including list of visitors which contains UserEvent.
headersDictRequest headers


For example code, see the notification listener topic in your SDK language.