Demand360 data in Insights is sourced from Amadeus and brings forward-looking market benchmarking into the same product as your bookings, pickup, forecast, and rate shopping data. Understanding how the data is structured and delivered will help you get the most out of it — and know exactly when to reach for the native Demand360 product instead.

When building Demand360 into Insights, we made a deliberate choice: always show the most recent data available.

Our research with revenue managers consistently showed that when evaluating forward-looking market performance, the latest snapshot is what matters most. Where are you positioned right now, relative to your comp set? That is the question driving daily decisions — and it is the question the latest data answers most directly.

This also reflects how Insights is designed more broadly. Our goal is not to replicate every capability of the native Demand360 product, but to bring the most decision-relevant benchmarking data into the same environment as your own performance data, so you can evaluate your forward position in context rather than in isolation. Demand360 in Amadeus remains the right tool for deep historical snapshot comparisons and exploring how your comp set picture has evolved at specific points in time. We are designed to complement that, not replace it.

Future phases of this integration will bring in pickup and same time last year benchmark comparisons, so you can track how your market position is trending over time — alongside the contextual richness you already have in Insights.

Amadeus sends Demand360 data to FLYR in two ways:

The days of delivery are not fixed — they vary week to week.

The Latest Reported Date shown in the Demand360 dashboard tells you the date the data is current as of. It is informational — not a filter. You are always viewing the most recent snapshot we have received from Amadeus, and earlier snapshots are not accessible within Insights.

Latest Reported Date is also available as a field in the Demand360 topic. You can add it to your own dashboard templates or include it in ad hoc queries to make data currency visible wherever you are working.

If you also have access to the native Demand360 product, you may notice that numbers don't always align exactly. This is expected. For the full breakdown of reasons, see FAQ: Demand360 Data in Insights.

The most nuanced factor to understand is snapshot timing. The native Demand360 product lets you select a specific historical date to view how the picture looked at that point in time. Insights always shows the latest snapshot — earlier snapshots are not accessible. If you are comparing to a specific as-of date in Amadeus, you are looking at different underlying data. That is not a discrepancy — it is two distinct views of the same market, taken at different points in time.

If you notice a significant or persistent discrepancy that you can't explain by the above, reach out to us via the chat — it may indicate a data delivery issue worth investigating.

Room nights and occupancy in the Demand360 topic are consistent with how those metrics work across all other Insights topics. They represent all room nights that are deducting from available capacity — including Unsold Block room nights — because these are committed room nights that reduce what is available to sell, regardless of whether a confirmed reservation exists against them.

This makes it straightforward to compare and layer Demand360 figures with room nights and units in your bookings and pickup topics, because they are built on the same principle.

A note on the Amadeus platform: Amadeus represents occupancy differently in different parts of their product — some views include Unsold Block, others do not. In Insights, the default always includes all room nights that are deducting from capacity, giving you a complete and consistent picture.

If you want to focus only on room nights with confirmed reservations — picked-up demand only, excluding Unsold Block — use the Segment fields as filters. You can do this using the Segment filter control on the pre-built dashboard, or in any workbook or ad hoc query by filtering the Segment field to exclude 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 or allotments — it can represent any category of uncommitted room nights that are deducting from available capacity.

Because of this, Unsold Block is its own Segment value in the Demand360 topic, visible alongside Transient, Group, and Other. You can filter to it, exclude it, or explore it independently depending on what you are trying to understand.

The pre-built Demand360 dashboard includes a Risk Signal for each stay period. This is a field FLYR built into the dashboard template — it does not exist in the underlying Demand360 topic and will not appear if you build a workbook from the topic directly.

The signal classifies each stay period into one of three tiers 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 two compounding risk factors: how much block room nights still need to convert, and whether your overall market position already shows underperformance. A large block exposure is less concerning when you are over-indexing against the market; it carries more weight when you are already under-indexing and relying on those blocks to materialize.

Because this field lives in the dashboard template and not the topic, you can copy the template and adjust the thresholds to reflect your own risk tolerance. If you would like help doing that, reach out to us via the chat.

The Occupancy Index is calculated as:

Subscriber occupancy % ÷ Comp set occupancy % × 100

The index is suppressed and shown as — when comp set room nights for a given period fall below 50, to avoid presenting a misleading signal based on too thin a sample.

At segment level: a high index for a specific segment can reflect concentration rather than genuine outperformance. If your Group segment is heavily committed and the comp set has little Group on the books, the index will be high — but that reflects a mix difference, not necessarily a demand advantage. Use segment-level index as a signal to investigate further, not as a standalone conclusion.

Amadeus does not provide comp set revenue data for future stay dates. This is an industry policy restriction that applies across all Amadeus products.

In practice:

For past stay dates, comp set ADR and RevPAR are available and all three indexes calculate normally.

This is where Demand360 in Insights really shines. Forward-looking benchmarking data is most useful not in isolation, but in context — and Insights is built to make that combination as frictionless as possible.

The central question Demand360 helps you answer is: are you getting your fair share of demand in the market, for the periods that matter most to your performance goals? Pairing it with your other data is how you move from that question to a decision.

A few things to keep in mind when combining topics:

For details on how your comp set is configured, what to do if you change it, and segment and channel naming conventions, see FAQ: Demand360 Data in Insights.

Questions about your Demand360 data or how to get the most from it? Ask in the chat — always happy to help.