Onboarding Health (新手上路健康狀態) 資訊主頁
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Onboarding Health (新手上路健康狀態) 資訊主頁
可用的 Onboarding Health (新手上路健康狀態) 資訊主頁會因環境而異，您可使用這些資訊主頁，在沙箱和正式環境中查看在地生活服務廣告端到端整合的目前健康情況。
在新手上路期間，沙箱資訊主頁會顯示您已完成整合的哪些部分，以及整合的哪些部分需要您特別留意。整合在「沙箱」和「正式環境」中都必須狀態良好，才能進行發布。
存取 Onboarding Health (新手上路健康狀態) 資訊主頁
請先登入合作夥伴入口網站，然後在「Dashboards」(資訊主頁) 下方選取「Onboarding Health」(新手上路健康狀態) 連結。只有採用端對端整合第 3 版的合作夥伴，才能使用新手上路健康狀態資訊主頁 (不是候位名單、商家連結或重新導向整合)。
在沙箱和正式環境的資訊主頁之間切換
合作夥伴入口網站的沙箱和正式環境中，都有「Onboarding Health」(新手上路健康狀態) 資訊主頁。如要在正式環境和沙箱之間切換，請按照環境切換工具說明文件中的指示操作。
各種狀態代表的意義
每一項新手上路健康狀態檢查旁邊，都有三種不同的狀態選項：
- 通過 (綠色)：您目前通過了這項檢查，且符合所有條件。
- 失敗 (紅色)：整合目前未達到這項整合健康狀態檢查的條件，這可能是因為您還沒有開始進行相關的整合作業。
- 不適用 (黃色)：這項新手上路健康狀態檢查不適用於您的整合，原因可能出在您的整合停用了某項功能。您不需要在意這類檢查。
我必須符合哪些條件才能通過檢查？
如要讓端對端在地生活服務廣告整合處於良好狀態，每項檢查的結果都必須是「通過」(綠色) 或「不適用」(黃色)。
每項新手上路健康狀態檢查旁邊都會列出相關條件 (在頁面右側)，這些條件的依據是成功上傳且正確無誤的動態饋給、預訂伺服器 API 回應，以及即時更新要求。
所需的測試次數會因環境 (正式環境或沙箱) 以及路徑而異：舉例來說，您需要為 CheckAvailability/BatchAvailabilityLookup 進行的測試數量，會比 CreateBooking 的數量更多。系統會在每項未通過測試的分數旁顯示說明，解釋您未符合哪些條件。
這個資訊主頁多久更新一次？
「Onboarding Health」(新手上路健康狀態) 資訊主頁每兩小時會更新一次。如果您變更了整合的某部分，就必須重新測試該部分，然後等待 2 小時再到資訊主頁查看變更的相關資訊。
舉例來說，如果您更新 CreateBooking 路徑，就需要從 Actions Center 前端測試該路徑，然後等候 2 小時，讓變更相關資訊反映在資訊主頁上。
為什麼 Onboarding Health (新手上路健康狀態) 資訊主頁顯示了我沒有做的檢查？
由於可用的整合類型不只一種，可能有一些新手上路健康狀態檢查並不適合您使用：這類檢查會以黃色標明，表示「不適用」。此外，有些檢查可能適用於多種整合類型，例如：
- BatchAvailabilityLookup 檢查也適用於 CheckAvailability。
如果您不確定某項新手上路健康狀態檢查的確切條件，請參考頁面右側的指南。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-26 (世界標準時間)。
[null,null,["上次更新時間：2025-07-26 (世界標準時間)。"],[[["\u003cp\u003eOnboarding health dashboards provide an environment-specific view of your Local Services Ads End-to-End integration health in sandbox and production.\u003c/p\u003e\n"],["\u003cp\u003eTo launch, your integration must be healthy in both sandbox and production environments, as indicated by the dashboard's status checks.\u003c/p\u003e\n"],["\u003cp\u003eDashboard statuses include Pass (Green), Fail (Red), and N/A (Yellow), reflecting the integration's adherence to specific criteria.\u003c/p\u003e\n"],["\u003cp\u003eAchieving a healthy integration requires all checks to be either Pass (Green) or N/A (Yellow), ensuring successful feed uploads, API responses, and real-time updates.\u003c/p\u003e\n"],["\u003cp\u003eThe dashboards update every two hours, requiring retesting and a waiting period for changes to be reflected after integration modifications.\u003c/p\u003e\n"]]],["The Onboarding Health dashboards, accessible via the Partner Portal, display the health of Local Services Ads End-to-End integrations in sandbox and production environments. Statuses include Pass (green), Fail (red), or N/A (yellow). Successful integration requires all checks to be Pass or N/A, based on criteria from feed uploads, booking server API responses, and real-time updates. Dashboards update every two hours, requiring re-testing of integration changes. The criteria are listed next to the check and the number of attempts needed varies.\n"],null,["# Onboarding Health Dashboards\n----------------------------\n\nThe onboarding health dashboards are environment specific and will allow you to\nsee the current health of your Local Services Ads End-to-Endintegration in your sandbox and\nproduction environments.\n\nDuring onboarding, the sandbox dashboard will show you which areas of\nthe integration you have completed and which areas of the integration still need\nmore attention. In order to launch it is expected that you have a healthy\nintegration in both Sandbox and Production.\n\nAccessing the Onboarding Health Dashboards\n------------------------------------------\n\nOnce logged into the Partner Portal, select the \"Onboarding Health\" link under\n\"Dashboards.\" The onboarding health dashboards can only be used by partners on\nv3 of end-to-end integrations (ie not waitlist, business link, or redirect\nintegrations).\n\nSwitching between Sandbox and Production dashboards\n---------------------------------------------------\n\nThe Onboarding Health dashboard is available in both sandbox and production\nenvironments in the partner portal. To switch between production and sandbox\nplease follow the [environment switcher documentation](/actions-center/verticals/local-services/e2e/partner-portal/overview/environment-switcher)\n\nWhat each status means\n----------------------\n\nThere are three different status options you will see next to each onboarding\nhealth check:\n\n- Pass (Green): You are currently passing this check. All criteria are currently being met.\n- Fail (Red): The integration is not currently passing the criteria for this integration health check. This could be because you have not begun working on this aspect of the integration yet.\n- N/A (Yellow): This onboarding health check does not apply to your integration.This could be because a specific feature has been turned off for your integration. You do not need to worry about these checks.\n\nWhat criteria do I need to meet to get a passing score?\n-------------------------------------------------------\n\nIn order for your Local Services Ads End-to-End integration to be considered healthy, you\nwill need every check to say either Pass (Green) or N/A (Yellow).\n\nEach different onboarding health check will have the criteria listed next to\nthe check on the right of the page. The criteria are based off of successful\nand error free feed uploads, booking server api responses, and real-time update\nrequests.\n\nThe number of attempts needed will vary by environment (production vs\nsandbox) as well as the route (for example, you will need to make more tests for\nCheckAvailability/BatchAvailabilityLookup than you would\nneed to for CreateBooking). Each test that is not passing will\nhave a description next to the score telling you what criteria has not been met.\n\nHow often does this dashboard update?\n-------------------------------------\n\nThe onboarding health dashboards update once every two hours. After you make a\nchange to the integration you will need to re-test that portion of the\nintegration and wait two hours for the changes to reflect.\n\nFor example, if you update your CreateBooking route, you will need to test that\nroute from the Actions Center frontend and wait two hours for the changes to\nreflect on the dashboard.\n\nWhy are there things I did not implement on the onboarding health dashboard?\n----------------------------------------------------------------------------\n\nBecause there are different types of integrations available, there may be some\nonboarding health checks that do not apply to you. If a specific check does not\napply to your Local Services Ads End-to-End integration, it will be marked as N/A in yellow.\nCertain checks map apply to a variety of integration types. For example:\n\n- The BatchAvailabilityLookup check also works for CheckAvailability.\n\nIf you are unsure of the exact criteria for a specific onboarding health check,\nyou can reference the guide on the right of the page."]]
