[null,null,["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003eYou need to create Merchant feeds (and optionally Services feeds, though not recommended) to transmit your inventory data to Google.\u003c/p\u003e\n"],["\u003cp\u003eFeeds must be in JSON or Protocol Buffer 3 format, uploaded to your Google SFTP Dropbox, and uniquely named, ideally with a timestamp.\u003c/p\u003e\n"],["\u003cp\u003eGoogle evaluates the feeds for quality, completeness, and adherence to specifications, including required fields and matching with Google Maps locations.\u003c/p\u003e\n"],["\u003cp\u003eEach merchant must have at least one \u003ccode\u003eaction_link\u003c/code\u003e or one service with at least \u003ccode\u003eaction_link\u003c/code\u003e defined within the feeds for successful processing.\u003c/p\u003e\n"],["\u003cp\u003ePre-evaluation of your feeds before submission is strongly recommended to ensure a smooth integration process.\u003c/p\u003e\n"]]],["Generate a Merchant feed containing merchant data like ID, name, geo-location, telephone, category, and action links; a Services feed is optional and not recommended. Export feeds using protocol buffer 3 syntax or JSON format, preferably. Upload feeds to Google's SFTP dropbox, ensuring unique file names and file sizes under 200MB (compressed). A complete Merchant feed, and Service if applicable, must be provided daily. Google then evaluates the uploaded feeds for specification adherence, required fields, action links, and Google Maps data matching.\n"],null,["Overview\n\nThis section provides details about the feed files required to transmit inventory data to Google. The contents of your feeds define the services that you provide and the services that are available to consumers.\n| Note: If you use the legacy redirect schema, then follow the instructions in the [archive](/actions-center/verticals/ordering/redirect/reference/action-link-feeds/overview) section.\n\nYou need to create the following feed files and upload them to the Actions Center in both sandbox and production environments.\n\n| Feed | Description | Frequency |\n|--------------------------------------------------------------------------------------------------|----------------------------------------------------------|----------------------|\n| [Entity](/actions-center/verticals/ordering/redirect/reference/feeds/entity-feed) | Describes your merchant entity. | Once every 24 hours. |\n| [Action](/actions-center/verticals/ordering/redirect/reference/feeds/action-feed) | Describes your deep links associated with your entities. | Once every 24 hours. |\n| [Services (Optional)](/actions-center/verticals/ordering/redirect/reference/feeds/services-feed) | Describes services your merchants provide. | Once every 24 hours. |\n\n\nThe following diagram shows how service, restaurant, and action entities represent a single restaurant.\n\n\nImplement real time updates (Optional)\n\nRTUs are primarily intended for updates that are not predictable, such as emergency closures or metadata that changes periodically (such as ETAs).\nIf your change doesn't need to be reflected immediately, you can use batch feed ingestion instead. Real-time updates are processed within five minutes.\nFor more information, see [Real time update](/actions-center/verticals/ordering/redirect/integration-steps/action-link-feeds/real-time-update)."]]
