Stay organized with collections
Save and categorize content based on your preferences.
Implement your feed against our reference documentation. The sandbox environment is available for
you to upload and test your feed at any time.
Create feeds
Generate your feed(s). You transmit most of your inventory data to Google by feeds. To
get started, create your Events JSON feed and a JSON descriptor file.
Descriptor file:
Provide metadata about your feed such as timestamp, feed type and list of files to be
transmitted in the set.
Export your feeds. The feeds format is described with the
protocol buffer 3 syntax, however you can
reference the samples to see the JSON format. We recommend that you upload the feeds in JSON
format.
Upload the feeds to your SFTP server. To upload your feeds, use the
SFTP server information
that Google provided to you and the private key that you created in
Setup. The Google SFTP server is available at sftp://partnerupload.google.com on port
19321.
Upload your files with unique names, such as a name that includes a timestamp. Unique names
help with troubleshooting and allow queries for the feed status.
To determine the size of the feeds and frequency of delivery, use the following guidelines:
Size of feed files and shards:
Keep the feed file size less than 200MB (after compression). Compress them using
gzip
If your file may reach more than 200MB (after compression), split them in multiple
shards following the
Sharding feed files
tutorial. However, this integration alone is unlikely to reach the 200MB limit.
Frequency of complete updates:
A complete event feed is provided at least once a day.
Google evaluates feeds
Once you upload your feeds, Google processes and evaluates them for quality and completeness. We
look at several factors:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-20 UTC."],[[["\u003cp\u003eTo integrate your event ticketing data with Google, you need to create and upload three feeds: Merchant, Service, and Availability.\u003c/p\u003e\n"],["\u003cp\u003eThese feeds must be in JSON format, compressed using gzip, and uploaded to Google's SFTP server.\u003c/p\u003e\n"],["\u003cp\u003eEach feed has required fields that must be populated correctly for Google to process the data; ensure data accuracy and completeness before uploading.\u003c/p\u003e\n"],["\u003cp\u003eGoogle evaluates submitted feeds based on data quality, completeness, and compliance with specifications to ensure smooth integration.\u003c/p\u003e\n"],["\u003cp\u003eYou can find detailed information about feed specifications, required fields, and troubleshooting in the provided documentation links within the content.\u003c/p\u003e\n"]]],["To integrate, create and upload three feeds: `Merchant` (venue details), `Service` (event details), and `Availability` (event availability). Each feed has required fields; for example, `Merchant` needs `merchant_id`, `name`, and `geo.address`; `Service` requires `service_id`, `merchant_id`, and `localized_service_name`. Upload the JSON-formatted feeds to Google's SFTP server, ensuring files are under 200MB and using unique names. Feeds must include metadata and be delivered completely at least once a day. Google then evaluates them for quality and completeness.\n"],null,["# Step 2: Implementing the feeds\n\nImplement your feed against our reference documentation. The sandbox environment is available for\nyou to upload and test your feed at any time.\n\nCreate feeds\n------------\n\n1.\n **Generate your feed(s).** You transmit most of your inventory data to Google by feeds. To\n get started, create your Events JSON feed and a JSON descriptor file.\n\n - [`Event feed`:](/actions-center/verticals/events/reference/v1-feed/feed-spec#event-feed) Describes your events.\n - [`Descriptor file`:](/actions-center/verticals/events/reference/v1-feed/feed-spec#descriptor-file) Provide metadata about your feed such as timestamp, feed type and list of files to be transmitted in the set.\n2.\n **Export your feeds.** The feeds format is described with the\n [protocol buffer 3 syntax](/protocol-buffers/docs/proto3), however you can\n reference the samples to see the JSON format. We recommend that you upload the feeds in JSON\n format.\n\n3.\n **Upload the feeds to your SFTP server.** To upload your feeds, use the\n [SFTP server information](/actions-center/verticals/events/integration-steps/setup#create-sftp)\n that Google provided to you and the private key that you created in\n [Setup](/actions-center/verticals/events/integration-steps/setup#create-keys). The Google SFTP server is available at `sftp://partnerupload.google.com` on port\n `19321`.\n\n\n Upload your files with unique names, such as a name that includes a timestamp. Unique names\n help with troubleshooting and allow queries for the feed status.\n\n\n To determine the size of the feeds and frequency of delivery, use the following guidelines:\n - Size of feed files and shards:\n - Keep the feed file size less than 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/events/reference/tutorials/sharding) tutorial. However, this integration alone is unlikely to reach the 200MB limit.\n - Frequency of complete updates:\n - A complete event feed is provided at least 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/events/reference/feeds/feed-errors).\n\nGoogle evaluates feeds\n----------------------\n\n\nOnce you upload your feeds, Google processes and evaluates them for quality and completeness. We\nlook at several factors:\n\n- Feeds meet the specifications.\n- Feeds include all required fields.\n- Venue data matches with Google Maps locations.\n\n| **Note:** To ensure a smooth integration, perform a pre-evaluation of these factors, except for the last one, before you submit your feeds."]]