HTTP persistence, ad caching & endpoints

HTTP persistence

CitrusAd requires a persistent HTTP connection. Without it, ad generation requests will take longer, and response times will be slower than desired. Ad generation requests should be made on a persistent connection and not have a new connection generated every time a new ad generation request is made to ensure you can receive CitrusAd's services at the intended speed.

Every TLS handshake generated has a cost, and the more TLS handshakes that are established, the more expensive the transfer of data is from CitrusAd to your ecommerce website. Maintaining a persistent HTTP connection avoids congestion and improves HTTP response times.

πŸ“˜

To learn more about HTTP persistent connections, please visit the following resources:

https://en.wikipedia.org/wiki/HTTP_persistent_connection

https://tools.ietf.org/html/rfc7230#section-6.4

Ad caching

Ads returned from ad generation endpoints cannot be cached, regardless of adtype. Every time a page is loaded on a retailer's website, a new ad generation request should be sent to CitrusAd with the correct context to generate a fresh set of ads.

Endpoint URL

You are free to name the endpoint connecting your e-commerce server and your e-commerce site as you wish. However, as a native ad solution, CitrusAd advises avoiding any endpoint naming structure that includes β€˜ads’.

πŸ“˜

If your endpoint contains β€˜ads’, it’s much more susceptible to ad blocking which reduces your revenue opportunities.