[null,null,["上次更新時間：2025-08-21 (世界標準時間)。"],[[["\u003cp\u003eAuthorized Buyers RTB limits the Queries Per Second (QPS) sent to bidders' servers to protect them from overload and conserve resources, with this limit configurable by a Technical Account Manager or through the Authorized Buyers API.\u003c/p\u003e\n"],["\u003cp\u003eWhen pretargeting matches surpass the set QPS limits, excess bid requests are throttled, with prioritization given to specific requests based on bidding history and Programmatic Guarantee requests.\u003c/p\u003e\n"],["\u003cp\u003eThe Callout Quota System may be less accurate with smaller volumes, potentially leading to exceeding the requested limit, particularly for limits around 1,000 QPS or less.\u003c/p\u003e\n"],["\u003cp\u003eBidders with servers in North America benefit from cross-location callout spillover, which attempts to send bid requests to another North American location if the quota is met in the initial location.\u003c/p\u003e\n"],["\u003cp\u003eAn error throttling mechanism reduces outgoing QPS when a bidder's error rate is too high due to untimely or invalid responses, independent of the quota limit, to maintain system stability.\u003c/p\u003e\n"]]],[],null,["# Callout Quota System\n\nThe Authorized Buyers Real-time Bidding system has a maximum rate of callouts,\nexpressed in Queries Per Second (QPS), that can be sent to a bidder's servers.\nPretargeting matches that exceed the limit are dropped. The limit serves the\nfollowing purposes:\n\n- Protect bidders from receiving more requests than their servers can handle.\n- Conserve Authorized Buyers resources when the bidder isn't interested in receiving all eligible callouts, for example, if the bidder is in test mode.\n\n| **Note:** Bidders use test mode to make sure the bidder endpoint responds within the deadline before it receives live traffic. The response deadline ranges from 80 to 1000 ms, depending on format and auction type; check the `BidRequest.tmax` field in the bid request for the exact value. The bidder can't win impressions in test mode, so the type of bid, such as \"no bid\", doesn't matter as long as a response is supplied.\n\nQuota limit\n-----------\n\nThe limit is configured and enforced per bidder server URL, technically per\ntrading location-URL pair. However, bidders shouldn't use the same server URL in\nmultiple trading locations. The limit can be configured by a Technical Account\nManager (TAM) or by the bidder through the [Authorized Buyers API](/authorized-buyers/apis/v1.4/accounts).\n\nWhen you change the limit through the API, the total quota for all the account's\nURLs can't exceed the total quota configured internally by the TAM.\n\nThe maximum quota limit for your bidder also depends on your recent spend. Your\neffective quota limit before error throttling is the minimum of the configured\nquota and spend-based quota. You can view your spend-based quota on the RTB\nGraphs dashboard.\n\nThe Callout Quota System attempts to not exceed the requested quota limit per\nbidder server URL. More than 15K QPS, the system generally adheres to within 10%\nof the QPS limit, and more than 45K QPS, it generally adheres to within 5% of\nthe limit---often 1 to 2%.\n| **Key Point:** If pretargeting matches exceed the requested quota limits, excess bid requests are throttled.\n\nSometimes bid requests you're likely to respond to are prioritized based on your\nrecent bidding history. Here are some features Google uses to identify requests\nyou're likely to bid on:\n\n- Publisher IDs\n- Environment type\n- Ad format\n\nProgrammatic Guarantee requests are always prioritized.\n\nThe Callout Quota System is less accurate at small volumes. The requested quota\nlimit can be exceeded if the requested limit is about 1,000 QPS or less. In such\ncases, the requested quota can be doubled or occasionally more than doubled. If\nyou operate with small quota limits, you should consider reducing your quota\nlimit to account for these inaccuracies.\n\nCallout spillover\n-----------------\n\nCross-North America callout spillover helps maximize the number of bid requests\nyou receive within your QPS quota limit. This feature only applies to bidders\nwith server URLs in North America.\n\nThere are two Real-time Bidding (RTB)\n[trading locations](/authorized-buyers/rtb/peer-guide#trading-locations) in\nNorth America. When a callout is sent to one of these North America trading\nlocations and RTB detects that your bid request quota limit is already met\nthere, it transfers the callout to the other location, and tries to send a bid\nrequest to your server URL there.\n\nFor example, if RTB is processing a callout in the North America East Coast\ntrading location and detects that your East Coast server URL's quota limit is\nalready met, RTB then transfers the callout to the North America West Coast\ntrading location and tries to send a bid request to your West Coast server URL\ninstead.\n\nIf your quota is full in both locations, the callout is throttled.\n| **Warning:** This feature might not work as expected for bidders with geolocation-based DNS configurations. See the [Best practices](/authorized-buyers/rtb/practices-guide#submit-static-dns) guide for recommendations on DNS configuration.\n\nError throttling\n----------------\n\nThe Callout Quota System uses error throttling. It sends less callouts than it\ncan if the bidder doesn't respond to bid requests in time or if the bidder's\nresponses are invalid. Note that error throttling:\n\n- Triggers when Google deems the error rate too high for the bidder endpoints.\n\n- Gradually lowers the outgoing QPS until the error rate or number of bid\n requests drops to an acceptable level.\n\n- Is unrelated to the quota limit.\n\n- Adjusts within minutes to changing error rates."]]
