Page tree

Before using PubMatic APIs, first generate the API Token. For more information, refer to  Getting Started with PubMatic APIs .  
Note: This document supports a set of APIs for older integrations.

PubMatic’s performance requires that total latency should be within 130 milliseconds 30 ms for connection establishment and100ms for bid response. If either of these independent thresholds are exceeded (connection and bid response time) during the transaction the bid is considered a ‘timeout’.

For better performance Demand Partners should support HTTP 1.1 and enable the following features:

PubMatic reuses pre-established (persistent) connections wherever possible.  This practice saves connection establishment time to reduce latency.

Data Center

PubMatic can send API Requests from servers located in following locations.

  1. US West Coast – PubMatic - (Ping IP Address)
  2. US East Coast – PubMatic - (Ping IP Address)
  3. Amsterdam, Europe – PubMatic - (Ping IP Address)
  4. Singapore – Amazon AWS - (Ping IP Address)
  5. Tokyo, Japan – Amazon AWS - (Ping IP Address)

Distribution of impressions based on data centers:                                                                                       


Impression Source% Distribution of Impressions to Each PubMatic Data Center
Western USUS West Coast – 100%
Central USUS West Coast – 66% and US East Coast – 34%
Eastern USUS East Coast – 100%
Western EUAmsterdam – 100%
Central EUAmsterdam – 100%
Eastern EUAmsterdam – 100%
JapanTokyo – 100%
Asia (except Japan)US West Coast – 94% and Singapore – 6%
Rest of the WorldAmsterdam – 50% and US West Coast – 50%

KeepAliveTimeOuts Recommendations

PubMatic uses persistent connections in order to minimize the time required for RTB Request/Response. Hence there will be significant number of open connections to Demand Partner’s system. Demand Partner’s should set KeepAliveTimeOut in the range of 3 to 5 minutes in order to minimize open connections.

⇧ Top