LogoLogo
  • Overview
  • What Ads Can Project Agora Commerce Serve?
  • Integration
    • API Introduction
    • Integration Workflow
      • Integration Summary
      • Integration Steps
    • Ad Proposal file
    • Syncing Data
      • Syncing Data Via File Protocols
    • Syncing Catalog & Products
      • Syncing Catalog and Products Via File
    • Syncing Order Data
      • Syncing Multiple Orders
    • Reporting Clicks and Impressions
  • INTEGRATION GUIDES
    • HTTP Persistence & Ad Caching
    • Reference
    • Requesting Ads (the "Context" and its Parts)
    • Product Listing Ad Integration Guide
      • Requesting a Category Product Ad
      • Requesting a Search Term Product Ad
    • Discovery Product Listing Ad Integration Guide
      • Requesting a Discovery Product Ad
    • Banner Ad Integration Guide
      • Banner Ad Content Standard
      • Requesting a Search Term Banner Ad
      • Requesting a Category Banner Ad
      • Requesting a Middle Home Page Banner Ad
      • Requesting a Top Home Banner Ad
      • Requesting an Ingrid Banner Ad
      • The Post Checkout Banner Ad Context
      • Graceful Fallback in the Event That No Ads Are Displayed
Powered by GitBook
On this page
  • HTTP Persistence Guide
  • Ad Caching Guide
Export as PDF
  1. INTEGRATION GUIDES

HTTP Persistence & Ad Caching

PreviousReporting Clicks and ImpressionsNextReference

Last updated 1 year ago

HTTP Persistence Guide

Project Agora Commerce requires a persistent HTTP connection in order to speedily respond to Ad Generation requests. 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) in order for you to receive Project Agora's Ad services at the intended speed.

Every TLS handshake that is generated has a cost, and the more TLS handshakes that are established, the more expensive is the transfer of data from Project Agora Commerce to your E-commerce website.

Maintaining a persistent HTTP connection avoids congestion and improves HTTP response times.

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

Ad Caching Guide

Ads returned from Ad Generation Endpoints regardless of adtype cannot be cached.

Every time a page is loaded on a retailer's website, a new ad generation request should be sent to Project Agora Commerce with the correct context, to generate a fresh set of ads.

https://en.wikipedia.org/wiki/HTTP_persistent_connection
https://tools.ietf.org/html/rfc7230#section-6.4