TR payload is the reflection of what a user would see in the UI when they search for tickets. If some results come from the Skyscanner cache, then the same results are sent in TR. It's similar to results retrieved from live responses.
Articles in this section
- What dimensions can we filter the data with?
- Where does Skyscanner get the currency and how often does it get reloaded?
- What is the difference between "position" and "rank"?
- Why does TR feed has searches with identical correlation ID, but varying uuids?
- Why do I see mismatch between TI and TR data sets itinerary position mismatch?
- Why do I see a mismatch between TI and TR datasets?
- Can we link searches data in Travel Insight reports to TR search events?
- Why am I getting several partner_quote_ids per search (uuid) while I expect a single value?
- Why am I getting null in some partner_quote_id I received?
- What kind of granularity does partner_quote_id have?
Comments
0 comments
Please sign in to leave a comment.