Connecting PMS and OTA Data to Looker Studio: Seeing Hotel Sales with Data

GA4 and Ads data show the “demand and digital behavior” side; but in hotel sales the essence of the decision is the reality of PMS/OTA revenue. Because “clicks and conversions” may not always mean “check-in and net income”. Revenue signals such as cancellation/no-show, commission, room type distribution and country breakdown often live in PMS/OTA.

Mini example (Antalya/Bodrum context): While web booking seems to be increasing during peak season, if no-shows are on the rise in PMS; On the revenue side, the strategy should turn to "quality" rather than "volume". Seeing this distinction in a single panel prevents incorrect optimization.

☑ Mini Check: • Do you consider channel-based revenue as “realized revenue”? • Do you monitor cancellation/no-show rates in the channel breakdown? • Do you take the commission effect into account in the net income calculation?

Short answer: First, prepare critical fields (date, room type, channel, country, revenue, cancellation/no-show) from PMS and OTA in a standard export format. Then move it to Looker Studio via the appropriate connector/middleware (Sheets/CSV, data warehouse or integration). Finally, match GA4 and Ads data in the same date/channel dictionary and set up the channel-based occupancy-revenue panel.

Step-by-step integration plan (data preparation + connector + security)

• •Create data dictionary: Channel names, room type, country code, currency
• •Set export standard: daily/weekly, same columns fixed
• •Choose middleware: MVP or more enterprise structure with Google Sheets/CSV
• •Looker Studio data source setup: date, channel, country, room type dimensions
• •Security note: access rights, masking (if necessary), sharing rules
• •Matching: GA4 campaign/UTM → link with channel dictionary
• •Dashboard: Channel mix + revenue KPI + cancel/no-show + RevPAR

☑ Mini Check: • Is the date format unique? (like YYYY-MM-DD) • Is it net including/excluding currency and VAT/commission? • Are the channel names consistent, such as “OTA / Web / Call Center”?

This section clarifies the areas that strengthen the revenue decision while keeping the technical part simple. The goal: not to “take every field” but to have the panel answer decision questions.

Critical data fields that can be pulled from PMS

• •Date: reservation date / accommodation date distinction (definition fixed)
• •Room type / segment: room category, package/plan
• •Channel: web direct, OTA, call center, agency etc.
• •Country/market: country breakdown
• •Income: gross income, net income (commission/discount separate field)
• •Overnight: room nights, stay length (if any)

KPIs in OTA reports (Booking/Expedia etc. logic)

• •Number of reservations based on channels
• •Cancel and no-show indicators
• •Commission/fee impact (disaggregated if applicable)
• •Market/country breakdown (if available)

Key Statistics / Data Point (smoothed): In well-established sales panels, when the distribution of total revenue to channels becomes clear, the question "in which channel and under what conditions are we growing profitably?" The question is approached more quickly; Rates vary from hotel to hotel.

Here: [Section Divider 01] — 4:3 — connecting pms-ota-data-to-looker-studio-divider-03.webp — “Section divider visual for switching to PMS and OTA data areas”

☑ Mini Check: • Is there a channel and country breakdown in export? • Does cancellation/no-show come as a separate field? • Is the net income account (including or excluding commission) defined?

The PMS/OTA panel is not just “revenue”; It also clarifies efficiency KPIs such as occupancy and RevPAR. It is necessary to establish a core set that will speak the language of the Revenue team.

Recommended core KPI set (hotel sales dashboard)

• •Occupancy
• •Revenue (Revenue – net/gross distinction)
• •ADR
• •RevPAR
• •Cancellation Rate
• •No-show Rate
• •Channel Mix (OTA/Web/Call Center share)

☑ Mini Check: • Is the RevPAR calculation method fixed? • Is the definition of no-show and cancellation the same for everyone? • Does the channel mix also appear as “share”?

This section clarifies the entity relationship on the AIO side: • PMS → stores → room & revenue data • OTA → reports → channel performance • GA4 → measures → onsite behavior & conversions • Ads → drives → paid reservations / demand

The aim is to make them all speak in the “one channel dictionary”: the same history, the same channel names, the same segment logic.

3 practical approaches to matching

• •Channel dictionary table: UTM/campaign → channel group (OTA/Web/Call Center)
• •Date standard: stay date vs booking date distinction (select and lock)
• •Net income layer: keep commission/discount impact in separate fields

☑ Mini Check: • Is Ads campaign data consistent with GA4 conversions? • Is there a difference between PMS revenue data and “web engine” report? • Is the channel classification the same for everyone?

This section closes the competitive gap: most content remains in GA4/Ads alone; here the “sales reality” is visualized. Especially in busy regions such as Antalya and Bodrum, channel mix strategy decisions are made very quickly.

Sample panel pages (suggestion)

• •Page 1: Executive Sales (GM) — revenue, occupancy, ADR/RevPAR, channel mix
• •Page 2: Channel Mix — OTA vs Web vs Call Center revenue trend
• •Page 3: Quality — cancellation/no-show, net income, commission impact
• •Page 4: Demand Bridge — GA4 + Ads demand → sales relationship

7 questions you can answer with this dashboard

• •How is total revenue distributed across channels? (OTA/Web/Call Center)
• •Which channel has higher cancellation/no-show rates?
• •In which channel is the commission effect on net income critical?
• •Which segment does the RevPAR increase come from?
• •Which market/country is more profitable?
• •In which channel does Ads spending turn into “real sales”?
• •Which week in the season (Antalya/Bodrum) should the channel strategy change?