Optimizely will be sunsetting Full Stack Experimentation on July 29, 2024. See the recommended Feature Experimentation migration timeline and documentation.

Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket
These docs are for v2.0. Click to read the latest docs for v3.0.

Event transmittal

If you work with implementations that include many integrations and external requests, you may wonder if adding Full Stack tracking will contribute to a network bottleneck.

Some Full Stack SDKs implement an asynchronous event dispatcher to prevent requests from blocking each other or forming a bottleneck. It is also possible to use an events pipeline, along which you would send events at a later date to avoid slowing down your site for visitors.


The events pipeline diagram above shows how an Optimizely customer working with a service like Amplitude might use a backend event pipeline to serve as a unified event propagation mechanism. Activate and Track HTTP requests are deferred on the server and dispatched in the browser, using a cookie to transmit the required information.