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.