Data Compression (gzip)
Edited

ConnectAd supports JSON and Compressed JSON (gzip) as data formats for bid requests and bid responses. It is recommended to use Compressed JSON to minimize the amount of data exchanged between you and ConnectAd as this reduces latency times between servers, and traffic listening costs for all parties involved.

+) There is no tangible extra CPU load due to compressing/decompressing traffic, i.e. there is no extra cost
+) When enabled, gzip compression ratios tend to be in the range of x1.4 to x2.0 (depending on the size of the request/response)

You can enable this on your integration at any time.

In order to set up Compressed JSON bid requests and accept compressed responses, use the following instructions:

1.) Compress your HTTP request body with gzip
2.) Add a Content-Encoding: gzip HTTP header to indicate that the request is compressed
3.) Add an Accept-Encoding: gzip header to indicate that you can accept a compressed response

Once set up, ConnectAd starts accepting bid requests in Compressed JSON and responds using compressed JSON. All such bid responses carry a Content-Encoding: gzip HTTP header indicating that the response is compressed. It is recommended that you check for this HTTP header to distinguish between JSON and Compressed JSON bid response formats if it is present decompress the HTTP body before further processing.