Weekly SiteMinder channel performance and pace report

1. Go to Insights > Booking performance. The report opens on last month to date, so set the dates to last Monday to Sunday.
2. Choose View performance by > Channel mix and note room revenue, room nights and reservations for each channel.
3. Change the dates to the week before and write the same numbers down again to compare the two weeks channel by channel.
4. Open Insights > Pace: it defaults to the next 30 days and compares room revenue and ADR with the same period last year.
5. Copy everything into a sheet or the team chat. The SiteMinder help pages for Booking performance and Pace mention no scheduled email or export, so the review happens only when someone sits down to do it.

Every Monday, compare last week's bookings by channel with the week before, and tell me how the next 30 days pace against last year.

1. 01

   Use booked-on dates for the week

   The agent calls get_booking_performance for last Monday to Sunday and for the week before, by booking date with a channel_mix breakdown. Booked-on dates show what each channel sold that week; stay dates would mix in bookings made months ago.

2. 02

   Compare like with like

   For each channel it computes the change in reservations, room nights and room revenue. ADR is compared only where revenue was recorded, because some channels send bookings without revenue and SiteMinder leaves those out of ADR.

3. 03

   Add the pace view

   get_pace_report for the next 30 days gives this year against last year. The agent flags a fall in room nights even when revenue is up, since a higher ADR can hide fewer bookings.

4. 04

   Explain big moves before sending

   When one channel moves by more than your threshold, the agent says so in one line and names the likely cause it can see, such as a jump in cancellations, rather than guessing at OTA rankings.

5. 05

   Add parity only when you ask

   If you want parity in the report, get_rate_parity covers the next 30 days and adds the dates where an OTA sits below your direct rate. Without SiteMinder Plus that part is skipped with a note.

Week 5 to 11 Oct vs 28 Sep to 4 Oct (booked on)
Booking.com: 24 reservations (+5), 58 room nights, EUR 5,120 room revenue (+18%)
Expedia: 11 (-4), 26 room nights, EUR 2,310 (-22%)
Direct Booking: 9 (+2), 21 room nights, EUR 1,890 (+14%)
Cancelled: 6, of which 4 Expedia
Pace, next 30 days vs last year: room nights 341 vs 302 (+13%), ADR EUR 83.28 vs 83.11

• SiteMinder Booking performance never counts cancelled bookings in Reservations (after cancellations); cancellations appear as their own count.
• With Booking performance set to stay date, SiteMinder hides total revenue and counts only the room nights inside the chosen period.
• SiteMinder converts reservations in other currencies to your default currency at xe.com rates, so a week's total can move with the exchange rate.
• SiteMinder Pace shows reservation revenue as nightly room rates only, without extras and card surcharges, and looks up to one year ahead.
• The SiteMinder Rate parity report needs SiteMinder Plus and covers Agoda, Booking.com, Expedia, HRS and Direct Booking 30 days ahead, or 90 with Dynamic Revenue Plus.

Every tool here only reads, so it can run weekly from n8n, Make, Zapier or cron without waiting for your OK.

Sources: SiteMinder Help: Booking performance report · SiteMinder Help: Pace report · SiteMinder Help: build custom booking performance charts · SiteMinder Help: Rate parity report

curl https://cotlet.dev/api/v1/siteminder/get_booking_performance \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"from":"2026-10-05","to":"2026-10-11","date_basis":"booked_on","breakdown":"channel_mix"}'

{
  "from": "2026-09-01",
  "to": "2026-09-30",
  "date_basis": "booked_on",
  "currency": "EUR",
  "room_revenue": "42500.00",
  "total_revenue": "45000.00",
  "reservations": 212,
  "cancelled_reservations": 18,
  "room_nights": 500,
  "avg_lead_time_days": 21.4,
  "adr": "90.00",
  "alos": 2.36,
  "channel_mix": [
    {
      "channel": "Booking.com",
      "reservations": 95,
      "room_nights": 225,
      "room_revenue": "19500.00"
    },
    {
      "channel": "Expedia",
      "reservations": 55,
      "room_nights": 135,
      "room_revenue": "11500.00"
    },
    {
      "channel": "Direct Booking",
      "reservations": 45,
      "room_nights": 105,
      "room_revenue": "9000.00"
    },
    {
      "channel": "Agoda",
      "reservations": 17,
      "room_nights": 35,
      "room_revenue": "2500.00"
    }
  ]
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is siteminder_get_booking_performance. Example data.

• Update SiteMinder rates for busy dates and events
• Set SiteMinder minimum stay and closed to arrival for peak dates
• Fill SiteMinder gap nights by lowering minimum stay
• SiteMinder API and MCP server: every tool
• All use cases