How to track bookings back to Google Ads

The defining measurement problem in travel is time and channel. Someone clicks an ad on a Tuesday, submits an enquiry, moves to WhatsApp, discusses it with family for two weeks, calls your office, and confirms a booking over a phone call. The revenue is real. As far as Google Ads is concerned, it never happened.

Offline conversion import exists to close that gap. It is not new, it is not difficult, and a surprising number of travel accounts still do not use it.

How it works, conceptually

When someone clicks a Google ad, Google appends a click identifier — the GCLID — to your landing page URL. If you capture and store that identifier with the enquiry, you can later hand it back to Google along with an outcome and a value. Google then attributes that outcome to the original click, campaign, keyword and device.

The chain is: capture the GCLID, store it against the lead, record the outcome, upload it back. Break any link and the chain fails silently.

Step 1 — Capture the click identifier

On your landing page, read the gclid parameter from the URL and write it to a first-party cookie with a 90-day lifetime. Also capture wbraid and gbraid, which appear in place of GCLID for certain iOS app-to-web journeys.

Then add a hidden field to every enquiry form that reads from that cookie and submits alongside the form data. Do the same for your UTM parameters while you are there — you will want them for reporting even where they are not needed for import.

Step 2 — Store it in the CRM

Create fields on the lead record for the click identifier, the source, the campaign and the enquiry timestamp. These must survive the lead being reassigned, merged or converted to a deal — if your CRM drops custom fields on conversion, fix that before going further.

Where leads arrive through Meta lead ads or click-to-WhatsApp there will be no GCLID. That is expected; those leads are handled separately through Meta's own offline events.

Step 3 — Define the conversion actions

In Google Ads, create import conversion actions matching the stages that matter in your pipeline. A workable set for a travel business:

• Qualified Enquiry — sales confirmed this lead is workable. Assign a value equal to your average booking value multiplied by the historical qualified-to-booked rate.
• Quote Sent — an itinerary and price were issued. Useful as a mid-funnel signal in long cycles.
• Booking Confirmed — payment received. Assign the actual booking value.

Set Booking Confirmed as your primary conversion once it has enough volume. Until then, use Qualified Enquiry as primary — a signal that arrives in days at reasonable volume is more useful to a bidding algorithm than one that arrives in weeks at low volume.

Step 4 — Upload the outcomes

You have three options, in ascending order of reliability:

1. Manual CSV upload. Fine to prove the concept. Unsustainable as a routine.
2. Scheduled import from Google Sheets or a hosted file, refreshed automatically. A reasonable middle ground.
3. Direct API integration via your CRM's native Google Ads connector or an automation layer. The right long-term answer.

Whichever you use, upload at least weekly. Google accepts conversions up to 90 days after the click, which comfortably covers most travel decision cycles, but delayed uploads slow down how quickly bidding can learn.

Step 5 — Add enhanced conversions for leads

Enhanced conversions for leads cover the cases where the GCLID went missing — a lead who cleared cookies, switched devices, or came through a path where the identifier was lost. Instead of matching on the click ID, Google matches on hashed first-party data such as email or phone number, collected at the point of enquiry.

The hashing happens before anything leaves the browser or your server, so raw personal data is not transmitted. You do need a lawful basis and a privacy policy that discloses the practice — treat that as a requirement, not a formality.

Run enhanced conversions alongside GCLID-based import, not instead of it. Together they recover materially more bookings than either alone.

What changes once this is live

Three things, usually within six to eight weeks.

Your reported conversion counts drop, because you are now counting bookings rather than form submissions. This is correct, and it is worth warning stakeholders in advance.

Campaign rankings reshuffle. Campaigns that looked efficient on cost per lead frequently turn out to produce few bookings, and vice versa. This reshuffle is the entire point — it is the first time you have been able to see it.

And Smart Bidding starts working in your favour. Target CPA or Target ROAS against a real booking signal behaves very differently from the same strategy chasing form fills. The algorithm was always competent; it was being pointed at the wrong target.

A note on honesty

Attribution will never be perfect. Some bookings genuinely cannot be traced — walk-ins, referrals from a past traveller, a phone call from a number you have never seen. Going from roughly zero visibility to a substantial and improving majority is a transformative change in decision quality. Chasing the final few percent is usually not worth what it costs.