Skip to main content

Business Analytics

Business Analytics is the commercial control room in Connect. Use it for GMV, conversion, and which connections or destinations produce confirmed bookings. It is not the place to debug a single ERR_CODE_* — use API Performance and Log & Audit.

Open: app.bundleport.com/connect/business-analytics (connect.read). Default Connect landing page.

Filters​

  • Date preset: 24 hours, 7 days, 30 days, or custom range
  • Service: all, hotels, flights, or ground
  • Connection
  • Destination text (filters the Top destinations table only — not KPIs, trends, markets, or connections)
  • Booking status: all, confirmed, or cancelled

A check-in-date toggle exists in the UI and is disabled. Do not rely on it.

Scope follows the workspace organization. Seller mode re-scopes when you opt in.

KPIs​

Default status is all. Confirmed view uses the cards below. Cancelled view swaps to cancel-oriented cards and hides conversion / L2B.

Cards you will see when status is all or confirmed:

  • Bookings, Cancellations
  • GMV, Cancelled Value Rate
  • Average booking value, nights, and pax
  • Conversion rate
  • Average margin (when cost data exists)
  • Searches, look-to-book (L2B) ratio

Charts and tables​

  • Booking trends — bookings or revenue, by day / week / month. CSV export on the chart.
  • Top markets and top destinations (hotel / city / country). CSV export.
  • Top connections — GMV, bookings, conversion, Cancel % (count: cancels / successful bookings), L2B, average value, nights, pax, margin. Click a row to open API Performance for that connection. CSV export. Cancelled Value Rate is the page KPI (value), not a connection-table column.

How to use it​

  1. Confirm GMV and conversion for the period, not just booking count.
  2. Sort connections by conversion and Cancel % (count). Use Cancelled Value Rate on the KPI row for value leaked to cancels.
  3. Export CSV from a table when you need a snapshot for finance. Rows match what the table shows.

Forward availability searchId as criteria.search_id on quote, then search_id / quote_id on book, so L2B is not inferred. These are analytics IDs, not booking tokens. See Observability.