Search
Clear search
Close search
Google apps
Main menu

Price Accuracy Report

The Price Accuracy report includes a set of sample data from your Hotel Price Feed. The data includes the prices that Google has and the prices on your website for some of your hotels/itineraries.

You can use the Price Accuracy report to help ensure adherence to Google's Price Accuracy Policy and Taxes and Fees Policy, and/or determine potential sources of price discrepancies. The report compares what a hotel "really" costs with what you "told" Google the hotel costs.

Note: Because the Price Accuracy report includes a subset of your Hotel Price Feed only, use it to detect patterns that might result in price accuracy issues. Do not use the Price Accuracy report as a comprehensive list of prices.

When you view the Price Accuracy report, compare the base rates as well as taxes and fees for a given hotel/itinerary that you supplied to Google (the Cached Price and Cached Tax values) to what Google fetched from your website (the Fetched Price and Fetched Tax values). If the fetched values are different than the cached values, Google can take the following actions:

  1. Flag the values as Price Accuracy Policy or Taxes and Fees Policy violations.
  2. Suspend the hotel.
  3. Lower your account's Price Accuracy Score.

To access the Price Accuracy report in Hotel Ads Center:

  1. Open Hotel Ads Center in a browser.
  2. Select the Tools tab. The Tools view displays.
  3. Select Prices > Accuracy Score in the left-hand navigation. The Price Accuracy Score view displays.
  4. Select the date to report on from the date drop-down list, or enter a custom date range. The default is "Last 7 Days".
  5. Click the Download button.

    Hotel Ads Center generates the report and saves it to your local storage as a CSV file.

    The Price Accuracy report contains a subset of your prices only. It is a representation of your Hotel Price Feed and not a comprehensive list.

The following table describes the columns in the Price Accuracy report:

Name Column name Description
Hotel ID hotel_id

The unique ID for the hotel that you use in your Hotel List Feed.

Check-in date check_in The first day of the itinerary, in YYYY-MM-DD format.
Length of stay nights The number of days for the itinerary.
Fetched price fetched_price The price per night of the given itinerary that Google fetched directly from your website. Google compares this value to the Cached Price to determine if your prices are accurately displayed in Hotel Ads as compared to on your website. If the values are very different (especially if the Fetched Price is higher than the Cached Price), Google might flag this as a price accuracy policy violation, suspend the hotel, and lower your account's Price Accuracy Score.

The value of Fetched Price is given in the Fetched Currency.

Fetched tax fetched_tax The total amount of taxes and fees for the given itinerary. Google compares this value to the Cached Tax to determine if your taxes and fees are accurately displayed in Hotel Ads as compared to on your website.

If the values are very different (especially if the Fetched Tax is higher than the Cached Tax), Google might flag this as a price accuracy policy violation, suspend the hotel, and lower your account's Price Accuracy Score.

Prices in the US and Canadian markets typically break out taxes and fees separately from the price. As a result, this value might be 0 for other markets. For more information, see Taxes and Fees Policy.

The value of Fetched Tax is given in the Fetched Currency.

Fetched currency fetched_currency

A three-letter currency code representing the currency that the Fetched Price and Fetched Tax are given in.

Fetched total price fetched_total_price  Total price (fetched), in local currency.
Fetched time fetched_time The date and time that Google gathered the Fetched Price, using the following format:
YYYY-MM-DDTHH:MM:SS[+|-]Z1:Z2
Where:
  • YYYY is the four-digit year
  • MM is the two-digit month
  • DD is the two-digit day of month
  • HH is the two-digit hours, using a 24-hour clock
  • MM is the two-digit minutes
  • SS is the two-digit seconds
  • [+|-] indicates if the timezone offset is positive or negative
  • T is a separator
  • Z1 is the two-digit number of hours in the timezone offset
  • Z2 is the two-digit number of minutes in the timezone offset
Feed price feed_price The price per night of the given itinerary that you supplied to Google in your Hotel Price Feed. Google compares this value to the Fetched Price to determine if your prices are accurately displayed in Hotel Ads as compared to on your website.

If the values are very different (especially if the Fetched Price is higher than the Cached Price), Google might flag this as a price accuracy policy violation, suspend the hotel, and lower your account's Price Accuracy Score.

The value of Cached Price is given in the Cached Currency.

Feed tax feed_tax The total amount of taxes and fees for the given itinerary. Google gets this value from its data cache, which contains the taxes and fees that you supplied with your Hotel Price Feed.

Google compares this value to the Fetched Tax to determine if your taxes and fees are accurately displayed in Hotel Ads as compared to on your website.

If the values are very different (especially if the Fetched Tax is higher than the Cached Tax), Google might flag this as a price accuracy policy violation, suspend the hotel, and lower your account's Price Accuracy Score.

Prices in the US and Canadian markets typically break out taxes and fees separately from the price. As a result, this value might be 0 for other markets. For more information, see Taxes and Fees Policy.

The value of Cached Tax is given in the Cached Currency.

Feed currency feed_currency

A three-letter currency code representing the currency that the Cached Price and Cached Tax are given in.

Total price total_price 

Total price (from feed), in local currency.

Feed time feed_time The date and time that Google received and stored the Cached Price (usually from your Hotel Price Feed), using the following format:
YYYY-MM-DDTHH:MM:SS[+|-]Z1:Z2
Where:
  • YYYY is the four-digit year
  • MM is the two-digit month
  • DD is the two-digit day of month
  • HH is the two-digit hours, using a 24-hour clock
  • MM is the two-digit minutes
  • SS is the two-digit seconds
  • [+|-] indicates if the timezone offset is positive or negative
  • T is a separator
  • Z1 is the two-digit number of hours in the timezone offset
  • Z2 is the two-digit number of minutes in the timezone offset

The value of Cached Time might not be when you most recently sent a pricing update to Google for the hotel/itinerary. It might reflect a different time if Google received a Live Query response from you for that hotel/itinerary.

Total price deviation total_price_deviation

The difference between (feed_price + feed_tax)  and  (fetched_price + fetched_tax). A positive percent indicates the fetched_price is greater than the feed_price.

Base price deviation base_price_deviation

The difference between feed_price and fetched_price. A positive percent indicates the fetched_price is greater than the feed_price.

Price freshness (hours) price_freshness_hrs

Fetched time minus feed time.

This is how fresh the price and is the difference between when we fetched (fetched_time), and the last time this price was updated (feed_time). This is a good column to use to spot patterns of prices or hotel IDs for which prices are stale.

Advance purchase window (days) advance_purchase_window_days

Check in minus fetched time.

This is the difference between when we fetched the price (fetched_time) and the check-in date for the itinerary (check_in). This is also a good column to use to spot patterns of prices or hotel IDs for which we have inaccurate prices

Corrected time corrected_time

The time that a price update that matched the one fetched from your web site was made.

For price inaccuracies, we will look at subsequent updates from your price feed to see if you have sent us the correct price at a later time.  If we detect that the the correct price update was sent to us after we have fetched the site, we will note the time that your feed updated and had the correct price. This should also be displayed in YYYY-MM-DDTHH:MM:SS[+|-]Z1:Z2.

NOTE: This field is new in version 2 of the Price Accuracy Report.
Incorrect updates incorrect_updates

The number of non-matching price updates that we received between when the price was fetched and either the corrected_time or when the price accuracy report was generated, whichever was earlier.

This column is useful when also considered against Corrected Time. If we have detected a correct price at a later time, and we saw intervening price updates that were incorrect, we aren't sure if your price feed is delayed, or if there are incorrect prices in the feed. In this case, we log the number of incorrect price feed updates between the time we fetched and the time we got the correct price.

NOTE: This field is new in version 2 of the Price Accuracy Report.
Mismatch reason mismatch_reason

A mismatch reason will be computed to be one of following reasons:

Price Feed Delayed: corrected_time is not null and incorrect_updates = 0

Price Feed Delayed, Incorrect Prices: corrected_time is not null and incorrect_updates > 0

Undetermined

URL url

The URL that Google used to get the values of the Fetched Price and Fetched Tax columns.

Deal deal Indicates whether or not a row represented a deal (the prices were low enough to be labelled as a good deal/offer).
NOTE: This field is new in version 2 of the Price Accuracy Report.
Rate Rule ID rate_rule_id

If a fetched price is associated with a fenced rate or Rate Rule, the ID of the rate rule appears in this column.

Hotel country hotel_country Indicates the country where the fetched hotel is located.

 

The following example shows the header and a single line of data from a sample Price Accuracy report:

Sample Price Accuracy Report
partner,hotel,check_in_date,length_of_stay,fetched_price,fetched_tax,
fetched_currency,fetched_time,cached_price,cached_tax,cached_currency,cached_time,
url
sample,3135,7/5/2015,1,222.39,0,BRL,2015-12-15T11:46:14-08:00,BRL,2015-12-15T11:46:14-08:00,
http://capyb1.sample.com/media/redir.php?p=977&c=192007&a=k27&destination=42
&di=05&mi=07&yearIn=2015&n=1&an=2&cn=0&mid=2

In a spreadsheet application, you might calculate the difference in prices and flag when the Fetched Price is not that same as the Cached Price. The following example divides the value of Fetched Price by Cached Price and highlights price accuracy issues in red in the "DIFF" column (which was added after the report data was imported into a spreadsheet application):

Was this article helpful?
How can we improve it?