Introduction
In the Bookings topic, there are two sets of Lead Time fields: one based on the stay date and the other based on the arrival date. Each set serves a different purpose, and it's important to understand when to use each one to ensure that your analysis is accurate.
Why Are There Two Sets of Lead Time Fields?
We provide two sets of Lead Time fields because they are designed to support different use cases:
Stay Date-based Lead Time: This set of fields calculates lead time based on the dates that guests stay. This is useful when you are analyzing bookings grouped by stay date (e.g., stay day, stay week, or stay month). Using these fields allows you to see how lead time behaves across your booking calendar.
Arrival Date-based Lead Time: This set of fields calculates lead time based on the date a booking was made (i.e., the arrival date). This version is useful when you are grouping by non-date dimensions, such as company, inventory, or channel. It ensures that the data is normalized and not skewed by bookings with longer stays.
When to Use Each Set of Lead Time Fields
1. Use Stay Date-based Lead Time When:
Grouping by date dimensions (such as stay day, stay week, or stay month).
Analyzing how lead time varies across different time periods for specific stay dates.
You want each night of a booking to be counted only once within the time period, ensuring no over-representation of long stays.
Example: If you're analyzing how lead time changes by stay week, the stay date-based lead time will give you the right view since it counts bookings according to their stay dates and shows trends over time.
2. Use Arrival Date-based Lead Time When:
Grouping by non-date dimensions, such as company, inventory, or channel
You need to understand booking behavior while normalizing the impact of longer stays. This ensures that long stays do not disproportionately affect your analysis.
You’re focusing on how far in advance guests are booking, regardless of the length of their stay.
Example: If you're analyzing bookings by company or inventory, the arrival date-based lead time will ensure that all bookings are treated equally, and you won’t see your average lead time artificially inflated by longer stays.
Key Differences at a Glance:
Field Type | When to Use | Best For |
Stay Date-based Lead Time | Grouping by date dimensions (stay date, stay week, stay month) | Understanding booking patterns over time |
Arrival Date-based Lead Time | Grouping by other dimensions (company, inventory, or channel) | Normalizing lead time across different booking types |
Conclusion
To summarize, use the stay date-based fields when grouping by time periods like stay dates or weeks. Use the arrival date-based fields when grouping by dimensions such as company, inventory, or channel, and when you want to control for the effect of long stays on average lead time.
By using the appropriate Lead Time field based on your analysis needs, you’ll ensure that the insights you get are relevant and actionable.
If you have any questions or need further assistance, please feel free to reach out to us via the chat!