Calendar Events allow you to analyse and compare specific periods such as holidays, festivals, or special trading windows directly within Insights. To ensure comparisons behave as expected, there are a few important considerations when creating events in FLYR Hospitality.
This article explains what to pay attention to when configuring events so they can be compared accurately in Insights.
Why Event Configuration Matters
When you compare events in Insights (for example, Ramadan this year versus last year), the system does not align dates by calendar day. Instead, it compares events using a day-number approach:
Day 1 vs Day 1
Day 2 vs Day 2
And so on
This approach allows events that occur on completely different stay dates to be analysed side by side in a consistent way.
Because of this, how your events are configured in the calendar directly affects the validity of the comparison.
Required Setup for Accurate Event Comparisons
Use the Same Number of Dates for Comparable Events
When creating or editing an event in Calendar Settings (either as an Event Price Setting or a Note):
Ensure that each event you plan to compare contains the same number of dates
This applies even if the actual stay dates differ year over year
Example
If you want to compare:
Ramadan 2024
Ramadan 2025
Both events must cover the same number of days (for example, 30 days each). If one event spans 29 days and the other spans 30 days, the day-by-day comparison in Insights will not align correctly.
This is the single most important requirement for event-based comparison.
Naming Conventions: Flexible by Design
There is no required naming convention for events. You can choose whatever naming approach works best for your team.
How event names appear in Insights
Within Insights, events can be analysed using:
Event Name
Event Name + Start Date - End Date
The start and end dates are automatically pulled from the event’s date selector.
Practical naming options
You may choose to:
Use the same event name every year (for example, Ramadan)
Or include the year in the name if you prefer (for example, Ramadan 2025)
If you use the same name each year, you can simply rely on the Event Name + Dates field in Insights to clearly distinguish between periods without needing to rename events annually.
Summary of Best Practices
When creating events intended for analysis in Insights:
Always use the same number of dates for events you want to compare
Remember that Insights compares events using day number, not calendar date
Choose any naming convention that suits your workflow
Use Event Name + Dates in Insights if you want clarity without maintaining year-specific names
Once these conditions are met, event-based comparisons in Insights will behave consistently and predictably.