Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Setelah aplikasi selesai, dan Anda telah mengujinya secara internal, aplikasi tersebut harus
melakukan serangkaian pengujian standar yang dilakukan oleh perwakilan akun Google
Anda yang mengirimkan permintaan pengujian ke server Anda. Setelah aplikasi Anda
lulus pengujian ini, aplikasi tersebut memenuhi syarat untuk dirilis. Topik berikut menjelaskan
cara kerja proses pengujian dan rilis.
Menguji dengan traffic Google
Jika Anda siap untuk mulai melakukan pengujian dengan traffic yang dikirim dari Google, hubungi
perwakilan Authorized Buyers Anda. Anda akan diminta untuk memberikan berbagai
informasi seperti berikut:
Informasi kontak engineer. Jika pengujian tidak berjalan seperti
yang diharapkan dan ada masalah teknis yang harus ditangani, kami akan menggunakan
informasi kontak ini untuk berinteraksi langsung dengan tim Anda.
URL yang mengaktifkan SSL dan merespons permintaan RTB.
URL server Pencocokan Kode Cookie yang mengaktifkan SSL, jika Anda memilih
untuk menggunakan fungsi ini.
Lokasi fisik (negara bagian, negara) server RTB Anda, untuk
mengoptimalkan komunikasi dengan server Google.
QPS (kueri per detik) maksimum yang ingin Anda tayangkan dari setiap
lokasi fisik setelah pengujian selesai.
Tanggal server Pencocokan Kode RTB / Cookie Anda aktif untuk
pengujian. Google akan mengirimkan permintaan RTB ke server Anda pada atau segera setelah
tanggal tersebut.
Estimasi latensi yang akan digunakan server Anda untuk memproses permintaan RTB.
Kunci PGP untuk informasi dekripsi harga pengiriman.
Hubungi perwakilan Authorized Buyers Anda untuk melakukan perubahan pada informasi
ini kapan saja selama proses pengujian.
Pengujian akan melibatkan beberapa langkah dengan traffic sintetis untuk memverifikasi latensi dari berbagai lokasi. Google juga akan melakukan beberapa pengujian dasar yang
dirender iklan dan untuk pelacakan klik dengan benar. (Sebagian besar hal ini harus dilakukan selama
pengujian Anda sendiri dan selama sertifikasi.) Kami juga akan meminta Anda untuk
mengonfirmasi bahwa Anda dapat menerima dan mendekode notifikasi dan
klik harga pemenang. Setelah item ini diverifikasi, langkah berikutnya adalah peningkatan traffic live secara bertahap selama beberapa hari.
Persyaratan latensi untuk menggunakan Bidder Real-time adalah 80 hingga 1.000 md,
diukur dari waktu Google mengirim panggilan hingga waktu Google menerima
balasan. Batas waktu ini bergantung pada format dan jenis lelang; periksa
kolom BidRequest.tmax untuk mengetahui nilai yang tepat.
Agar memenuhi syarat untuk tayangan iklan yang diproses di lokasi tertentu, maksimal 2% permintaan harus melebihi batas waktu ini. Jika Anda ingin menerima tayangan iklan
dari beberapa
lokasi trading sesuai dengan persyaratan ini, biasanya Anda harus
menjalankan server bidding di semua region. Misalnya, untuk menerima tayangan iklan
dari Pantai Timur dan Pantai Barat Amerika Serikat, Anda biasanya harus
memiliki server bidding yang berjalan di Pantai Timur dan Pantai Barat.
Bidder yang sementara memiliki rasio waktu tunggu tinggi karena peristiwa jaringan
atau masalah lainnya akan otomatis dibatasi. Throttling ini akan
otomatis mengurangi atau meningkatkan traffic selama jangka waktu beberapa menit. Jika
traffic sering dibatasi selama jangka waktu yang lama, Google dapat
menyesuaikan kuota traffic Anda ke tingkat yang dapat ditangani dengan lebih konsisten.
[[["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\u003eOnce in-house testing is complete, applications must undergo standardized tests from Google, with the Google account representative sending test requests to the servers, in order to become eligible for release.\u003c/p\u003e\n"],["\u003cp\u003eTo initiate testing with Google traffic, you must contact your Authorized Buyers representative and provide them with key information such as engineering contact details, server URLs, server locations, maximum QPS, and PGP keys.\u003c/p\u003e\n"],["\u003cp\u003eTesting involves synthetic traffic to verify latencies and basic ad rendering, as well as receiving and decoding winning price notifications and clicks, followed by a gradual ramp-up of live traffic.\u003c/p\u003e\n"],["\u003cp\u003eThe latency requirement for Real-time Bidder is between 80 to 1000 ms, and no more than 2% of requests should exceed this deadline to qualify for impressions from a specific location.\u003c/p\u003e\n"],["\u003cp\u003eBidders with high timeout rates will experience automatic throttling, with Google adjusting traffic quotas if throttling persists over an extended period.\u003c/p\u003e\n"]]],["After in-house testing, contact your Google representative to initiate testing with Google traffic. Provide details like engineering contacts, SSL-enabled URLs, server locations, maximum QPS, and estimated latency. Testing involves synthetic traffic to verify latency and basic ad functionality. Live traffic will gradually increase. The latency requirement is 80-1000 ms. High timeout rates trigger automatic throttling, which might result in a reduced traffic quota. Servers in multiple locations are recommended for broader reach.\n"],null,["When your application is complete, and you have tested it in-house, it must\nundergo a suite of standardized tests in which your Google account\nrepresentative sends test requests to your servers. Once your application\npasses these tests, it is eligible for release. The following topics explain\nhow the test and release process works.\n\nTesting with Google traffic\n\nWhen you are ready to start testing with traffic sent from Google, contact\nyour Authorized Buyers representative. You will be asked to provide various\ninformation such as the following:\n\n- Engineering contact information. If the testing does not proceed as expected and there are engineering issues to be addressed we will use this contact information to interact directly with your team.\n- The SSL-enabled URL that responds to RTB requests.\n- The SSL-enabled URL of the Cookie Code Matching server, if you opted to use this functionality.\n- The physical location (state, country) of your RTB servers, in order to optimize communication with Google's servers.\n- Maximum QPS (query-per-second) you are willing to serve from each physical location after testing is finished.\n- Date from which your RTB / Cookie Code Matching servers are live for testing. Google will send RTB requests to your servers on or soon after that date.\n- Estimated latency your servers will use for processing RTB requests.\n- PGP keys for mailing price decryption information.\n- Confirm that [pretargeting](//support.google.com/authorizedbuyers/answer/6048315) is set up in your [Pretargeting\n UI](//www.google.com/authorizedbuyers).\n\nContact your Authorized Buyers representative to make changes to this\ninformation at any time during the testing process.\n\nTesting will involve several steps with synthetic traffic to verify\nlatencies from different locations. Google will also do some basic tests that\nads render and to click tracking properly. (Most of this should be done during\nyour own testing and during certification.) We will also ask for you to\nconfirm that you are able to receive and decode winning price notifications and\nclicks. Once these items are verified, the next step will be a gradual ramp up\nof live traffic over several days.\n| Since your account as a whole is placed into test mode for this, any bid that you make in response will be filtered out of the auction whether the value you see in the `BidRequest.test` is `true` or `false` (`1` or `0` if using the JSON format).\n\nThe latency requirement for using Real-time Bidder is 80 to 1000 ms,\nmeasured from the time Google sends the call to the time Google receives a\nreply. This deadline depends on format and auction type; check the\n`BidRequest.tmax` field for the exact value.\n\n\u003cbr /\u003e\n\nTo qualify for impressions processed at a given location, at most 2% of requests should exceed this deadline. If you want to receive impressions from multiple [trading locations](/authorized-buyers/rtb/peer-guide#trading_locations) according to these requirements, it is usually necessary to run bidding servers in all regions. For example, receiving impressions from both the East and West coasts of the United States will usually require that you have bidding servers running on both the East and West coast.\n\n\u003cbr /\u003e\n\nA bidder that temporarily has high timeout rates because of network events\nor other problems will be automatically throttled. This throttling will\nautomatically reduce or increase traffic over a time-frame of a few minutes. If\ntraffic is often throttled for an extended period of time, then Google may\nadjust your traffic quota to a level that can be handled more consistently."]]
