מייצאים את הפידים. הפורמט של הפיד מתואר באמצעות תחביר של protocol buffer 3, אבל אפשר לעיין בדוגמאות שצוינו למעלה כדי לראות את פורמט ה-JSON.
מומלץ להעלות את הפיד בפורמט JSON.
אם אתם רוצים להמשיך בפורמט pb3, תוכלו לקרוא מידע כללי על שימוש במאגרי פרוטוקול כדי ליצור קובץ pb3 במאמר יסודות של Protocol Buffer: Java.
מעלים את הפידים לשרת ה-SFTP. כדי להעלות את הפידים, משתמשים בפרטי שרת ה-SFTP ש-Google סיפקה לכם ובמפתח הפרטי שיצרתם בהגדרה. שרת ה-SFTP של Google זמין בכתובת sftp://partnerupload.google.com ביציאה 19321.
כדאי להעלות קבצים עם שמות ייחודיים, כמו שם שכולל חותמת זמן. שמות ייחודיים עוזרים בפתרון בעיות ומאפשרים להריץ שאילתות לגבי סטטוס הפיד.
כדי לקבוע את הגודל של הפידים ואת תדירות השליחה, מומלץ לפעול לפי ההנחיות הבאות:
הגודל של קבצים ושבבים של פידים:
חשוב לוודא שגודל קובץ הפיד קטן מ-200MB (אחרי דחיסת נתונים). דחיסת הקבצים באמצעות gzip
אם הקובץ עשוי להגיע לגודל של יותר מ-200MB (אחרי דחיסת נתונים), צריך לפצל אותו לכמה קטעים לפי ההוראות במדריך
פיצול של קובצי פיד
. עם זאת, סביר להניח שהשילוב של ערכת ההתחלה מדור קודם לא יגיע למגבלה של 200MB.
תדירות העדכונים המלאים:
פיד מלא של מוכרים מסופק פעם ביום.
(אם הטמעתם את הפיד) פיד שירות מלא מסופק פעם ביום.
Google בודקת את הפידים
אחרי שתעלו את הפידים, Google תעבד אותם ותעריך את האיכות והשלמות שלהם. אנחנו מביאים בחשבון כמה גורמים:
הפיד עומד בדרישות המפרט.
הפידים כוללים את כל שדות החובה.
לכל מוכר יש לפחות action_link אחד או שירות אחד עם לפחות action_link מוגדר.
רוב נתוני המוכרים שלכם תואמים למיקומים במפות Google.
[null,null,["עדכון אחרון: 2025-07-26 (שעון UTC)."],[[["\u003cp\u003eYou need to create and upload at least a Merchants feed, and optionally a Services feed, to transmit your inventory data to Google.\u003c/p\u003e\n"],["\u003cp\u003eThe Merchants feed requires fields such as \u003ccode\u003emerchant_id\u003c/code\u003e, \u003ccode\u003ename\u003c/code\u003e, \u003ccode\u003egeo\u003c/code\u003e, and \u003ccode\u003etelephone\u003c/code\u003e, while the Services feed (if used) needs \u003ccode\u003eservice_id\u003c/code\u003e, \u003ccode\u003emerchant_id\u003c/code\u003e, \u003ccode\u003elocalized_service_name\u003c/code\u003e, \u003ccode\u003etype\u003c/code\u003e, and \u003ccode\u003eaction_link\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eInclude feed metadata with each feed, setting \u003ccode\u003eprocessing_instruction\u003c/code\u003e to \u003ccode\u003ePROCESS_AS_COMPLETE\u003c/code\u003e and a unique generation timestamp, and if using multiple files, be sure to properly shard them.\u003c/p\u003e\n"],["\u003cp\u003eUpload your feeds in JSON format to Google's SFTP server, with each file named uniquely, and ensure files are under 200MB (after compression) and compressed using \u003ccode\u003egzip\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eGoogle evaluates uploaded feeds for specification compliance, required fields, action links for each merchant or service, and matches with Google Maps locations.\u003c/p\u003e\n"]]],["To start, generate Merchant and optional Services feeds, detailing merchants, services, and action links. Merchant feeds require `merchant_id`, `name`, `geo`, and `telephone`; Services feeds need `service_id`, `merchant_id`, `localized_service_name`, `action_link`, and `type`. Include feed metadata, particularly `PROCESS_AS_COMPLETE`. Export in JSON or pb3 format, then upload to the provided SFTP dropbox with unique filenames, keeping files under 200MB. Provide complete merchant feeds daily. Google then checks for specification compliance, required fields, action links, and Google Maps matching.\n"],null,["# Starter Feeds (legacy)\n\n\u003cbr /\u003e\n\nFirst you need to create your feeds, then Google evaluates them.\n\nCreate feeds\n------------\n\n1. **Generate your feeds.** You transmit most of your inventory data to\n Google by feeds. To get started, create two types of feeds:\n\n - [Merchants feed:](/actions-center/verticals?vertical_redirect_fragment=reference/feed-specifications/merchants-feed) The Merchants feed describes your merchants and merchant level action links.\n - [Services feed](/actions-center/verticals?vertical_redirect_fragment=reference/feed-specifications/services-feed) (optional): The Services feed describes services and service level `action_link`s your merchants provide to your platform.\n\n **Required and Recommended fields**\n\n | Feed | Field name | Description | Required? |\n |----------|------------------------|---------------------------------------------------------------------------------------------|-----------------------------------------------------------|\n | Merchant | merchant_id | Unique identifier for the merchant | Yes |\n | Merchant | name | Name of the merchant | Yes |\n | Merchant | geo | Address and geo coordinates of the merchant | Yes |\n | Merchant | telephone | Telephone of the merchant | Yes |\n | Merchant | category | [Place type](/maps/documentation/places/web-service/supported_types#table1) of the merchant | Nice to Have |\n | Merchant | action_link | Information regarding Merchant Specific Deep Links | Optional if Service feeds is provided, required otherwise |\n | Merchant | brand_id | String that identifies the consumer-facing brand to use | Optional |\n | Services | service_id | Unique Identifier of the service provided by the merchant | Yes (only if Service feed is provided) |\n | Services | merchant_id | Link to the Merchant which is providing this service | Yes (only if Service feed is provided) |\n | Services | localized_service_name | Name of the service provided | Yes (only if Service feed is provided) |\n | Services | localized_description | User-visible service description | Optional |\n | Services | action_link | Provides information about the service related deep links | Yes (only if Service feed is provided) |\n | Services | type | Type of Deep link (e.g. SERVICE_TYPE_DINING_RESERVATION) | Yes (only if Service feed is provided) |\n\n | **Note:** All additional fields outlined in the reference section should be ignored.\n | **Key Point:** You are only required to upload merchant feed.\n\n To start, check out the sample feeds\n - [Dining Reservation Feeds](/actions-center/verticals/dining/samples/end-to-end-feed-samples/vertical-specific-feeds/dining)\n - [Food Ordering Delivery Feed](/actions-center/verticals/dining/samples/starter-feed-samples/food-ordering-delivery)\n - [Food Ordering Pickup Feed](/actions-center/verticals/dining/samples/starter-feed-samples/food-ordering-pickup)\n - [Food Ordering Feeds with Metadata](/actions-center/verticals/dining/samples/starter-feed-samples/food-ordering-with-metadata)\n - [Retail Ordering Feeds](/actions-center/verticals/shopping/samples/starter-feed-samples/shopping)\n - [Retail Ordering Feeds with Metadata](/actions-center/verticals/shopping/samples/starter-feed-samples/shopping-with-metadata)\n - [In-Person Appointment Feeds](/actions-center/verticals?vertical_redirect_fragment=samples/starter-feed-samples/in-person-appointment)\n - [Online/Virtual Appointment Feeds](/actions-center/verticals?vertical_redirect_fragment=samples/starter-feed-samples/online-appointment)\n\n For Merchants who have multiple services, but are serving them using a\n single action link, you should provide a single action link for all services\n associated with a merchant in the merchants feed.\n\n You can learn more about specifying action links in the legacy starter integration\n feeds\n [here](/actions-center/verticals?vertical_redirect_fragment=guides/tutorials/tutorial-specifying-action-links).\n\n Include\n [feed metadata](/actions-center/verticals?vertical_redirect_fragment=reference/feed-specifications/feed-metadata) in each of your feeds that instructs Google on\n how to interpret the feed.\n\n The following is a feed metadata snippet: \n\n ```scdoc\n \"metadata\": {\n \"generation_timestamp\": \"1467993600\",\n \"processing_instruction\": \"PROCESS_AS_COMPLETE\",\n \"total_shards\": 1\n }\n ```\n | **Note:** All feeds must be uploaded with processing_instruction PROCESS_AS_COMPLETE. PROCESS_AS_INCREMENTAL is deprecated and cannot be used.\n | **Note:** The legacy starter integration can also be implemented in conjunction with an Actions Center end-to-end integration or as an add on to the end-to-end integration. In order to support this you will also be required to implement availability feeds and the end-to-end integration required fields as per this [guide](/actions-center/verticals?vertical_redirect_fragment=guides/end-to-end-integration/overview).\n2. **Export your feeds.** The feeds format is described with the\n [protocol buffer 3 syntax](/protocol-buffers/docs/proto3),\n however you can reference the samples mentioned above to see the JSON format.\n We recommend that you upload the feeds in JSON format.\n\n\n If you really want to proceed with pb3 format, for general information on how to use protocol\n buffers to generate a pb3 file, see\n [Protocol Buffer Basics: Java](/protocol-buffers/docs/javatutorial).\n3. **Upload the feeds to your SFTP server.** To upload your feeds, use\n the\n [SFTP server information](/actions-center/verticals?vertical_redirect_fragment=guides/starter-integration/setup#create-sftp-server) that Google provided to you and the\n private key that you created in\n [Setup](/actions-center/verticals?vertical_redirect_fragment=guides/starter-integration/setup#create-keys). The Google SFTP server is available at\n `sftp://partnerupload.google.com` on port `19321`.\n\n Upload your files with unique names, such as a name that includes a\n timestamp. Unique names help with troubleshooting and allow queries for\n the feed status.\n\n To determine the size of the feeds and frequency of delivery, use the\n following guidelines:\n - Size of feed files and shards:\n - Keep the feed file size below 200MB (after compression). Compress them using `gzip`\n - If your file may reach more than 200MB (after compression), split them in multiple shards following the [Sharding feed files](/actions-center/verticals?vertical_redirect_fragment=guides/tutorials/tutorial-sharding) tutorial. However, the legacy starter integration alone is unlikely to reach the 200MB limit.\n - Frequency of complete updates:\n - A complete merchant feed is provided once a day.\n - (If implemented) A complete service feed is provided once a day.\n\n | **Note:** Google processes feed files as soon as they're uploaded to the SFTP server. If the feed is sharded into multiple files, the process begins after you upload the last file. If your feed contains errors, you receive an email with the [feed error codes](/actions-center/verticals?vertical_redirect_fragment=reference/feed-specifications/feed-errors).\n\nGoogle evaluates feeds\n----------------------\n\nOnce you upload your feeds, Google processes and evaluates them for quality\nand completeness. We look at several factors:\n\n- Feeds meet the specifications.\n- Feeds include all required fields.\n- Each merchant has at least one `action_link` or one service with at least `action_link` defined.\n- The majority of your merchant data matches with Google Maps locations.\n\n| **Note:** To ensure a smooth integration, perform a pre-evaluation of the factors above, except for the last one, before you submit your feeds."]]
