How to Set Up Conversion Setup and Tracking in Google Ads for Hotels?

In the hotel funnel, “transformation” is not a single action. In addition to direct bookings, calls to the call center and WhatsApp chats also generate revenue. That's why you should consider transformations in two layers:

Primary conversions (business target – bid signal)

• •Reservation completed (booking engine purchase/booking)
• •Qualified phone call (e.g. 60+ seconds)
• •Qualified form (offer/booking form)

In Google Ads, primary conversions fall into the "Conversions" column and are the main signal that automatic bid strategies optimize.

Secondary conversions (micro/auxiliary – observation)

• •WhatsApp click
• •Room detail viewing
• •Price/availability display
• •Map directions click

Secondary conversions are ideal for demonstrating “intent” and “UX bottleneck” without inflating optimization.

Step blocks of 2–3 sentences readable in voice search (Voice-First):

• •First select your hotel's primary conversions (booking, qualified search, qualified form).
• •Generate relevant events in GA4 and mark the important ones as key events.
• •Set up and test tags with Google Tag / GTM; Then, separate the conversions into primary/secondary in Google Ads and apply them as the correct target for the campaigns.

GA4 now works “event-based”. The logic is this: first you generate the correct event, then you mark this event as "important" and report it. The step of marking an event as a key event in the GA4 interface is managed from the Admin > Events area.

Event name standard (practical scheme for hotel)

Assumption: You have TR/EN/DE/RU on your site; Event names should be kept language independent.

• •booking_complete (primary)
• •lead_form_submit (primary)
• •call_click (secondary → can be primary with call tracking)
• •whatsapp_click (secondary)
• •room_detail_view (secondary)
• •price_view (secondary)

In Google Ads, conversions are controlled by two critical layers:

• •Primary vs Secondary conversion actions (which one will be used for bid?)
• •Account-default conversion goals (which goals will be applied to campaigns by default?)

“Conversion Set” recommended for hotels (example)

• •Goal: Purchases/Bookings → booking_complete = Primary
• •Goal: Leads → lead_form_submit = Primary, whatsapp_click = Secondary
• •Goal: Calls → “calls from ads / website” = Primary (with attribute filter)

Note: Conversion goals groups conversion actions; Having “primary_for_goal” in an action goal affects the bid and “Conversions” report (Ads API logic also confirms this).

If you are going to set up Google Ads conversion tags with GTM, you take the Conversion ID and Label from the Google Ads conversion action and use them with the "Google Ads Conversion Tracking" tag in GTM. The official flow of web conversion setup starts with “Conversions on a website” and selects the appropriate connection method (scan / tag suggestion, etc.).

Hotel example: Reservation (booking_complete)

• •Trigger: “Reservation thank you page” or booking engine event
• •Tag: Google Ads Conversion Tracking
• •QA: test booking / debug view / Ads tag diagnostics

Assumption: If the booking engine is on a different domain, you will definitely apply the cross-domain section below.

In hotel sales, the phone call is often “high intent.” Google Ads offers different options for measuring phone calls as conversions: calls via ads, call assets/call ads, and call link clicks on the website.

Attribute filter (call length threshold)

Google Ads lets you use thresholds like “minimum search duration” to count a search as a conversion; This way you eliminate short/poor quality searches.

On hotel sites, the reservation engine is often a separate domain/subdomain. If cross-domain measurement is not set up correctly in GA4, when the user changes domains, it will appear as a "new session / referral" and attribution will be broken. Google's official guideline; It explains how to configure cross-domain measurement from Admin and verify that the same tag ID is used in the relevant domains.

Practical checklist for cross-domain

• •Web data stream tag ID (G-…): is it the same property/tag ID in all domains?
• •GA4 Admin > Data streams > Configure cross-domain: Has the booking engine domain been added?
• •Have referral exclusion / unwanted referrals been checked? (especially payment providers)

Technical Note (red line): If the cross-domain is incorrect, on the Ads side, "which campaign brought a reservation?" The report is also corrupted; because the underlying source/medium data is deviated.

The purpose of this blog is not to do OTA management; But in the measurement setup, you should accept OTA as "reality": sometimes the user sees it from OTA and comes to the site, or vice versa. For this reason:

• •Measure web conversions cleanly
• •Track call center conversions separately
• •Put the “web + call + lead” set under a single roof in reporting (Internal Link: /digital-analysis/digital-sales-analysis)

Set-A (Direct booking focused – resort)

• •Primary: booking_complete, qualified call_conversion
• •Secondary: whatsapp_click, room_detail_view, price_view

Set-B (Lead + offer focused – boutique / low season)

• •Primary: lead_form_submit, qualified call_conversion
• •Secondary: whatsapp_click, availability_check

Don't forget the "Primary/Secondary" rule

Primary = optimization signal; Secondary = observation.

Word Count target: 2300–2700 band.