Insights shows distribution activity and booking outcome amounts for your organization. Review gross merchandise value (GMV), confirmed bookings, request processing, and Adrasis AI Operator usage alongside the selected outcome agreement. Read your platform subscription separately when checking the complete service price.
Selecting one payable outcome does not turn off the other measurement. Insights keeps both comparisons available while including only the selected result in outcome totals. Selected booking usage consumes the annual USD balance. Explicitly purchased capacity and Token Packs are separate charges; usage totals are not payment receipts.
What Insights answers
| Question | Where to look |
|---|---|
| Which outcome basis applies to this organization? | Commercial model tile |
| How much service usage was recorded in the latest closed period? | Latest closed usage period |
| How much credit remains and what payment is still due? | Annual usage balance |
| What would the same activity produce under the other outcome basis? | GMV comparison and Per-booking comparison |
| How much GMV and how many bookings were confirmed? | GMV tile and comparison cards |
| How much distribution traffic reached the availability pipeline? | L2B and Compute tiles, trends, channel matrix |
| How much included AI Operator usage remains today and this month? | AI Operator usage tile |
| Which channels and properties are driving traffic or errors? | Channel matrix, Top consumers, Gate rejections |
| Who visits your web shop, from where, and how many book? | Shop tab |
Commercial model and comparisons
Standard provides an annual usage budget of USD 6,000 at a 2% booking service rate. Pro provides USD 12,000 at 1%. The budget is funded upfront; monthly booking service fees consume that balance. There is no monthly minimum deduction. See Platform subscriptions for the full offer.
Enterprise uses an accepted quote. Only Enterprise can select the per-booking fee: USD 1 for each confirmed booking, or USD 2 for a package that holds accommodation and at least one other product, such as a transfer or a tour. Nights, rooms and guests are not counted. Both booking-value and per-booking comparisons remain visible. Only the selected basis consumes credit; a comparison never creates another charge.
For example, Standard usage on USD 10,000 of eligible booking value is USD 200. If that value came from 3 bookings, one of them a package, the per-booking comparison is USD 4. Standard deducts USD 200 from its funded balance at monthly close.
The booking's accepted agreement freezes the rate. A package change does not reprice earlier activity. Activity without an agreement remains analytical; a later agreement does not retroactively create a charge. A cancelled booking returns its per-booking fee; a no-show keeps it.
Reading the headline strip
- COMMERCIAL MODEL: the current effective outcome agreement and either its explicit basis-point rate or the per-booking fee of USD 1.00, USD 2.00 for a package.
- L2B RATIO: the current card compares requests classified as processing work with all distribution requests in the selected range. Despite its label, this is not searches divided by confirmed bookings. It does not determine a contractual search allowance or an excess-usage fee.
- COMPUTE METER: measured distribution compute in the selected range. It remains analytics-only and is not a payable line item.
- DATA TRAFFIC: the size of the search requests received in the selected range and of the answers sent to them, shown as in and out.
- AI OPERATOR USAGE: used, reserved, remaining, and total usage units in the current UTC-day and UTC-month pools included with the organization's subscription.
- CONFIRMED: booking confirmations in the selected range.
- GMV: net GMV movements, kept as a separate line for each currency.
- LATEST CLOSED USAGE PERIOD: recorded service usage from the latest closed period. Booking usage settles in USD and consumes prepaid credit; this is not the amount still due.
Raw booking values and comparisons remain separated by currency. Closed booking usage is shown in USD using its frozen conversion. Separate service charges retain their recorded currency and must not be nominally added across currencies.
AI Operator usage
AI Operator usage is included in the organization's existing subscription at no additional charge. Each organization receives 2,000,000 usage units per UTC day and 60,000,000 usage units per UTC month, and Adrasis can raise these allowances for your organization. Usage units follow real consumption, so the same work on a lower-cost model uses fewer units. The active configuration also defines the maximum context and completion limits and the available model set. Effective context and output limits use the lower of the configured limit and the selected model's capability.
Reserved and completed usage remains part of both applicable allowances when a screen is refreshed or a request is retried. When an allowance is exhausted, the AI Operator continues with your organization's token packs for the month. Without one, requests wait for the applicable UTC reset or a quota reset by Adrasis. There is no automatic overage charge: extra usage comes only from token packs an administrator buys and confirms. The AI tile shows the effective limits and the remaining token pack units.
Annual usage balance
The balance panel shows the annual commitment, confirmed funding, closed usage, available credit, amount due and expired credit in USD. Creating a term does not mean payment was received. Amount due covers unpaid commitment or usage above confirmed funding; closed usage is not collected a second time.
Monthly close deducts the selected usage. Open-month activity has not yet reduced the displayed balance. Additional funding keeps the same annual expiry. Unused credit expires at term end, with no rollover or automatic refund. Renewal creates a new term. A shortfall does not change or block bookings.
Closed usage statements are not invoices
The latest closed usage period shows the immutable usage statement. Booking usage settles in USD and consumes prepaid credit. It is neither a second cash demand for the same usage nor proof of payment. Confirmed payments appear in the balance panel. Token Packs and explicitly purchased additional services remain separate.
The original booking value retains its currency. At the first monthly close, the service fee is converted into USD using a recorded rate. Corrections use the original conversion and original annual term, including after expiry. They do not restore spendable credit in an expired term.
Commercial movements determine amounts. Analytical refresh delays do not create or change charges. A statement is not a statutory invoice.
Operational panels
The trend cards show L2B, compute volume, and p95 distribution latency. The channel matrix breaks down requests, measured gate reach, cache share, latency, errors, confirmed bookings, L2B, and net GMV by channel. Top consumers ranks properties by measured processing work. A search can contribute to several returned-property rows. These rows are not a count of billable external searches and do not describe properties that returned no offer.
Gate rejections and the hourly waveform are operator diagnostics over the last 24 hours. A spike at one gate often indicates malformed partner traffic or an out-of-date property configuration. Cache-served requests and early gate rejections remain useful operational signals. The operational counters do not create a charge. If your agreement includes search capacity, use its explicit unit and allowance; a valid cached response can count as a delivered search, while rejected requests and platform failures do not.
Review traffic as you add API partners
Review observed requests and errors in the channel matrix for the selected period. Use the trend cards and the last 24 hours of hourly traffic to assess changes. For example, a Bodrum tour operator adding a new API partner can share current channel traffic and expected demand with its Adrasis contact.
Check the covered operations, account scope, and time window in your connection terms when discussing request limits. Your Adrasis contact can review the requested capacity change using those terms and the observed traffic.
Use the API figures to understand traffic. They do not show a remaining contractual API allowance. Reviewing Insights does not change request limits or create an additional charge; agree capacity and price changes with Adrasis.
Shop visitors
The Shop tab shows who visited your web shop, where they came from, what they looked at, how many reached a booking and where the others stopped, and keeps the bots apart from your visitors. For example, Blue Coast Tours can see that most of last week's visitors came from Germany on a phone, that 6 of them started the checkout and that 4 of those left before entering the guest details.
| Card | What it shows |
|---|---|
| From visit to booking | Visits, search result views, hotel page views, checkout starts and bookings in the selected range, each as a share of visits. |
| Checkouts that did not book | Where the guests who started the checkout and did not book stopped: before the guest details, after the details without paying, at the payment step, a payment or booking that did not go through, or still in progress; and the hotels left most often. Shown while there is one. |
| Hotel pages | How many hotel pages were opened, the hotels opened most, and how many guests started the checkout and booked at each. |
| Where visitors come from, Countries | Visits by country on a world map and as a ranked list. |
| Daily visits | Visits and page views for each day. |
| Devices | The share of desktop, phone and tablet visits, the operating systems, and how many requests your web shop, your iOS app and your Android app sent. |
| Most viewed pages | Page views and entries for each kind of page, such as the home page, search results and hotel pages. |
| Bots | Page requests from bots, which are not counted as visits: search engines and SEO tools, AI bots, link previews and other known bots, each with the bots that asked most and how many were stopped, and other automated traffic that was blocked or asked to prove it is human. |
If you run more than one web shop, choose the shop in the first card.
Visits and page views are estimates counted from the pages your web shop served, with known bots removed; bot requests are estimates too. They are refreshed every minute, so today's visits show up within a few minutes, and 24h shows yesterday and today so far (days are counted in UTC). Checkout starts and bookings are exact: a booking is a checkout that ended in a booking, so a checkout whose payment failed counts where it stopped. Your mobile apps are counted in requests, not visits: one screen makes several.
Refresh, ranges, and corrections
The range selector controls operational analytics and comparison activity. The current agreement and latest closed usage period are independent of the selected range. Recent analytical results may take a short time to appear.
Cancellations and corrections reverse the original movement and its frozen agreement terms. They do not use today's agreement. A late correction is recorded in the next open accrual period with lineage to the original period; a closed period itself remains immutable.
Permission requirements
The insights:read permission grants access to an organization's Insights data.
Organization isolation still applies to every query. Platform administrators must
switch to an authorized organization context before reading another organization's view.
Trace service usage to its movements
-
Open Month reconciliation
In Latest closed usage period, select See the facts behind this figure. The Month reconciliation card opens for that month. Choose another Month to look at it.
-
Read the month's total
While a month is open, So far shows the fees recorded until now; they can change until the month closes. A closed month shows Month closed, total. When Usage Credits paid part of it, a line shows the charges and the part paid by Usage Credits. Charged for lists what the month charges, such as booking fees and AI Operator usage.
-
Find the records behind it
Each record shows Date, What happened (for example Booking confirmed, Stay completed, Booking cancelled or Correction), Booking, Sale amount and Fee. Under Records, choose Cancellations or From an earlier month to explain a difference, or use Search booking number. With a filter on, the total reads Fee of these records.
-
Export the records
Choose Export, then CSV file or Excel file, to download every matching record, including those beyond the visible page. The export uses the current filter. A result above 50,000 rows is refused; narrow the filter before exporting again.
For example, to explain why Bodrum Travel's July fees fell, open July and choose Cancellations under Records to see the cancelled bookings that lowered the total. Return to All records before exporting the complete month.
Refreshing the view does not close an open month or change a closed total. If the page says that the month's closed total does not match its records, tell our support team. An empty result means no matching records; it does not by itself mean the organization owes nothing.
Where to next
- Review platform prices and annual payment → Platform subscriptions
- Use the included AI Operator allowance → AI Operator overview
- Review inventory and availability controls → Pricing & Availability
- Check commercial and operational terms → Glossary