In light of COVID-19, please review the latest announcement regarding the Reserve with Google guidelines for supporting users and merchants during this time. Additionally, since we are operating with a limited support team, it may take longer to connect with us. Thank you for your patience, and we value your partnership.

Introduction to deals

Partners participating in the deals integration must complete the account setup step before they begin. The implementation, testing, and launch of the deals integration will be detailed in this guide. Read through this overview and deals policies before going through the integration steps.

Deals

The deals integration allows you to relay structured information about merchant promotions and discounts applied to specific services at specific times. Deals are made up of the actual deal (percent-off, dollar-off, etc), validity windows (specific times, days of the week, etc), and applicable uses (the deal can only be used on certain services).

Examples of deals:

  • Half-off appetizers on Wednesdays and Thursdays in December from 12pm to 5pm
  • Buy one get one dessert free for Mother’s Day dinner from 6pm to 10pm
  • $5 off a brunch entree every Sunday from 10am to 2pm

In order for a deal to be included in the integration, it needs to fit within the technical data model as well as meet our eligibility requirements. Please make sure to review our deals policies to ensure your integration is in compliance and for instructions on what to do with deals that do not fit the technical requirements.

Deals implementation

The deals integration consists of three feeds that will be uploaded daily:

All three feeds must be uploaded daily and contain all data (not just new or changed data). Any previously uploaded data that is not included in the latest feed upload will be deleted.

Feed file sizes and upload frequency

  • Keep feed file size below 200 MB (after compression). Use multiple shards if needed.
  • Most integrations will only need to use a single shard. You should use as few shards as possible. There is a maximum of 1000 shards per feed.
  • Individual records sent in one shard don't need to be sent in the same shard number in future feeds.
  • For better performance, split data evenly among the shards, to make all the shard files similar in size.
  • If necessary, use gzip to compress plain text JSON feeds. However, do so for each individual feed shard.

End to end booking with deals

Deals can be used in the Reserve with Google end-to-end booking integration. If you are also a Reserve with Google partner, you will need to also complete the end-to-end integration and integrate the deals into your booking server. If you are not a Reserve with Google end-to-end partner, this does not apply to your integration.

Development & launch process

Throughout your integration, the Partner Portal will be able to assist you with information and feedback based on your development. The development process will follow this flow:

  • The integration will be first developed in the Sandbox environment. You should be using an export of production (or even production data directly) in the Google Sandbox environment. This helps ensure that your development catches all edge cases and allows Google to evaluate data quality and better assist you based on your data model.
  • Once you are uploading complete and daily Merchant, Services, and Deals feed consistently in the Google Sandbox environment the Google team will evaluate your feeds. Once the Google team provides approval, you can push your code to production and begin sending production data to the Google Production environment.
  • After you have fully tested the Production integration the Google team will test as well. Once all testing is complete, then your integration will launch.