Step 2: Implementing the feeds

AI-generated Key Takeaways

• To integrate your feed, generate and export your event feeds and descriptor files in JSON format using the protocol buffer 3 syntax.

• Upload your feeds to the provided Google SFTP server using unique file names and follow guidelines for file size and update frequency.

• Google evaluates uploaded feeds for quality and completeness based on specifications, required fields, and venue data matching Google Maps locations.

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

1. 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.

   • Event feed: Describes your events.
   • Descriptor file: Provide metadata about your feed such as timestamp, feed type and list of files to be transmitted in the set.

2. 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.

3. 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.
   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.

Google evaluates feeds

Once you upload your feeds, Google processes and evaluates them for quality and completeness. We look at several factors:

• Feeds meet the specifications.
• Feeds include all required fields.
• Venue data matches with Google Maps locations.

Note: To ensure a smooth integration, perform a pre-evaluation of these factors, except for the last one, before you submit your feeds.