Alpha.
Hand holding a cup on a wooden table near a round window facing a bamboo grove.

Written by Alpha Digital Agency· · Updated

Digital marketing audit checklist for hotels and villas in Bali

Explore a single reservation from the room page to payment. Audit checklist for hotel and Bali villa owners includes tracking, channel costs, and retesting.


Take one reservation that has already checked in. Ask the receptionist to show how the guest made the booking, the marketing team to show where the transaction is linked, and the finance department to show the final payment. If the three teams recognize the same reservation but mention different values, you have found the starting point for the audit. The difference can stem from tax, deposit, partial cancellation, or how the channel recognizes revenue. Record the difference before drawing conclusions about the ads.

Determine the work area and note the starting point

Start with property, check-in date range, room type, currency, and reservation status covered. Specify the date the data was taken. Reports that change continuously need to be saved as a temporary copy so meeting participants can see the same numbers. Remove guest name, phone number, and payment notes before sharing them. Use internal reference code so authorized staff can still trace the discrepancy back to the original system.

Identify the owner for each source. The receptionist checks the stay status, finances match the payment, and the digital team explains how the campaign earned credit. Agree on what falls under direct booking. Phone orders after a guest views the site need to be distinguished from payments completed in the booking engine. Record cases that cannot be classified in their own group. Forcing the channel origin on every transaction actually hides data limitations.

Check the information viewed by the guest

Open the room page from your phone like a new guest getting to know the property. Find the right location, room capacity, child rules, check-in time, and cancellation terms. Compare with the contents of the confirmation sent after booking. Save screenshots of the differences that change the guest's decision. Room titles that sound similar can refer to different capacity or views. Ask the reservation staff to show the name used in the system so the website team can fix the mapping.

Continue from search results or business profile to the referenced page. Check address, check-in pin, phone number, and official site address against property data. If the villa location is difficult to find at night, entrance photos and arrival instructions can help guests recognize it. To audit organic pages, separate information that actually helps choose a room from text that merely repeats keywords. Google SEO Starter Guide

Follow the reservation path to the end

Request permission to use the test inventory or agreed test reservation procedure for the property. Record the landing page, date, number of guests, room type, and cancellation policy. Proceed from the check availability button. See if that choice persists when switching from site to booking engine. If the date changes without notice, attach the step record that triggered the change. The vendor requires a repeatable sequence of events to fix it.

Note the moment the guest receives a reservation number. Transfer proof, success page, acceptance email, and confirmed status in the system may appear at different times. Ask who will contact the guest if payment is recorded but room confirmation has not appeared. Repeat testing after the fix and save the results together with the initial findings. For the transition check from site to booking system, see Alpha’s booking engine integration service.

Match event name with transaction

In an internal audit of a hospitality property in Bali, the Alpha team found an event named Purchase sent while the configuration uses purchase. The case-sensitive naming causes both events to be read separately. This audit note explains why the payment indicator must be tested against the actual configuration. The finding itself does not prove an increase in sales nor ensure how many bookings actually occurred. Google Analytics event naming rules

Take a test transaction and see if the same ID appears on the purchase event and the record in the booking engine. Check the currency and the amount sent, then reopen the confirmation page to detect double recording. Perform a refund test if the test environment allows. Write what is observed on each system. When there is a gap due to user approval or device switch, record the attribution limitation in the report. Google Analytics ecommerce documentation

Search costs and cancellation by channel

To check OTA costs, match completed reservations with commission invoices according to the property contract. Record the promotion deduction borne by the hotel, partial cancellation, and refunds. Compare with advertising costs, payment processing, and services the hotel actually paid for on direct reservations. Use comparable check-in dates. Write down tax treatment and variable cost decisions so that next month's calculation can be repeated in the same way.

Select a partial cancellation from the test data approved by the property. Explore how the changes appear on the number of transactions, the number of room nights, and the payment value. In the test list, write which column changed and when the last report was updated. If the check-in date has not passed, mark its value as temporary and assign who will confirm the results when the period closes.

Conversation test and handover to the receptionist

Select questions that truly often come in via the site or WhatsApp. For example, prospective guests ask about an extra bed, vehicle entry in the middle of the night, or a room on the ground floor. Prepare answers that have been checked by staff. Test whether the first response contains that information and whether the prospective guest knows who will follow up on matters requiring confirmation. Avoid including the guest's phone number or payment details in the shared audit notes.

If using automation, perform testing while the team is on duty and off-shift. Check how conversations are routed when answers depend on actual availability. The next staff member needs to know the arrival date, unanswered requests, and the response promise deadline. Ask agents to complete scenarios using the tools they use daily. Record the difference between automated answers and standard operating procedures, then provide owners with action for each difference.

Decide on one change and prove the result

Create a findings list with columns for journey stage, impact on guests, initial evidence, responsible party, corrective action, and retest results. Prioritize issues that block booking, cause incorrect payment, or make room confirmation difficult. Before changing the ad budget, check whether issues appearing as a drop in demand actually stem from untracked dates, sold-out rooms, or broken records.

To read reservation costs, divide the agreed cost by the number of reservations in the same group. If the divisor is zero, report the cost and the absence of reservations separately. To read ROAS, write the value attributed to the ad and the ad spend for the relevant period. Then look at commission, cancellation, and service fees so that decisions are based on the remaining money. The attribution model note helps explain why the platform number and property note can differ.

Close the audit with actionable decisions

Assign the process owner, not just the reporter. Provide one example of a reservation that was initially unmatched and the result after the fix. If a discrepancy remains, set the status to open, record the data needed, and set the date for the next review. The proof of approval for a broken button is different from the proof of approval for a commission error. Set the appropriate proof before closing each action on the findings list.

Save a readable summary during staff turnover. Include the reservation definition, report source location, how to reproduce the test, and the person who can explain the change history. At the next meeting, take a new sample of transactions for stays that have already taken place. Check whether old findings appear again or move to another part of the flow. With this note, the owner can distinguish tested improvements from work still waiting for vendor access.

Before marking as complete, perform one test using the link actually used by the prospective guest, such as the link on the business profile or the offer email. Testing only from the homepage may miss issues with links that have been shared for a long time. Check whether the date and package code are still valid, whether the page can be read without logging in, and whether the displayed contact is still active. Record when the test was performed and the inventory conditions at that time.

Suppose staff finds an active breakfast package on the room page but disappears when the prospective guest selects a check-in date. Attach a copy of both views and the package terms confirmation with the reservation section. Check whether the cause is date range, guest limit, or rate code mapping. After the vendor responds, ask a different staff member to repeat the same flow. This way, the test result does not depend on the knowledge of a person who already knows how to avoid that error.

Alpha Digital Hospitality Practice

Need a Google Ads and Direct Booking Audit for Your Property?

We audit OTA commission leakage, GA4 conversion tracking, and Google Ads connections to real hotel or villa reservations.

Related Alpha Digital Pages

Continue withDigital Marketing Bali

Explore all articles aboutDigital Marketing Bali

More from Alpha Digital

Related Articles

Call
WhatsApp
Email