Langkah 5: Peluncuran dan pemantauan
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Saat peluncuran, Google mengaktifkan semua inventaris yang memenuhi syarat di lingkungan produksi kami. Tindakan ini menyelesaikan integrasi dan memungkinkan pengguna eksternal
memesan atau mereservasi inventaris Anda melalui Pusat Tindakan.
Setelah Anda melakukan peluncuran, penting untuk memantau kondisi integrasi Anda. Ambang batas berikut harus dipertahankan. Kegagalan dalam mempertahankan ambang batas ini secara konsisten akan mengakibatkan penghapusan integrasi.
Feed
- Feed harus dikirim setiap hari tanpa error atau peringatan
- Petunjuk pemrosesan harus ditetapkan ke PROCESS_AS_COMPLETE
- Untuk feed Ketersediaan, upload feed harian inventaris lengkap tidak boleh menetapkan kolom
_restrict apa pun.
Server pemesanan
Untuk semua penerapan server pemesanan, ada rute HealthCheck yang harus disertakan. Google akan memeriksa rute HealthCheck Anda secara berkala,
dan jika tidak merespons atau menampilkan respons yang tidak sehat, kami akan
menonaktifkan integrasi Anda untuk sementara. Kami akan terus memeriksa rute HealthCheck Anda secara berkala dan setelah rute tersebut kembali menampilkan respons yang sehat, kami akan otomatis memulihkan integrasi Anda.
| Penerapan standar |
| Metode |
Ambang Batas Tingkat Error |
Ambang Batas Latensi |
| CheckAvailability |
<10% |
<5 dtk |
| BatchAvailabilityLookup |
<3% |
<1,5 dtk |
| CreateLease |
<10% |
<5 dtk |
CreateBooking
UpdateBooking |
<5% |
<4 dtk |
CreateBooking
(dengan pembayaran) |
<5% |
<15 dtk |
| SetMarketingPreference |
<5% |
<5 dtk |
Update realtime
Untuk update real-time, latensi diukur berdasarkan selisih waktu antara saat tindakan diambil (mis., mengubah pemesanan) dan saat Pesan dengan Google menerima permintaan update real-time.
| API |
Ambang Batas Tingkat Error |
Ambang Batas Latensi |
| Update real-time AvailabilityReplace |
<10% setiap hari |
<5 mnt |
| Update real-time BookingNotification |
<10% setiap hari & untuk setiap status |
<5 mnt |
Tingkat error dapat dipantau melalui berbagai dasbor Portal Partner, yaitu dasbor Feed, Server Pemesanan, dan Update Real-Time.
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-07-26 UTC.
[null,null,["Terakhir diperbarui pada 2025-07-26 UTC."],[[["\u003cp\u003eGoogle enables eligible inventory for external user booking upon integration launch through Actions Center.\u003c/p\u003e\n"],["\u003cp\u003eMaintaining specific thresholds for feeds, booking server, and real-time updates is crucial for sustained integration.\u003c/p\u003e\n"],["\u003cp\u003eFailure to consistently meet these performance benchmarks, including error rates and latency, will result in integration takedown.\u003c/p\u003e\n"],["\u003cp\u003ePartners can monitor integration health and error rates through dedicated dashboards within the Partner Portal, covering feeds, booking server, and real-time updates.\u003c/p\u003e\n"]]],["Upon launch, all eligible inventory is enabled for external user booking. Post-launch, daily feeds must be sent error-free with `PROCESS_AS_COMPLETE` and no `_restrict` fields in Availability feeds. A functioning HealthCheck route is crucial; failure results in temporary integration disablement. Booking server and real-time updates have strict error and latency thresholds. These are monitored via the Feeds, Booking Server, and Real-time Updates dashboards. Consistent failure to meet standards will result in integration removal.\n"],null,["# Step 5: Launch and monitoring\n\nAt launch, Google enables all of your eligible inventory in our production\nenvironment. This completes the integration and allows any external user to\nbook or reserve your inventory through the Actions Center.\n\nOnce you've launched, it's important to monitor the health of your\nintegration. The following thresholds must be maintained. Failure to maintain\nthese thresholds consistently will result in integration take-down.\n\nFeeds\n-----\n\n- Feeds should be sent on a daily basis with no errors or warnings\n - Processing instructions should be set to PROCESS_AS_COMPLETE\n - For Availability feeds, the full inventory daily feed upload should not set any `_restrict` fields.\n\nBooking server\n--------------\n\nFor all booking server implementations, there is a HealthCheck route that\nshould be included. Google will periodically check your HealthCheck route\nand should it not respond or return an unhealthy response, we will\ntemporarily disable your integration. We will continue to periodically\ncheck your HealthCheck route and once it resumes returning a healthy\nresponse we will automatically restore your integration.\n\n| Standard implementation |||\n| Method | Error Rate Thresholds | Latency Thresholds |\n|-------------------------------|-----------------------|--------------------|\n| CheckAvailability | \\\u003c10% | \\\u003c5s |\n| BatchAvailabilityLookup | \\\u003c3% | \\\u003c1.5s |\n| CreateLease | \\\u003c10% | \\\u003c5s |\n| CreateBooking UpdateBooking | \\\u003c5% | \\\u003c4s |\n| CreateBooking (with payments) | \\\u003c5% | \\\u003c15s |\n| SetMarketingPreference | \\\u003c5% | \\\u003c5s |\n\nReal-time updates\n-----------------\n\nFor real-time updates, latency is measured by the time difference between\nwhen an action is taken (e.g. modifying a booking) and when Reserve with\nGoogle receives the real-time update request.\n\n| API | Error Rate Thresholds | Latency Thresholds |\n|-------------------------|----------------------------------|--------------------|\n| AvailabilityReplace RTU | \\\u003c10% each day | \\\u003c5 mins |\n| BookingNotification RTU | \\\u003c10% each day \\& for each state | \\\u003c5 mins |\n\nError rates can be monitored through the various Partner Portal dashboards,\nnamely the\n[Feeds](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/feeds),\n[Booking Server](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/bookingserver), and\n[Real-time Updates](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/realtimeupdates) dashboards."]]
