[null,null,["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003eLocal Services Ads Redirect integration requires regular data feeds to Google, including Entity and Action feeds, which are updated daily.\u003c/p\u003e\n"],["\u003cp\u003eFeeds must adhere to content guidelines, use protocol buffer 3 syntax or JSON format, and be uploaded to a designated SFTP Dropbox.\u003c/p\u003e\n"],["\u003cp\u003eGoogle evaluates submitted feeds for quality, completeness, and adherence to specifications, including required fields and data matching.\u003c/p\u003e\n"],["\u003cp\u003eEach merchant must have at least one action link and one service with at least one action link defined for successful integration.\u003c/p\u003e\n"],["\u003cp\u003ePre-evaluation of feeds is recommended before submission to ensure a smooth integration process with Google's systems.\u003c/p\u003e\n"]]],["This content details the Local Services Ads Redirect integration process, requiring two feeds: Entity and Action, updated every 24 hours. Feeds, in protocol buffer or JSON format, describe entities and associated deep links. Upload feeds via SFTP to `sftp://partnerupload.google.com:19321` using unique file names and fileset descriptor files, specifying `reservewithgoogle.entity` or `reservewithgoogle.action.v2`. Upload to the sandbox environment first. Google evaluates feeds for specification adherence, completeness, and merchant data matching. Ensure you pre-evaluate your feeds before submission.\n"],null,["# Using the Generic feed SFTP server\n\nThe following describes the details of the Actions Center integration\nprocess that are unique to Local Services Ads Redirect.\n\nKey Guidance\n------------\n\nThe following are examples and tutorial covering features that are required by\nthe Local Services Ads Redirect integration:\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| [Entity](/actions-center/verticals/local-services/redirect/reference/feeds/entity-feed) | Describes your entities. | Once every 24 hours |\n| [Action](/actions-center/verticals/local-services/redirect/reference/feeds/action-feed) | Describes your deep links associated with your entities. | Once every 24 hours |\n\n| **Objective:** When you provide service names and descriptions, adhere to our [Content editorial guidelines](/actions-center/verticals/local-services/redirect/support#content-editorial-guidelines).\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.\nPlease reference the feed samples below\n\n- [Entity Feed](/actions-center/verticals/local-services/redirect/reference/feeds/entity-feed)\n- [Action Feed](/actions-center/verticals/local-services/redirect/reference/feeds/action-feed)\n\nWe recommend that you upload the feeds in JSON format.\n\n\u003cbr /\u003e\n\nUpload the feeds to your 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/local-services/redirect/partner-portal/testing/feeds) page. The Google SFTP server is\navailable at `sftp://partnerupload.google.com` on port\n`19321`.\n| **Note:** To access the sandbox, make sure that the [environment switcher](/actions-center/verticals/local-services/redirect/partner-portal/overview/environment-switcher) on the top is set to Sandbox.\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:** All feeds should be uploaded to the **Generic** SFTP server.\nEnsure you are uploading all feeds to the 'Generic' account.\n\n\nEach feed needs to be uploaded through SFTP separately with a fileset descriptor file.\nThe filename of a fileset descriptor should be **\\\u003cfeed_name\\\u003e-\\\u003c\ngeneration_timestamp\\\u003e.filesetdesc.json** ,\nin which **\\\u003cfeed_name\\\u003e** should correspond to the following for each feed:\n\n| Feed | FilesetDescriptor.name |\n|--------|-------------------------------|\n| Entity | `reservewithgoogle.entity` |\n| Action | `reservewithgoogle.action.v2` |\n\n\u003cbr /\u003e\n\n\nVisit [Using the Generic feed SFTP server](/actions-center/verticals/appointments/redirect/reference/tutorials/generic-sftp)\nfor more information.\n| **Warning:** Upload your feeds to the production servers only after Google has tested and confirmed your feeds in the sandbox environment.\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` and 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."]]
