The empty destination (airport, city or country) is caused by MULTI-CITY trips. For multi-city we can’t definitively say what the person’s destination is (e.g. if they travel MEL-SYD-DPS-MEL was their destination SYD, DPS or MEL?). So partners are encouraged to use leg/segment information for every search / redirect to define their own logic in the case of multi-city trips.
Articles in this section
- Are all segment and leg location codes in IATA?
- How do I handle invalid characters in the csv files?
- Why does my historical data contain empty columns?
- What is a session ID?
- What is a correlation ID?
- How big is the file size for the TI raw data?
- Can we receive historical data in v5 format?
- How can we add and remove fields to the reports?
- There is a small volume difference between Partner portal redirects and Travel Insights reports redirects (about 5-7%). Why is that?
- We found around 2% of destinations are missed in routes and destination country according to TI redirect data, could you please help confirm why this happened?
Comments
0 comments
Please sign in to leave a comment.