Hotel website conversion: measuring confirmed bookings

More website enquiries do not establish that more guests completed a booking. A contact button, a submitted request and a confirmed reservation describe different outcomes. Give each its own name and counting rule.

The direct booking strategy guide covers the wider sales process. Here we define the conversion percentage and check its supporting evidence.

Agree what a successful session means

SiteMinder describes hotel conversion as turning interest into confirmed reservations. For this worksheet, success requires evidence of a completed online booking, with a valid reservation reference and the hotel’s confirmation conditions met.

Use booking session conversion = sessions with a confirmed online booking ÷ eligible measured sessions × 100. A session is a visit as defined by the analytics system; one person can have several visits. Keep the same measurement scope and exclusions in both parts of the calculation.

Google’s metric reference defines sessionKeyEventRate for any key event and sessionKeyEventRate:event_name for one specified event. Combining enquiry and booking events cannot answer the booking-only question.

Count a successful session once even if its confirmation event appears twice. Reservation volume belongs in another column: two genuine bookings in one session still contribute one successful session. If tracking cannot establish completed bookings reliably, label the result unavailable rather than replacing it with button clicks.

Keep enquiry stages separate

Recorded outcome	Interpretation
Telephone or WhatsApp button click	Contact intent; a conversation may never happen
Accepted enquiry form submission	A request received, awaiting the hotel’s response
Confirmed online booking	A completed website transaction meeting the agreed conditions
Later telephone confirmation	An offline outcome requiring separate evidence of origin

A site that only collects enquiries can report enquiry submission conversion. It should not call that percentage completed booking conversion. The reservation workflow guide helps staff define where a request becomes a confirmed internal record.

Work through an original example

Imagine a fictional hotel recording 2,400 eligible sessions from 1–7 September. Tests and identified internal visits have been excluded consistently. Of these sessions, 120 include a contact-button click, 72 include an accepted enquiry submission, and 36 include a confirmed online booking. These groups may overlap; do not add them together.

The booking session rate is 36 ÷ 2,400 × 100 = 1.5%. Enquiry submission conversion is 72 ÷ 2,400 × 100 = 3%. Neither figure is a benchmark or a promised result.

Suppose the log contains 41 confirmation events, including repeated signals. Dividing 41 by 2,400 answers the wrong question. Reconcile reservation references and sessions to establish 36 successful sessions and investigate repetition. Do not delete genuine reservations to match totals.

Freeze the cohort and allow for delay

Record the observation dates, time zone, included website domains and data extraction date. Recheck the same session cohort after the agreed reporting delay; mark the first reading provisional. A completed booking in a new visit the following week belongs to that later session, even if the guest first discovered the hotel earlier.

For offline follow-up, keep a separate enquiry cohort. Suppose 50 distinct requests received during 1–7 September produce 15 confirmed telephone bookings by 14 September. That cohort’s confirmation rate is 30%. Do not add the 15 to the website numerator: the request list, follow-up window and outcome are different.

Document source evidence, such as an enquiry reference. “I found you online” does not identify a session. Leave uncertain attribution unknown; staff assumptions can exaggerate campaign performance.

Check the journey before judging performance

Ask the website or analytics owner to verify these cases and keep the results with the worksheet:

• A successful booking has a matching confirmed reservation.
• A rejected or abandoned request never appears as a completion.
• Reloading the confirmation page does not inflate the successful-session count.
• Moving to an external booking domain does not split one journey into misleading duplicate visits.
• Mobile and desktop journeys use the same success definition.
• Consent gaps, tracking outages and test exclusions are documented.

This is a measurement review, not a tracking installation guide. Investigate missing or duplicated records before claiming improvement. Compare similar traffic groups and show counts beside rates; one extra booking can move a small sample sharply.

Frequently asked questions

Should cancellations reduce the original conversion rate? Keep the original completion measure stable. Review subsequent cancellations separately using a defined cohort and cutoff, as in the booking cancellation rate guide.

Is a return visit another session? It may be, according to the analytics definition. Session conversion is not the percentage of individual people who eventually book.

Does BirOtel automatically measure website conversion? A native booking engine, GA4 integration and automatic website attribution are not confirmed. Website measurement needs separately verified analytics.

BirOtel supports internal reservation and source records, income, occupancy and ADR reports, and Excel exports. Its PMS interface is available in Azerbaijani and English. Bring a sample reconciliation worksheet to a reservation software demonstration to check how staff can maintain the internal records used in your review.