Send events with the Optimizely Event API

With the Event API, you can send event data from any application without using the native Web Experimentation snippet, Feature Experimentation SDKs, or Optimizely Agent. There are several reasons you might use the Event API directly. The following examples are from developers who are using the Event API today:

• Offline conversions – You are collecting offline experiment data, such as phone call conversions tracked by third-party software. You would need to store this information locally until the Internet connection is restored. The Optimizely Experimentation SDKs do not currently support offline data storage.
• Security – You are working in a restricted environment and are not allowed to load third-party Web snippets or install third-party SDKs or services. You would need to develop your own method of tracking events and sending them to Optimizely.
• Third-party sources – You want to combine data from third-party sources with your event data. You would need to combine the data before sending it to Optimizely.
• Communication control – You want your application to have extra control over how events are batched and when they are sent to Optimizely.
• Integrations and extensions – You are building a custom Optimizely integration or extension. See the following developer documentation:
  • Web Experimentation – Integrations and Extensions.
  • Feature Experimentation – Integrations with Feature Experimentation.

To use the Optimizely Event API, follow the Get started guide or see the Event API Reference.

📘

Note

Optimizely Experimentation uses this API internally — the clients and SDKs send event data through it too. This means your data is processed the same way regardless of how it is received.