Sending conversion data via Generic feeds

This guide explains how partners can provide Reserve with Google information regarding transactions which are completed via place action links.

This guide is only applicable to Reserve with Google Starter integration partners who provide action_link(s) which allow users to perform the following actions:

  • Make an online appointment
  • Complete a shopping transaction

Conversion data for tracking

In order to provide Google information about assisted conversions, partners must upload a Conversion feed on a daily cadence. This feed can be uploaded alongside Merchant and/or Service feeds uploads. You are required to upload conversion data for all action links which are currently being provided via the Merchant and/or Services feeds. Each feed upload can contain data for the last 30 days.

If a conversion value for a particular action_link changes after the initial upload, you can upload the new value as part of the next feed upload. The latest data uploaded via feeds will be considered the source of truth and will be merged with the previously submitted data.

For instances when there is no conversion data for an action_link, we recommend that you include information about the link with the conversion data values set as 0 for that date.

Conversion data for action link(s) can be collected in multiple ways and is based on your preference, the preferred way is by appending UTM parameters to your URL which indicates this link originated from the action_link provided in your feeds.

The Conversion feed will be uploaded to the Generic feed dropbox. Follow the How to use the Generic feed dropbox tutorial for instructions and use the name set to the exact string reservewithgoogle.conversion_data in your descriptor file.

For conversion data tracking, we require you to upload the following information for the last 30 days per merchant via the feeds:

  • url - Identifier for which action_link the information is being provided.
  • num_transactions - Total number of assisted transactions via action_link(s). Examples of transactions include the user performing the following actions:

    • place an order
    • make a reservation
    • book an appointment
  • num_visits - Number of visits to the merchant’s landing page from action_link(s). These visits may or may not have an associated transaction.

Feed samples for conversion tracking can be found here.


For partners providing us with Medical inventory, you are required to adhere to these additional requirements when providing us with conversion data.

  • You need to only provide a single entry per day which contains aggregated data for all participating merchants combined.

  • url - Do not provide.

  • num_transactions - Provide the number of transactions, aggregated for all merchants, only if there are more than 50 transactions. Do not provide if less.

  • num_visits - Provide, aggregated for all merchants, the number of visits to the merchant's landing page. The visit may or may not have an associated transaction.