3. Export feeds (you)

  1. Generate your feeds. You will transmit most of your inventory data to Google via feeds. To do this, create two types of feeds:

    1. Merchants feed: descriptions of your merchants. You can find an example of Merchants feed under Samples section. Please note, Merchants feed in Starter integration does not require tax_rate and it can be omitted.

    2. Services feed: services your merchants provide and action links to your platform. Take a look at posted Services feed sample as an illustration. Since Services feed primary function is to provide an action link to your website, the only fields that you would need to specify in the Services feed: service_id, merchant_id, type, action_link. Please note that fields name and description are optional in Starter integration and can be omitted.

    Include metadata in each feed that instructs Google on how to interpret the feed. Any field in the feed specification that is marked as optional can be left out.

    The messages used to describe these feeds align closely to schema.org's LocalBusiness and GeoCoordinates.

  2. Export your feeds. The feeds format is described using protocol buffer 3 syntax. You export the feed files in one of two ways:

    • Binary serialization of the protocol buffer data in pb3 format
    • Derived JSON format

    For general information on how to use the protocol buffers to generate a pb3 file, here is an example in Java.

  3. Upload the feeds to your SFTP Dropbox. Use the Google-provided SFTP Dropbox information from step 2 and the private key you created in step 1A. The Google SFTP server is available at sftp://partnerupload.google.com on port 19321.

    Upload your files with unique names (e.g. containing a timestamp). This action helps with troubleshooting and allows querying for feed status.

    Use the following guidelines to determine the size of the feeds and frequency of delivery:

    • Size of feed files and sharding:

      • Keep feed file size below 200MB, and use multiple shards if needed
      • At present we support a maximum of 1000 shards per feed
      • Individual records sent in one shard, doesn't necessarily have to be sent in the same shard in future feeds.
      • For better performance, data should be split fairly among the shards, making all sharded files similar in size.
    • Frequency of complete updates:

      • Merchants feed: a complete feed once per day
      • Services feed: a complete feed once per day

Have questions?

Be sure to check out our FAQs.

Next step

NEXT STEP: Evaluate feeds (Google)