Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Devi prima creare i feed, poi Google li valuta.
Creare feed
Genera i tuoi feed. Trasmetti la maggior parte dei dati di inventario a Google tramite feed. Per iniziare, crea il feed dei tuoi prodotti (e il feed dei servizi, se applicabile):
Feed dei commercianti:il feed dei commercianti descrive i tuoi commercianti e i link alle azioni a livello di commerciante.
Feed di servizi(facoltativo / non consigliato):
non è consigliabile implementare i feed di servizi per le nuove integrazioni di Link per le prenotazioni aziendali.
Se vuoi mantenere l'integrazione esistente, segui
questa documentazione precedente.
Campi obbligatori e consigliati
Feed
Nome campo
Descrizione
Obbligatorio?
Commerciante
merchant_id
Identificatore univoco del commerciante
Sì
Commerciante
nome
Nome del commerciante
Sì
Commerciante
geo
Indirizzo e coordinate geografiche del commerciante
Esporta i tuoi feed. Il formato dei feed è descritto con la
sintassi di Protocol Buffer 3,
tuttavia puoi fare riferimento agli esempi sopra indicati per visualizzare il formato JSON.
Ti consigliamo di caricare i feed in formato JSON.
Se vuoi procedere con il formato pb3, per informazioni generali su come utilizzare i buffer di protocollo per generare un file pb3, consulta Nozioni di base sui buffer di protocollo: Java.
Carica i feed sul tuo server SFTP. Per caricare i feed, utilizza
le
informazioni sul server SFTP che ti sono state fornite da Google e la
chiave privata che hai creato in
Configurazione. Il server SFTP di Google è disponibile all'indirizzo
sftp://partnerupload.google.com sulla porta 19321.
Carica i file con nomi univoci, ad esempio un nome che includa un
timestamp. I nomi univoci sono utili per la risoluzione dei problemi e consentono di eseguire query sullo stato del feed.
Per determinare le dimensioni dei feed e la frequenza di invio, segui le seguenti linee guida:
Dimensioni dei file e dei frammenti del feed:
Mantieni le dimensioni del file del feed inferiori a 200 MB (dopo la compressione). Comprimili utilizzando gzip
Se il file potrebbe raggiungere più di 200 MB (dopo la compressione), suddividilo in più
shard seguendo il tutorial su come eseguire lo sharding dei file del feed
. Tuttavia, è improbabile che questa integrazione da sola raggiunga il limite di 200 MB.
Frequenza degli aggiornamenti completi:
Viene fornito un feed completo del commerciante una volta al giorno.
(Se implementato) Un feed del servizio completo viene fornito una volta al giorno.
Google valuta i feed
Una volta caricati, Google li elabora e valuta per verificarne la qualità
e la completezza. Prendiamo in considerazione diversi fattori:
I feed soddisfano le specifiche.
I feed includono tutti i campi obbligatori.
Ogni commerciante ha almeno un action_link o un servizio con almeno action_link definito.
La maggior parte dei dati del commerciante corrisponde alle sedi su Google Maps.
[null,null,["Ultimo aggiornamento 2025-07-26 UTC."],[[["\u003cp\u003eCreate and upload Merchant feeds daily to provide Google with your restaurant data, including location, contact details, and a deep link for reservations.\u003c/p\u003e\n"],["\u003cp\u003eEnsure your feeds adhere to the provided specifications, include all required fields, and are in JSON format for optimal processing.\u003c/p\u003e\n"],["\u003cp\u003eGoogle will then evaluate your feeds for quality, completeness, and accuracy against Google Maps locations.\u003c/p\u003e\n"],["\u003cp\u003eWhile optional, consider providing a \u003ccode\u003ecategory\u003c/code\u003e field using Google's Place types and a \u003ccode\u003ebrand_id\u003c/code\u003e to enhance your listing.\u003c/p\u003e\n"],["\u003cp\u003eUse the SFTP dropbox provided by Google to upload your feeds, ensuring file sizes remain below 200MB after gzip compression.\u003c/p\u003e\n"]]],["To transmit inventory data, you must first generate a Merchant feed (and optionally a Services feed, though not recommended for new integrations). The Merchant feed, containing merchant details and action links, is required; other fields are optional. You'll then export the feed, preferably in JSON format, and upload it to Google's SFTP dropbox, using unique file names. Google will process it as soon as the last file is uploaded. Once they are uploaded, Google will evaluate your feed.\n"],null,["# Step 2: Feeds\n\nFirst you need to create your feeds, then Google evaluates them.\n\nCreate feeds\n------------\n\n1. **Generate your feed(s).** You transmit most of your inventory data to\n Google by feeds. To get started, create your Merchant feed (and Services feed if applicable):\n\n - [Merchants feed:](/actions-center/verticals/reservations/bl/reference/feeds/merchants-feed) The Merchants feed describes your merchants and merchant level action links.\n - [Services feed](/actions-center/verticals/reservations/bl/reference/feeds/services-feed) **(optional / not recommended)** : It is not recommended to implement services feeds for new Reservations Business Link integrations. If you are looking to maintain your existing integration, follow [this legacy documentation](/actions-center/legacy/archived-guides/starter-integration-feeds).\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 | Yes |\n | Merchant | action_link_type | Type of link action. Reservations Business Link partners should use `ACTION_LINK_TYPE_MAKE_DINING_RESERVATION`. |\n | Merchant | brand_id | String that identifies the consumer-facing brand to use | Optional |\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/reservations/bl/reference/feeds/merchants-feed#samples)\n\n You can learn more about specifying action links in Reservations Business Link integration\n feeds\n [here](/actions-center/verticals/reservations/bl/reference/tutorials/specifying-action-links).\n\n Include 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:** This integration can also be implemented in conjunction with the Actions Center end-to-end integration or as an addon 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/reservations/bl/policies/platform-policies#merchant_and_service_eligibility).\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/reservations/bl/integration-steps/setup#create-sftp) that Google provided to you and the\n private key that you created in\n [Setup](/actions-center/verticals/reservations/bl/integration-steps/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/reservations/bl/reference/tutorials/sharding) tutorial. However, this 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/reservations/bl/reference/feeds/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."]]
