发布和监控
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
我们的团队会安排在特定日期和时间发布。您可能会看到商家上线时间延迟了几个小时。
您的集成在发布后会受到一周的监控。如果您的预订服务器或实时更新 (RTU) 超出任何错误阈值,我们会通知您进行更正。如果问题未解决,Google 将移除您的集成。
预订服务器
对于所有预订服务器实现,都必须包含 HealthCheck
路由。Actions Center 会定期检查您的HealthCheck
路线。
如果它没有响应或返回了不正常的响应,我们会暂时停用您的集成。我们会继续定期检查您的 HealthCheck
路由,并在其返回正常响应后自动恢复您的集成。
|
标准实现方法
|
错误率阈值
|
延迟时间阈值
|
CheckAvailability
注意:此预订服务器端点是旧版端点。新集成不得实现此端点。
|
<10% |
< 5 秒 |
BatchAvailabilityLookup
|
< 3% |
<1.5 秒 |
CreateBooking
UpdateBooking
|
<5% |
< 4 秒 |
RTU
对于 RTU,延迟时间是根据执行操作(例如修改预订)与 Action Center 收到 RTU 请求之间的时间差进行衡量的。
API
|
错误率阈值
|
延迟时间阈值
|
BookingNotification RTU
|
< 10%(每种状态每天) |
<5 分钟 |
您可以通过各种合作伙伴门户信息中心(即 Feed、预订服务器和 RTU 信息中心)监控错误率。
广告资源合规性要求
请务必继续遵守商品目录合规性要求。
如需了解商家如何选择不使用您的服务,请参阅帮助文章的移除第三方链接部分。
如果您违反了“商品目录合规性”政策,您的集成可能会被停用或终止。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-26。
[null,null,["最后更新时间 (UTC):2025-07-26。"],[],[],null,["# Launch and Monitor\n\nOur team schedules the launch for a specific date and time. You may see a delay\nof merchants going online over several hours.\n\nYour integration is monitored for a week after the launch. If your Booking\nServer or Real-Time Updates (RTUs) are over any error thresholds, we will inform\nyou to correct them. If the issues aren't resolved, Google will take down your\nintegration.\n\n### Booking Server\n\nFor all Booking Server implementations, there is a `HealthCheck` route that must\nbe included. The Actions Center periodically checks your `HealthCheck` route.\nIf it doesn't respond or returns an unhealthy response, we temporarily disable\nyour integration. We continue to periodically check your `HealthCheck` route\nand after it returns a healthy response, we automatically restore your\nintegration.\n\n|----------------------------------------------------------------------------------------------------------------------|-------|--------|\n| |||\n| `CheckAvailability` Note: This booking server endpoint is legacy. New integrations must not implement this endpoint. | \\\u003c10% | \\\u003c5s |\n| `BatchAvailabilityLookup` | \\\u003c3% | \\\u003c1.5s |\n| `CreateBooking` `UpdateBooking` | \\\u003c5% | \\\u003c4s |\n\n### RTUs\n\nFor RTUs, latency is measured by the time difference between when an action is\ntaken (for example, modifying a booking) and when Actions Center receives the\nRTU request.\n\n| **API** | **Error rate thresholds** | **Latency thresholds** |\n|---------------------------|-----------------------------------|------------------------|\n| `BookingNotification RTU` | \\\u003c10% each day and for each state | \\\u003c5 minutes |\n\nYou can monitor error rates through the various Partner Portal dashboards,\nnamely the [Feeds](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/feeds),\n[Booking Server](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/bookingserver),\nand [RTU](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/realtimeupdates)\ndashboards.\n\n### Inventory Compliance requirements\n\nMake sure that you continue to follow the [Inventory Compliance requirements](/actions-center/verticals/reservations/e2e/policies/compliance-requirements).\nFor information on how a merchant can opt out of your service, see\nthe **Remove third-party links** section of\nthe [help article](https://support.google.com/business/answer/6218037?hl=en&ref_topic=11498161&sjid=1606319823142007035-NC).\nIf you violate the Inventory Compliance policy, your integration could be\ndisabled or terminated."]]