Launch and monitoring
Stay organized with collections
Save and categorize content based on your preferences.
At launch, Google enables all of your eligible inventory in our production
environment. This completes the integration and allows any external user to
book or reserve your inventory through the Actions Center.
Once you've launched, it's important to monitor the health of your
integration. The following thresholds must be maintained. Failure to maintain
these thresholds consistently will result in integration take-down.
Feeds
- Feeds should be sent on a daily basis with no errors or warnings
- Processing instructions should be set to PROCESS_AS_COMPLETE
- For Availability feeds, the full inventory daily feed upload should
not set any
_restrict fields.
Booking server
For all booking server implementations, there is a HealthCheck route that
should be included. Google will periodically check your HealthCheck route
and should it not respond or return an unhealthy response, we will
temporarily disable your integration. We will continue to periodically
check your HealthCheck route and once it resumes returning a healthy
response we will automatically restore your integration.
| Standard implementation |
| Method |
Error Rate Thresholds |
Latency Thresholds |
| CheckAvailability |
<10% |
<5s |
| BatchAvailabilityLookup |
<3% |
<1.5s |
| CreateLease |
<10% |
<5s |
CreateBooking
UpdateBooking |
<5% |
<4s |
CreateBooking
(with payments) |
<5% |
<15s |
| SetMarketingPreference |
<5% |
<5s |
| Waitlist implementation |
| Method |
Error Rate Thresholds |
Latency Thresholds |
| BatchGetWaitEstimates |
<3% |
<1s |
CreateWaitlistEntry
GetWaitlistEntry
DeleteWaitlistEntry |
<5% |
<4s |
Real-time updates
For real-time updates, latency is measured by the time difference between
when an action is taken (e.g. modifying a booking) and when Reserve with
Google receives the real-time update request.
| API |
Error Rate Thresholds |
Latency Thresholds |
| AvailabilityReplace RTU |
<10% each day |
<5 mins |
| BookingNotification RTU |
<10% each day & for each state |
<5 mins |
Error rates can be monitored through the various Partner Portal dashboards,
namely the
Feeds,
Booking Server, and
Real-time Updates dashboards.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-05-20 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-20 UTC."],[[["\u003cp\u003eUpon launch, all eligible inventory is activated, enabling external users to book through Google.\u003c/p\u003e\n"],["\u003cp\u003eMaintaining specific performance thresholds is crucial for continued integration; failure to do so will result in takedown.\u003c/p\u003e\n"],["\u003cp\u003eKey thresholds include feed accuracy, booking server responsiveness, and real-time update latency, as detailed in provided tables.\u003c/p\u003e\n"],["\u003cp\u003eError rates and other performance metrics can be monitored via dedicated dashboards in the Partner Portal.\u003c/p\u003e\n"]]],["Upon launch, Google makes your inventory bookable via the Actions Center. Post-launch, maintaining integration health is crucial, with specific thresholds for feeds, booking servers, and real-time updates. Daily feeds must be error-free. Booking server methods have error rate and latency limits (e.g., `\u003c10%` error rate for CheckAvailability, `\u003c5s` latency). Real-time updates also have error and latency thresholds (e.g `\u003c10%` and \u003c5 mins respectively). Health status and the error rate can be tracked through the partner portal dashboards.\n"],null,["# 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\n| Waitlist implementation |||\n| Method | Error Rate Thresholds | Latency Thresholds |\n|----------------------------------------------------------|-----------------------|--------------------|\n| BatchGetWaitEstimates | \\\u003c3% | \\\u003c1s |\n| CreateWaitlistEntry GetWaitlistEntry DeleteWaitlistEntry | \\\u003c5% | \\\u003c4s |\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."]]
