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.
Description
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.
Parameters
The following tables show the information provided to the listener when it is triggered:
| Parameter | Type | Description |
|---|---|---|
| log event | Log Event | Whenever 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.
| Object | Type | Description |
|---|---|---|
| http verb Required (non null) | String | The HTTP verb to use when dispatching the log event. It can be Get or Post. |
| url Required (non null) | String | URL to dispatch log event to. |
| params Required (non null) | Dict | Event Batch. It contains all the information regarding every event which is batched, including list of visitors which contains UserEvent. |
| headers | Dict | Request headers |
Examples
For example code, see the notification listener topic in your SDK language.
Updated almost 3 years ago