Feeds overview
Stay organized with collections
Save and categorize content based on your preferences.
This section specifies the feed files used to transmit your
inventory data to the Actions Center. The contents of your feeds defines
which services you are providing and what services are available.
The structure of the inventory feeds are defined by the Google Maps Booking
API.
The following feeds are mandatory for the Local Services Ads Redirect integration:
- Action feed: Contains data describing your deep links associated with your entities.
Some fields in these feeds are required and some are optional. Any field
marked as optional can be left out of the feed when empty.
The feeds format is described using protocol buffer 3 syntax. You have the
option to upload the feeds file as a binary serialization of the protocol
buffer data in pb3 format or in a derived JSON format.
We recommend uploading the feeds in JSON format.
We recommend using
gzip to compress feeds prior to upload.
This guide is specific to the Actions Center protocol buffers. For
general information on how to use the protocol buffers to generate a pb3
file,
here is an example in Java.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-05-20 UTC.
[null,null,["Last updated 2025-05-20 UTC."],[[["\u003cp\u003eInventory data is transmitted to Actions Center using specific feed files, defining available services.\u003c/p\u003e\n"],["\u003cp\u003eMandatory feeds include Entity (describing your business entities) and Action (describing associated deep links).\u003c/p\u003e\n"],["\u003cp\u003eFeeds can be formatted as protocol buffer 3 syntax in pb3 or JSON, with JSON recommended.\u003c/p\u003e\n"],["\u003cp\u003eWhile optional fields can be omitted, required ones must be included for successful data transmission.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends using gzip compression for feeds before uploading to optimize the process.\u003c/p\u003e\n"]]],["Inventory data is sent to the Actions Center via feed files, which define service offerings. Mandatory feeds for Local Services Ads Redirect integration include the Entity feed (describing entities) and the Action feed (describing entity deep links). Fields can be required or optional. Feeds use protocol buffer 3 syntax and can be uploaded as binary or JSON; JSON is recommended. Gzip compression is advised before upload. The feeds format is defined by the Google Maps Booking API.\n"],null,["# Feeds overview\n\nThis section specifies the feed files used to transmit your\ninventory data to the Actions Center. The contents of your feeds defines\nwhich services you are providing and what services are available.\n\nThe structure of the inventory feeds are defined by the Google Maps Booking\nAPI.\n\nThe following feeds are mandatory for the Local Services Ads Redirect integration:\n\n- **[Entity feed](/actions-center/verticals/local-services/redirect/reference/feeds/entity-feed):** Contains data describing your entities.\n\n\u003c!-- --\u003e\n\n- **[Action feed](/actions-center/verticals/local-services/redirect/reference/feeds/action-feed):** Contains data describing your deep links associated with your entities.\n\nSome fields in these feeds are required and some are optional. Any field\nmarked as optional can be left out of the feed when empty.\n\nThe feeds format is described using protocol buffer 3 syntax. You have the\noption to upload the feeds file as a binary serialization of the protocol\nbuffer data in [pb3 format](/protocol-buffers/docs/proto3) or in a derived JSON format.\nWe recommend uploading the feeds in JSON format.\n\nWe recommend using\n[gzip to compress feeds](/actions-center/verticals/local-services/redirect/reference/tutorials/compression) prior to upload.\n\nThis guide is specific to the Actions Center protocol buffers. For\ngeneral information on how to use the protocol buffers to generate a pb3\nfile,\n[here is an example in Java](/protocol-buffers/docs/javatutorial)."]]