Write permission is used to be able to upload the file to the partner's S3 bucket or SFTP server. With this missing, we won't be able to deliver the report.
Read permission is used to validate if the file has been received on the partner's S3 bucket or SFTP server. With this missing, we won't be able to verify if the file has been successfully delivered.
2. How big is the file size for the TI raw data?
|Type of Data||Compressed Size||Uncompressed Size|
|Historical data||You need to allow at least 200GB for a whole year's worth of data|
3. How do we handle multi city flights?
We only include multi city flights with 3 legs. Anything more than that is excluded from our search.
4. Can I retrieve the files in a weekly or monthly fashion rather than a daily feed?
Unfortunately, we only provide daily feeds at the moment. Each file can be quite big in size already, so having each file daily will mean that they can be opened in Excel.
5. What is a correlation ID?
The correlation ID is a unique 36 character long ID (e.g. a7c638e2-a1c6-44c7-abfb-807025150f71) that appears in both Search and Redirect Reports when enabled in the subscription manager. As the name suggests, it helps Partners to simply correlate the relationship between search and redirect volumes to uncover how well-served a market or route is.
6. Is Correlation ID available for historical reports?
The correlation ID is available in historical reports after the date it was released i.e. 20 Aug 2019 onwards. You will have to enable Correlation ID in the subscription to get new historical reports generated with the CID.
7. What is a session ID?
The session ID is a unique 44 character long ID (e.g. RNAV4JG5WZZihmw5SSBjidxj1uxJKlG88PLsU9GrfpU) that appears in both Search and Redirect Reports when enabled in the subscription manager. This feature enables Partners to perform a range of analysis such as identify traveller search behaviour in finalizing route for specific journeys/route substitution effect. This helps partners to provide better route planning and pricing specific routes in order to capture the market share. Travellers will indirectly benefit from this feature since they would get better choices for their journey and potentially lower prices on desired routes.
8. Is Session ID legally approved?
Yes, Legitimate Interest Assessment was done by Legal before we released this feature into production. Documents available in case required.
9. Can I filter for the historical data?
Unfortunately, we do not provide any filtering for historical data as this historical data has been pre-generated from our our older versions of Travel Insight. Sending this data in its entirety mean that partners will have to sieve out what is relevant to them.
10. Why does my historical data contain empty columns?
The current Travel Insight offers more data columns than the previous generations of Travel Insight. Since historical data is pregenerated from older versions of Travel Insight, there are missing values for fields that have just been added in this new version.
11. Why does the feed's numbers not match the Partner Portal's?
The Partner Portal's numbers should match the Travel Insight feed data. The subscription could be misconfigured to send a sampled feed, which can cause mismatched numbers when attempting to compare the data between Travel Insight and Partner Portal.
12. Is Facilitated Booking (direct booking) data included in the TI exit results?
13. How do I handle invalid characters in the csv files?
Values with commas in them are wrapped around double quotes ("")
14. Are all segment and leg location codes in IATA?
No, there is a small percentage of locations without IATA code (e.g. Crete, Phuket). For this scenario, we are using the Skyscanner City Code.
15. What are sampled data sets?
Sampled data sets are based on routes (origin-destination pairs) taken as a subset of a global data set.
The sampling mechanism is based on the market field and not the user location. At Skyscanner we define a market based on the website e.g. Skyscanner.com.sg = SG market.
We don't keep a historical record of the sample sizes. This means that if we re-run a sampled report for our partner(s), the sample size is changed. Even older partners for the older dates will be using the new sample sizes when the report is regenerated.
Why is the data not being delivered to the SFTP Server?
We have found in our experience that failure delivery could be caused by:
- Not allocating permissions to list files in the directory, write and read files for the SFTP Server
- Not whitelisting Skyscanner IP addresses
- Insufficient Disk space in the SFTP Server
If you have made sure that the above three points are not the reason, please get in touch with us using this form.