Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Untuk membantu memenuhi batasan latensi layanan RTB, Anda harus menempatkan
server di dekat lokasi perdagangan yang tercantum di bawah. Lihat diskusi tentang
menemukan bidder untuk mengetahui informasi selengkapnya.
Lokasi perdagangan
Lokasi trading adalah titik optimal dari cluster server yang tersebar secara geografis
tempat infrastruktur yang menghosting aplikasi bidder dapat memperoleh manfaat terbesar
dalam hal latensi. Info bidding real-time tidak selalu berasal dari
lokasi perdagangan, dan dapat berasal dari tempat lain di cluster. Sebagai
contoh, Singapura adalah lokasi perdagangan untuk cluster Asia Pasifik
yang membentang dari Australia hingga Singapura.
Tabel berikut mencantumkan domain referensi yang dapat digunakan untuk menilai latensi dan memperkirakan lokasi terbaik untuk server Anda.
Cluster Server
Lokasi Perdagangan
Domain Referensi
Amerika Utara (Pantai Timur)
Northern Virginia, Amerika Serikat
rtb-us-east.g.doubleclick.net
Amerika Utara (Pantai Barat)
San Francisco Bay Area, California, Amerika Serikat
rtb-us-west.g.doubleclick.net
Eropa
Amsterdam, Belanda
rtb-europe.g.doubleclick.net
Asia Pasifik
Singapura
rtb-asia.g.doubleclick.net
Lokasi bidder
Kami mencoba mengirim permintaan bid ke lokasi perdagangan yang paling dekat dengan lokasi pengguna. Namun,
kami tidak menjamin bahwa permintaan bid untuk tayangan iklan pengguna tertentu akan selalu dikirim ke
lokasi perdagangan terdekat. Oleh karena itu, untuk menerima semua tayangan, Anda harus memiliki server yang dapat dijangkau
dari semua lokasi. Jika Anda hanya menginginkan sebagian tayangan iklan, menjalankan server di
sebagian lokasi mungkin sudah cukup. Misalnya, sebagian besar, tetapi tidak semua, traffic Amerika Utara dapat diterima dengan
menjalankan server yang dapat dijangkau dari pantai Timur dan Barat.
Batas waktu pengiriman respons bid ditunjukkan di
BidRequest.tmax. Batas waktu biasanya berkisar antara 80 hingga 1.000 md.
Kami mewajibkan 85 persen respons diterima dalam batas waktu
dari perspektif lokasi perdagangan dan akan membatasi bidder yang
tidak dapat secara konsisten mencapai hal ini. Batas waktu ini mencakup waktu jaringan
antara lokasi perdagangan dan bidder Anda, serta waktu yang diperlukan bidder Anda
untuk menghasilkan respons. Sebaiknya targetkan total waktu jauh di bawah
batas waktu untuk memberikan buffer bagi perubahan latensi jaringan
yang tidak terduga antara bidder dan lokasi perdagangan.
Peering
Google merekomendasikan agar pembeli RTB yang menerima permintaan dalam jumlah besar menyiapkan permintaan peering dengan kami untuk mengurangi latensi dan volatilitas latensi.
Kami melakukan peering dengan jaringan apa pun selama jaringan tersebut memenuhi persyaratan teknis
Google, seperti memiliki ASN publik. Lihat persyaratan teknis untuk
mengetahui detail selengkapnya. Perhatikan bahwa persyaratan traffic dihapus untuk klien RTB. Lihat
Kebijakan Peering
Google untuk informasi tambahan.
Untuk memulai permintaan peering, isi formulir permintaan peering kami. Kemudian, kami akan
mengirimkan nomor tiket melalui email yang dapat Anda gunakan dalam tindak lanjut apa pun dengan
pengelola akun teknis Anda.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eTo minimize latency in the Real-Time Bidding (RTB) service, position your servers near the specified trading locations, such as Northern Virginia, San Francisco Bay Area, Amsterdam, and Singapore.\u003c/p\u003e\n"],["\u003cp\u003eTrading locations serve as optimal points for server clusters to reduce latency, but bid requests can originate from anywhere within the cluster and are not guaranteed to always be sent to the geographically closest location.\u003c/p\u003e\n"],["\u003cp\u003eTo receive all potential impressions, ensure your servers are reachable from all listed trading locations; however, running servers in a subset of locations can suffice if only a specific subset of impressions are desired.\u003c/p\u003e\n"],["\u003cp\u003eBidders must respond to bid requests within a deadline, typically between 80 to 1000 ms, with a requirement that 85 percent of responses meet this deadline.\u003c/p\u003e\n"],["\u003cp\u003eFor high-volume RTB buyers, Google recommends setting up peering to decrease latency and latency volatility, with traffic requirements being waived specifically for RTB clients.\u003c/p\u003e\n"]]],[],null,["To help meet the latency restrictions of the RTB service, you should locate\nyour servers close to the trading locations listed below. See the discussion on\n[locating your bidders](#bidder-location) for more information.\n\nTrading locations\n\nA trading location is the optimal point of a geographically dispersed server\ncluster where infrastructure hosting a bidder application can benefit most in\nterms of latency. Real-time bidding callouts do not necessarily originate at\nthe trading location, and can come from elsewhere in the cluster. As an\nexample, Singapore is the trading location for the Asia Pacific cluster\nspanning from Australia to Singapore.\n\nThe following table lists reference domains that can be used to assess\nlatency and estimate the best locations for your server.\n\n| Server Cluster | Trading Location | Reference Domain |\n|----------------------------|---------------------------------------------------|-------------------------------|\n| North America (East Coast) | Northern Virginia, United States | rtb-us-east.g.doubleclick.net |\n| North America (West Coast) | San Francisco Bay Area, California, United States | rtb-us-west.g.doubleclick.net |\n| Europe | Amsterdam, Netherlands | rtb-europe.g.doubleclick.net |\n| Asia Pacific | Singapore | rtb-asia.g.doubleclick.net |\n\n| **Note:** We provide these domains for approximate estimation of latencies only. Routing outside of Google's network and Google's deployment of the service may change over time. In addition, network congestion or short term maintenance issues may leave these domains unreachable or too distant from a given location for extended periods.\n\nBidder location\n\nWe attempt to send bid requests to the trading location closest to the user's location. However,\nwe do not guarantee that bid requests for a given user's impressions will always be sent to the\nclosest trading location. Therefore, to receive all impressions, you need to have servers reachable\nfrom all locations. If you only want a subset of impressions, it may be sufficient to run servers in\na subset of locations. For example, most, but not all, North American traffic can be received by\nrunning servers reachable from the East and West coasts.\n\nThe deadline that you must send a bid response by is indicated in\n`BidRequest.tmax`. The deadline typically ranges from 80 to 1000 ms.\n\nWe require that 85 percent of responses be received within the deadline\nfrom the perspective of the trading location and will throttle bidders that\ncannot consistently achieve this. This deadline includes both the network time\nbetween the trading location and your bidder, and the time it takes your bidder\nto generate a response. We recommend targeting a total time well below the\ndeadline in order to to leave a buffer for unexpected changes in network\nlatency between your bidder and the trading location.\n\nPeering\n\nGoogle recommends that RTB buyers receiving a large volume of requests set\nup peering requests with us to reduce latency and latency volatility.\n\nWe peer with any network as long as they meet Google's technical\nrequirements, like having a public ASN. See the [technical requirements](//www.peeringdb.com/view.php?asn=15169) for\nmore details. Note that the traffic requirement is waived for RTB clients. See\nGoogle's [Peering Policy](//peering.google.com/#/options/peering)\nfor additional information.\n\nTo initiate a peering request, fill out our [peering request form](//isp.google.com/iwantpeering). We will then\nemail you a ticket number which you can use in any followups with your\ntechnical account manager."]]
