Send and receive compressed traffic using gzip

You can receive bid requests and send bid responses that are compressed using gzip. By using bid compression, DSPs can see a 20-30% reduction in bandwidth utilization which may contribute to lower latency, infrastructure costs, and fewer timeouts. To enable bid compression with Index, contact your Index Representative. To start sending and receiving compressed traffic using gzip:

Number 1 icon

By default, Index adds an Accept-Encoding: gzip HTTP header to the bid request An OpenRTB request that is sent from a supply-side platform (SSP) or ad exchange to the DSP requesting a bid response for potential impressions. A bid request contains information about the impression that allows the DSP to decide whether to bid on the impression. to specify that we accept compressed bid responses from DSPs.

Note: To opt-out of receiving the Accept-Encoding: gzip field for bid requests, contact your Index Representative.

Number 2 icon

If you have enabled bid compression, Index adds a Content-Encoding: gzip HTTP header to the bid request to specify that it is a compressed request.

Number 3 icon

You can send a compressed gzip bid response An OpenRTB response that is sent by the DSP in response to the SSP's or ad exchange's bid request. It is an event directed back to the seller expressing a valuation for the request and conditions of sale. to Index by including the following required fields in the HTTP header:

  • Content-Encoding: gzip : Specifies that you have sent a compressed bid response.
  • Content-Length header: Specifies the response size. For more information on the Content-Length field, see the HTTP header fields in the List of supported OpenRTB bid response fields for DSPs.