All Collections
Frequently asked questions
How does Triptease access accurate pricing data for hotels?
How does Triptease access accurate pricing data for hotels?
Holly Groom avatar
Written by Holly Groom
Updated over a week ago

Being in parity with OTAs can mean the difference between a booking taking place on your website, and a booking being made via an OTA. Staying in parity requires continuous monitoring of your own hotels’ prices versus those of the OTAs you partner with. If you participate on metasearch you’ll also need to monitor a whole range of smaller OTAs who are also displaying your prices there.

The backbone of the Triptease Data Marketing Platform is parity data. We analyze 7 billion prices a year which allows us to provide parity monitoring and insights that would be impossible to gather manually.

Here’s how we get the parity data that you see in the Triptease Data Marketing Platform:

  • A potential customer makes a search on a hotel booking engine.

  • Triptease gathers pricing data for that search from OTA website in real time via advanced web scraping functionality.

  • Those prices are then displayed in a Price Check Message on the hotel website (if the hotel has a set up a Price Check Message) to reinforce to the customer that the hotel has the best price.

  • All OTA and direct hotel price data is then aggregated in the Parity Manager too, so the hotel team can analyse the overall parity health and identify patterns or insights in their data.

Because Triptease’s parity scraping is triggered by a real customer search on the hotel booking engine, the resulting data is a ‘search wighted’ view on rate parity. This means that the pricing data we gather matches one-to-one with searches made on the hotel website. This gives you a very precise view on which undercuts are influencing guest booking decisions in real time!

How is metasearch pricing data different?

Metasearch parity data is gathered in a different way - here we regularly check OTA rates prices on meta for stay dates within the next 30 days (for DMP core) and within the next 90 days (for DMP Pro), up to 7 nights length of stay. This means you have a constantly updated feed of data within that window.

Did this answer your question?