Migrating to Things to do v1 feed specification

Existing Things to do partners on Reserve with Google can migrate to the new Things to do platform by following the steps below.

1. Development and testing

The things to do processing pipeline automatically recognizes v1 feed spec format. You can develop and upload feeds in the new v1 format at anytime to partnerdev environment. To try out the v1 format, you can download this sample JSON file and upload it to your endpoint.

Once processed, successfully loaded products as well as warnings & errors will be surfaced in the Things to Do Center.

2. Validating your new feed before uploading to production

Follow these steps to validate your new feed before uploading to production:

  1. Upload to partnerdev environment the latest production data in the old feed format.

  2. Once processing is complete, upload to partnerdev environment the feed in the new v1 feed format.

  3. Once processing is completed, check in the Things to Do Center under products section the following:

    • No. products updated should be the same or very close to Total.
    • No. products removed should be 0 or close to 0.
    • No. products added should be 0 or close to 0.
  4. Reach out to Google for a final review: Google will review the v1 feed in the partnerdev environment in order to ensure a smooth transition. Once confirmed, the production environment will be configured to receive the v1 spec. The following will be reviewed by Google:

    • Correct mapping between old and new products feeds (product id, title etc.).
    • Correctness of related_locations, inventory_type, operator vs existing feed and tagged results.
    • Language/currency are handled correctly by URL endpoint.

3. Uploading new feed to production

Once Google has confirmed the feed and allowlisted you for v1, you can upload the new feed to production as you would with the existing feed. Things to do processing will automatically recognize the new feed format and process accordingly.

4. Enabling automated location matching

Once the feed is uploaded to production, Google team will perform an additional internal review. When location & ticket information provided in the feed is validated for correctness and relevance, we'll enable it to be used for serving relevant products.

5. Transitioning from multiple services to single product with multiple options

Due to limitations of the previous spec, you may want to rework multiple services into a single product with multiple options. You can freely do that once you have performed the initial migration and have been flagged as a trusted partner.

6. Rolling back to v0 feed spec

If issues are detected in production with the new feed spec and more development work is required, you can roll back to the old feed format at any time by re-uploading a previous data snapshot in the old format.