Identify which logging endpoint is used by a given Optimizely X Web snippet

Understand the benefits of the /events endpoint

Enable the /events endpoint for your account

Optimizely X Web snippets can be configured to use one of two logging endpoints: /event or /events. Snippets which use the /event endpoint generate one network request per event to be tracked, while snippets using the /events endpoint batch events together. These batches are sent once per second for the first ten seconds after snippet activation, and then immediately thereafter.

Identify the logging endpoint used by a snippet

In the Filter field, type “logx” to only display logging requests generated by the Optimizely snippet.

Select a network request and check the request URL. If the URL ends in /event, your snippet has been configured to use the /event endpoint. If the URL ends in /events, your snippet has been configured to use the /events endpoint.

Benefits of the /events endpoint

Performance

Snippets using the /events endpoint generate fewer network requests during the critical first few seconds after a page starts loading, leading to improvements in page load performance.

Snippets using the /events endpoint generate fewer network requests overall. Mobile websites can reduce their impact on data and battery consumption by reducing the number of network requests they generate.

Timing

Snippets using the /events endpoint enable the holdEvents and sendEvents APIs. These APIs provide granular control over when the snippet begins logging events. They can be used to further optimize page performance, or to more closely align Optimizely logging with third-party analytics. See this KB article for more information on these use-cases.

Enable the /events endpoint for the snippets in your account

To enable the /events endpoint for all snippets in your account, please submit a support ticket via the form in the Optimizely X web interface.