Skyscanner has recently improved the Self-Debug Tool to better support our partners with enhanced Downstream Visibility (DV) capabilities. These updates are designed to make it easier for you to investigate and resolve data issues by providing more actionable insights, clearer event tracking, and validation support. With these new features, you’ll have greater transparency and control when reviewing DV events, helping to ensure accurate data transmission and a smoother integration experience with Skyscanner.
Self-Debug Features | Expand Cache Duration
We have a new feature in Self-Debug called Expand Cache Duration, which allows you to extend how long incoming events are stored in the cache.
By default, incoming events are cached for 2 days. However, with this feature, you can choose to cache new events for up to 7 days. After 7 days, the cache duration will automatically revert to the default 2-day window unless it is manually updated again on the Self-Debug page.
To use this feature, navigate to your Self-Debug page, select the desired cache duration, and save the changes.
Please note that this setting only applies to new events after it's enabled. It does not apply retroactively and will not display past events if the setting was not configured in advance.
Self-Debug Features | Search by Redirect ID
Another new feature in the Self-Debug tool is Search by Redirect ID.
This functionality enables partners to investigate potential Downstream Visibility data issues.
By querying the Redirect ID from events stored within the configured cache duration, partners can locate the corresponding Downstream Visibility event and verify that the data it contains accurately reflects both the intended values and the information presented on the partner’s site — for example, to confirm that the correct price is being sent from a landing page, you can perform a sample redirect, retrieve the associated Redirect ID, and search for it in the debug tool to verify the event contains the expected price.
Note that multiple events may appear for a single Redirect ID as events triggered at different stages of the funnel within the same flow share the same Redirect ID. In such cases, use the timestamp to identify the correct event.
If no Downstream Visibility event appears when searching with a Redirect ID, it might be because the event wasn’t triggered — for example, if the user rejected a cookie request. To avoid this, make sure to accept all cookies and test using multiple deeplinks to minimise one-off cases.
This feature gives you more visibility into Downstream Visibility events and helps streamline the debugging process.
Self-Debug Features | Added Sample Value and Format
The last new feature we’ve added is clear and actionable formatting guidance for common errors in the self-debug tool. For example, if there’s an issue like “price is empty”, the tool will now display a helpful message along with a correctly formatted example, such as 1000.00, to guide you in fixing the problem quickly. This update is designed to reduce confusion, speed up debugging, and help ensure that data is submitted in the correct format.