샌드박스 환경에 처음 업로드한 후 데이터가 올바른지 확인하려면 피드 페이지에서 피드 오류가 있는지 확인하세요.
그런 다음 인벤토리 요약 페이지에서 데이터 문제가 있는지 확인합니다.
일반적인 문제는 서비스 없이 판매자를 업로드하거나 향후 이용 가능 시간대가 없는 서비스를 업로드하는 것입니다.
실시간 UI 환경을 에뮬레이션하는 샌드박스 프런트엔드는 사용자의 관점에서 데이터가 어떻게 표시되는지 보여줍니다. 액세스하려면 상단의 환경 전환 도구가 샌드박스로 설정되어 있는지 확인하고
인벤토리 > 인벤토리
로 이동하여 '준비됨' 또는 '실제 (샌드박스)'인 판매자를 찾은 다음 가장 오른쪽 열의 링크를 클릭하거나 (있는 경우) 행을 클릭하고 'RwG - E2E' 링크를 클릭합니다. '준비됨' 또는 '실제 (샌드박스)' 상태의 판매자가 없는 경우 사용 중지된 판매자를 열고 오른쪽에 나열된 모든 문제를 해결합니다 (예: 향후 이용 가능 여부가 업로드되었는지 확인).
샌드박스 프런트엔드에 액세스할 수 없는 경우 프런트엔드 액세스 권한이 부여된 계정으로 로그인되어 있는지 확인합니다. 또한 이 계정으로만 로그인되어 있는지 확인합니다. 다른 계정으로 로그인한 다음 사용자 전환 기능을 사용하여 승인된 Google 계정에 로그인해도 샌드박스 프런트엔드에서 차단됩니다.
프로덕션에 피드 업로드
오류가 없는 완전한 피드를 샌드박스 환경에 지속적으로 업로드할 수 있게 되면 프로덕션 환경에 업로드를 시작할 수 있습니다.
이 시점에서는 통합이 게시되지 않습니다.
판매자를 Google 비즈니스 등록정보에 일치시키기 시작할 수 있도록 전체 판매자 피드를 최대한 빨리 (출시 1주일 전까지) 업로드하세요. 일치가 올바른지 확인하세요.
프로덕션 피드 데이터가 모두 일관되게 업로드되고 프로덕션 시스템에 연결되면 피드를 검토할 수 있습니다.
Google에서 피드 평가
피드를 업로드하면 Google에서 피드를 처리하고 피드의 품질과 완전성을 평가합니다. Google은 다음과 같은 요인을 확인합니다.
피드가 피드 사양과 일치합니다.
피드에 필수 입력란이 모두 포함되어 있습니다.
피드의 총 판매자 수가 Google과 상의한 수와 일치합니다.
판매자별로 하나 이상의 서비스가 정의되어 있습니다.
피드의 총 서비스 수가 Google과 상의한 수와 일치합니다.
각 서비스에는 waitlist_rules가 포함됩니다.
제공된 판매자 중 Google 지도의 지형지물과 매치시킬 수 있는 판매자 수를 확인합니다.
[null,null,["최종 업데이트: 2025-07-26(UTC)"],[[["\u003cp\u003eRegularly provide Merchant and Service feeds to Google in JSON format, keeping each shard under 200MB and using \u003ccode\u003ePROCESS_AS_COMPLETE\u003c/code\u003e processing instruction.\u003c/p\u003e\n"],["\u003cp\u003eUpload feeds to the sandbox SFTP dropbox (\u003ccode\u003esftp://partnerupload.google.com:19321\u003c/code\u003e) for testing and validation before uploading to the production environment.\u003c/p\u003e\n"],["\u003cp\u003eGoogle evaluates feeds for quality and completeness based on factors including feed specification adherence, required fields, merchant and service counts, waitlist rules, and Google Maps matching.\u003c/p\u003e\n"],["\u003cp\u003eEnsure consistent, error-free feed uploads in the sandbox before moving to production, starting with a full Merchant feed for Google Business listing matching at least a week before launch.\u003c/p\u003e\n"],["\u003cp\u003eMonitor feed status and address errors using the Feeds page in the Partner Portal and confirm data correctness using the sandbox frontend.\u003c/p\u003e\n"]]],["Feeds, containing merchant and service data, must be provided to Google every 24 hours, using JSON format and protocol buffer 3 syntax, to display data on Google. Include metadata and process as complete. Each feed can contain shards, under 200MB compressed, uploaded to an SFTP server. Regularly upload to the sandbox for testing, then production. After uploading, monitor the \"Feeds\" page and \"Inventory Summary\" for errors, using the partner portal, ensuring data correctness and following content guidelines. Google will review the feeds.\n"],null,["# Step 2: Export feeds\n\nCreate feeds\n------------\n\nFeeds must be provided to Google on a regular basis for the data to be directly shown on Google.\nThe following feeds are needed.\n\n| Feed | Description | Frequency |\n|----------------------------------------------------------------------------------------------|-------------------------------------------|---------------------|\n| [Merchants](/actions-center/verticals/reservations/waitlists/reference/feeds/merchants-feed) | Describes your merchants. | Once every 24 hours |\n| [Services](/actions-center/verticals/reservations/waitlists/reference/feeds/services-feed) | Describes services your merchants provide | Once every 24 hours |\n\n| **Objective:** When you provide service names and descriptions, adhere to our [Content editorial guidelines](/actions-center/verticals/reservations/waitlists/support#content-guidelines).\n\nIn each feed, include\n[metadata](/actions-center/verticals/reservations/waitlists/reference/feeds/feed-metadata) that instructs Google on how to interpret it.\n| **Note:** All feeds must be uploaded with processing_instruction `PROCESS_AS_COMPLETE`. `PROCESS_AS_INCREMENTAL` is deprecated and cannot be used.\n\nThe feeds format is described with the\n[protocol buffer 3 syntax](/protocol-buffers/docs/proto3) but you can upload your feeds\nas the corresponding JSON format.\n\nPlease reference the\n[Feed samples](/actions-center/verticals/reservations/waitlists/reference/feeds/overview) to see the JSON format.\n\nWe recommend that you upload the feeds in JSON format.\n\nFeed file size, sharding, and compression\n-----------------------------------------\n\nPlease view the following tutorials regarding compression and shards:\n\n- [Compress feed files](/actions-center/verticals/reservations/waitlists/reference/tutorials/compression)\n- [Shard feed files](/actions-center/verticals/reservations/waitlists/reference/tutorials/sharding)\n\nTo determine the size of the feeds, use the following guidelines (a feed can be constituted\nof multiple files called \"shards\"):\n\n- Suggested feed sharding:\n - Merchants feed: 1 shard\n - Services feed: 1 shard\n- Size of feed files and sharding:\n - Keep shard file size below 200 MB (after compression). Use multiple shards if needed.\n - Individual records sent in one shard don't need to be sent in the same shard in future feeds.\n - For better performance, split data evenly among the shards, to make all the shard files similar in size.\n - If necessary, use gzip to compress plain text JSON feeds. However, do so for each individual feed shard.\n\nUpload the feeds to the SFTP Server\n-----------------------------------\n\nUpload your feeds to the sandbox environment. To do so, refer to the\nusernames within the\n[Partner Portal feed configuration](/actions-center/verticals/reservations/waitlists/partner-portal/testing/feeds) page. The Google SFTP server is\navailable at `sftp://partnerupload.google.com` on port\n`19321`.\n| **Warning:** Upload your feeds to the production servers only after Google has tested and confirmed your feeds in the sandbox environment.\n| **Note:** To access the sandbox, make sure that the [environment switcher](/actions-center/verticals/reservations/waitlists/partner-portal/overview/environment-switcher) on the top is set to Sandbox and go to **[Inventory \\\u003e Inventory](https://partnerdash.google.com/apps/reservewithgoogle/inventory?env=sandbox)**, find a merchant that is either \"Ready\" or \"Live (in Sandbox)\" then either click on the link on the rightmost column (if available) or click on the row and click on the \"RwG - E2E\" link.\n\nWe recommend that you give the files you upload unique names. For instance,\nit can be helpful to append each filename with a timestamp. This helps to\ntroubleshoot issues and query for feed status.\n| **Note:** Google processes feed files as soon as they're uploaded to the SFTP server. If the feed is sharded across multiple files, they are processed after you upload the last file. If your feed contains errors, an email is sent to you with the [feed error codes](/actions-center/verticals/reservations/waitlists/reference/feeds/feed-errors).\n\nConfirm that your data looks correct\n------------------------------------\n\nSign in to the Partner Portal. Toggle to the **Sandbox** environment to\nfind the following pages in the **Dashboards** section.\n\n[Feeds](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/feeds?activeTab=feeds&env=sandbox)\n: Shows the feed summary statistics and points out errors during feed\n upload.\n\nTo confirm that your data looks correct after your initial upload to the\nsandbox environment, check the\n**[Feeds](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/feeds?activeTab=feeds&env=sandbox)**\npage for any feed errors.\n\nThen check the **Inventory Summary** page for any data issues.\nCommon issues include uploading merchants without any services or uploading services\nwithout any availability slots in the future.\n\nThe sandbox frontend, which emulates the live UI experience, shows how the\ndata will look from the user's perspective. To access it, make sure that the\n[environment switcher](/actions-center/verticals/reservations/waitlists/partner-portal/overview/environment-switcher) on the top is\nset to Sandbox and go to\n**[Inventory \\\u003e Inventory](https://partnerdash.google.com/apps/reservewithgoogle/inventory?env=sandbox)**, find a merchant that is either \"Ready\" or \"Live (in Sandbox)\" then either click on the link\non the rightmost column (if available) or click on the row and click on the \"RwG - E2E\" link. If\nthere is no merchant with status \"Ready\" or \"Live (in Sandbox)\", open a disabled merchant and make\nsure to fix all the issues listed on the right (such as making sure future availability have been\nuploaded).\n| **Note:** Our system matches the merchants that you send us to merchants already listed on Google Maps. In the sandbox, we perform only automated matches for your merchants. In production, the process may involve human review. Therefore, matches in the sandbox don't reflect the matches made in production, which are more stringent.\n\nIf you can't access the sandbox frontend, confirm that you are signed in\nwith an account that has been given access to the frontend. Also be sure that\nthis is the only account you are signed in to. If you sign in with a\ndifferent account and then use the Switch User feature to sign in to the\napproved Google account, you are still blocked from the sandbox frontend.\n\nUpload your feeds to production\n-------------------------------\n\nOnce you are able to consistently upload complete, error-free feeds to the\nSandbox environment you may begin uploading to the Production environment.\nAt this point your integration will **not** be live.\n\nPlease upload a full **Merchant feed** as soon as possible (minimum\n1 week before launch), so you can begin matching your merchants to a Google\nbusiness listing. Please verify the matching correctness.\n\nOnce **all** your production feed data is uploading consistently\nand connected to your production system, your feeds are ready for review.\n\nGoogle evaluates feeds\n----------------------\n\nOnce you upload your feeds, Google processes and evaluates them for quality\nand completeness. We look at the following factors:\n\n1. Feeds match the feed specification.\n2. Feeds include all the required fields.\n3. The total number of merchants in feeds matches the number discussed with Google.\n4. At least one service is defined for each merchant.\n5. The total number of services in feeds matches the number discussed with Google.\n6. Each service includes `waitlist_rules`.\n7. We check how many of the merchants provided can be matched against features on Google Maps.\n\n| **Note:** As you submit your feeds, work through items 1-5 to ensure a smooth integration."]]
