Identify the logging endpoint used by a snippet

1. In your web browser, visit a page where the snippet is implemented.

2. Open the developer console.

3. Select the Network tab.

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

5. 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

• 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.

• 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 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 web interface.