What data do we receive from Amadeus?
FLYR Hospitality receives two types of files from Amadeus Demand360:
A historical file delivered when your integration is first set up, covering up to 15 months of past stay dates. This gives you a meaningful baseline from day one.
Rolling updates delivered roughly twice per week, each covering a rolling 12-month forward window. These keep your forward-looking view current as market conditions evolve.
Each file includes on-the-books room nights for your property (subscriber) and your primary competitive set, along with revenue metrics for historical dates, and segment and channel breakdowns. Comp set revenue data for future stay dates is not included — this is an industry-wide restriction that applies across all Amadeus products.
Do I need an Amadeus Demand360 agreement to use this topic?
Yes. The Benchmarking (Demand360) topic is visible to all Insights customers, but data will only appear for properties with an active Amadeus Demand360 agreement.
If you have a D360 agreement but no data is appearing, your property may not yet be onboarded to the integration. Reach out to us via the chat to learn more.
How often does the data update?
Approximately twice per week. The exact days vary — delivery is not on a fixed schedule. The Latest Reported Date shown on the Demand360 dashboard tells you the date the data is current as of.
If you open the topic on consecutive days without a new file arriving in between, the data will be identical. This is expected.
Why might my data not match what I see in Amadeus?
A few reasons:
Delivery timing. The file Insights received may be a day or two behind the current state in Amadeus.
Snapshot differences. Amadeus lets you select a specific historical date to view how the picture looked at that point in time. Insights always shows the latest snapshot — so if you are comparing to a specific point in time in Amadeus, you are looking at different underlying data.
Minor calculation differences. Some metrics are calculated by FLYR from raw fields in the data file. Small differences from Amadeus's own displayed figures are possible.
If you notice a significant or persistent discrepancy, reach out via the chat — it may indicate a data delivery issue worth investigating.
For a full explanation of how data delivery works, see How Demand360 Data Works in Insights.
What limitations exist on the Demand360 data FLYR receives?
Forward window: Rolling 12 months ahead from the date of the latest file.
Historical depth: Up to 15 months, delivered as a one-time file when your integration is set up.
No daily updates: Data refreshes roughly twice per week, not daily.
Subscriber ADR and RevPAR are available for both historical and future stay dates. What is not available for future dates is comp set ADR and RevPAR — Amadeus does not share competitor revenue data forward-looking due to industry rules. Because the index calculations require a comp set denominator, ADR Index and RevPAR Index are also unavailable for future stay dates. Occupancy and Occupancy Index are available for future dates.
No individual competitor breakdowns: Comp set data is aggregated across your primary competitive set. You cannot see individual property-level data for competitors.
No ADR or RevPAR rank: These fields are not included in the data Amadeus shares with FLYR.
No as-of-date selection: Insights always shows the most recent snapshot received. You cannot view how the picture looked on a specific historical date as you can in the native Amadeus product.
Can I change my competitive set from within Insights?
No. Your comp set is determined by your Amadeus Demand360 account configuration, not within Insights. Changes need to be made in your Amadeus account directly.
If you change your comp set in Amadeus, rolling updates going forward will reflect the new comp set. Your historical data will continue to reflect the previous comp set unless a new historical file is requested — we can request one on your behalf once per year. Reach out via the chat if you make a comp set change and want the historical data updated to match.
How is occupancy defined in the Demand360 topic?
Occupancy = Room Nights ÷ Capacity, where Room Nights include all room nights deducting from available capacity — including Unsold Block. This is consistent with how occupancy works across all other Insights topics. If you want to see picked up reservations only, use the Segment filter to exclude Unsold Block.
For full detail on the occupancy definition and how it relates to what you see in Amadeus, see How Demand360 Data Works in Insights.
What is Unsold Block?
Unsold Block represents room nights that are committed but not yet picked up — blocked or allotted without a confirmed reservation against them. Depending on how your property reports this data in Amadeus, Unsold Block room nights can fall under Transient, Group, or Other. It is not exclusively group blocks — it can represent any category of uncommitted room nights that are deducting from available capacity.
Unsold Block is its own Segment value in the Demand360 topic. You can filter to it, exclude it, or explore it independently depending on what you are trying to understand.
What is the Risk Signal on the Demand360 dashboard?
The Risk Signal classifies each stay period into one of three tiers — Low, Moderate, or High — based on two factors: your unsold block share (unsold block room nights as a share of total room nights) and your Occupancy Index relative to the comp set.
The logic reflects compounding risk: a large block exposure carries more weight when you are already under-indexing against the market. The Risk Signal is a field built into the pre-built dashboard template — it does not appear in the topic if you build your own workbook from scratch.
For the full tier criteria and guidance on adjusting the thresholds, see How Demand360 Data Works in Insights.
Why is my Occupancy Index blank for some dates?
The Occupancy Index is suppressed and shown as — when comp set room nights for a given period fall below 50. This threshold exists to avoid presenting a misleading signal based on too thin a sample.
How does Demand360 segment naming compare to other Insights topics?
Demand360 uses Amadeus's own segment naming conventions, which differ from the segment names used in other Insights topics:
Segment (top level): Transient, Group, Other, Unsold Block
Sub-Segment: e.g. Discount, Retail, Negotiated, Qualified, Wholesale
Segment Detail: e.g. Corporate, Consortia/TMC, Crew/Contract
Channel naming also aligns with Amadeus: Direct, Brand.com, GDS, OTA, Other — with sub-channels at the next level (Property Direct, Expedia, Booking.com, Sabre, Amadeus).
Where can I find Demand360 data in Insights?
Dashboard Templates: A pre-built Benchmarking (Demand360) dashboard is available in the Dashboard Templates folder under FLYR Templates.
Topics: Demand360 data is available in the Benchmarking (Demand360) topic.
For more guidance, see How Demand360 Data Works in Insights or reach out to us via the chat.