Same Time Last Year (STLY) compares Demand360 metrics against the same calendar period in the previous year.
In Demand360 inside Insights, STLY gives you a year-over-year view across all available metrics for your subscriber property and comp set, including the full range of KPI indexes and rate data that is not accessible for forward-looking stay dates.
What STLY covers
Because STLY compares historical stay dates, the complete set of Demand360 metrics is available — including ADR, RevPAR, and KPI indexes for both subscriber and comp set.
This is a meaningful distinction from the forward-looking view in Demand360. For future stay dates, comp set rate and index data is not available in Demand360 due to industry anti-competitive rules — ADR Index, RevPAR Index, and comp set ADR and RevPAR cannot be shown for dates that have not yet passed. STLY removes that constraint entirely, because the stay dates being compared have already occurred.
Available in STLY:
Subscriber Occupancy
Comp Set Occupancy
Occupancy Index
Subscriber ADR
Comp Set ADR
ADR Index
Subscriber RevPAR
Comp Set RevPAR
RevPAR Index
STLY comparisons are available at subscriber and comp set level.
How STLY data is sourced
Demand360 is a snapshot-based dataset, with snapshots available approximately twice per week. Each snapshot represents the state of on-the-books demand as of the snapshot date. STLY is built around this structure, using the nearest available historical snapshot as the comparison point for each period.
For example: if today is 12 May 2026 and you are analysing stay dates in June 2026, the STLY column shows the data for those same June dates in 2025 as it appeared in the snapshot from around 12 May 2025.
Because snapshots are available approximately twice per week rather than daily, a precise day-for-day match is not always available. When there is no exact match, the nearest available snapshot from that period is used — typically within one to three days of the equivalent date.
What snapshot timing means for your data
This is how Demand360 data is structured, and it is worth keeping in mind when interpreting STLY figures.
What it does not affect:
Seasonal patterns and how performance compares year-over-year
Subscriber occupancy index position vs. the comp set
The overall trajectory of bookings at this point in the booking window compared to 12 months ago
ADR and RevPAR trends
For this kind of analysis, the directional signal is robust. A snapshot that is one or two days off from the exact equivalent date does not meaningfully change what the data tells you about year-over-year positioning or pacing.
Where to apply more caution:
Comparing the exact OTB room count for a specific stay date on a specific day, where a precise day-for-day match matters
Short-horizon stay dates (within the next week or two), where even a small difference in snapshot timing can affect the apparent pickup rate
FAQs
How far back does STLY data go?
Coverage reflects the historical data available in Demand360 for your property — in most cases this covers the past year. The exact starting point depends on when your Demand360 connection was activated and the historical data collected since then.
Why does STLY show slightly different figures than what I see in the Demand360 product directly?
Demand360 is a snapshot-based dataset, with snapshots available approximately twice per week. What you see in Insights reflects the most recent available snapshot rather than a live feed, so a short lag is expected. Small differences are normal and are not a data error.
I can see STLY for some periods but not others — why?
Coverage reflects the historical data available in Demand360 for your property. If earlier periods are not appearing, data may not have been collected for that time. Coverage cannot be extended beyond what is available in the historical feed.
Why is STLY fixed to last year? Can I compare to last week or last month instead?
Demand360 historical data is structured around annual files, which makes year-over-year the natural and reliable comparison window. Shorter windows like same time last week or same time last month would require a level of snapshot precision that a snapshot cadence of approximately twice per week cannot consistently support. A difference of one to three days in snapshot timing is negligible over a year-over-year comparison, but would materially distort a week-over-week or month-over-month one.
See also: Benchmarking (Demand360) Topic