With the Event API you can send event data from any application without using our native Web snippet, Full Stack SDKs or Full Stack Agent. There are many reasons why you may need to do this. Here are some examples from Optimizely developers who are using the API today:
- Offline conversions: You're collecting offline experiment data, such as phone call conversions tracked by third-party software. You'd need to store this information locally until the Internet connection is restored. Our SDKs currently don't have this feature built-in.
- Security: You're working on a restricted environment and aren't allowed to load third-party Web snippets or install third-party SDKs or services. You'd 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'd 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're building a custom Optimizely integration or extension. (Read the Integrations and Extensions sections of the Dev Docs for more information.)
To use the event API, follow the getting started guide.
Optimizely uses this API internally
We "consume" our own API: the Optimizely clients and SDKs send event data with this API. This consistency helps ensure that your data is processed the same way, regardless of how we receive it.
Updated about a year ago