BookingBridge An instrument of record · built by Second Step
File no.BB-2026-07-A
IssuedJuly 2026
StatusOPEN — UNRECONCILED

Re: The bookings your Google Ads cannot prove

Prepared for: the owner of a vacation rental company running Google Ads with an off-site booking checkout

1Summary of findings

  1. 1.1Google Ads keeps a record of clicks. Your property management system keeps a record of bookings. On most vacation rental websites, no record connects the two.
  2. 1.2The disconnect occurs at checkout, where the guest leaves your domain for the booking engine and Google's click ID is destroyed in transit. (Exhibit A)
  3. 1.3Revenue that originated with a paid click is therefore recorded as Direct / (none). In the account examined for this file, 74% of booking revenue was filed this way.1
  4. 1.4The condition is repairable. Where the click record is captured first-party and joined to the booking ledger, provable revenue emerges. (Exhibits B and C)

Action available to the reader: the same examination can be performed on your account, without charge. See section 6, Request of audit.

2Exhibit A — where the record breaks

Figure 1. The cross-domain hop. Google reports the click, the PMS reports the booking, and nothing connects the two. The ads may be working; the proof does not survive the journey.

3Exhibit B — one booking, fully evidenced

Reproduced from the first deployed account: the complete evidence trail of a single reservation. Identifiers are redacted; amounts are not.2

Booking file ····-7219 · ██████ ███████, party of 6 TIER: VERIFIED
Jun 05 Guest arrives via Google Ads, Brand campaign. Click ID captured first-party on landing. gclid Cj0KCQjw██████
Jun 05 Inquiry submitted for a beachfront estate. Identity recorded and normalized. ████████@█████.com
Jun 09 Reservation confirmed in the property management system. Order total recorded. $37,219.00
Jun 09 Matcher joins the click record to the confirmation on click ID + identity. No inference used. MATCHED · VERIFIED
The same booking, as recorded by analytics before repair: Direct / (none)

This is one of three reservations, together worth $100,646, proven against ad clicks in this account. All three had been filed under Direct.

4Exhibit C — the reconciliation

The account's Google Ads position for March through June, stated two ways: as Google models it, and as the captured evidence proves it.

Google Ads spend, as billed $28,038.00 invoiced
Booking revenue Google attributes to the ads $514,917.00 modeled, unverifiable3
Booking revenue proven with captured evidence $100,646.49 3 bookings, deterministic
Booking revenue accounted for, tier by tier 100% nothing counted twice

The two revenue figures will never agree. Only one of them survives scrutiny from an owner, a partner, or an accountant. Note also the repair record: before intervention this account captured the click ID on 0% of ad visits; within four weeks of one corrective deployment, 37.5% of the week's visits carried it. The working target is 60%.

5The instrument

BookingBridge is the system that produced the exhibits above. It is deliberately small: one tag on your website captures the click record first-party; the service reads spend from Google Ads and confirmations from your property management system every fifteen minutes; a matcher joins the two ledgers and labels every match with the strength of its evidence. It produces the one line this file is built around, spend against proven revenue, continuously.

VERIFIED
Click ID captured and matched to the confirmed booking.
LIKELY
The guest's email or phone bridges an ad-tracked inquiry to the booking.
ASSISTED
Ad parameters present on the visit; the click ID itself unrecoverable.
UNKNOWN
No ad evidence. Never counted, always disclosed.

When a booking cannot be proven to have come from your ads, the file says so. That is the entire point.

6Request of audit

We will prepare this file for your own account: the share of your booking revenue sitting in Direct, whether your checkout destroys the click ID and where, your capture rate today, and the repair plan in order. Prepared by a person with the instrument, returned within five business days, without charge or obligation. One report, no drip campaign.

A valid email is required to return the file.
The audit is performed against your website.
First-party only. Your details are used to prepare the file and for nothing else.

7Anticipated questions

Is this not what GA4 already does?
No. GA4 loses the click at the checkout hop and models what it does report. This instrument captures the click first-party and counts only what it can prove.
Does it replace the agency running our ads?
No. It is the referee, not a player. Whoever runs the ads keeps running them; the file states what they can be proven to have booked.
Which property management systems are supported?
Hostfully, natively, today. The matcher is system-agnostic by design; adapters follow demand. Name yours in the request.
Is a developer required?
No. Installation is one tag in Google Tag Manager, done with you, typically in under fifteen minutes.
What of bookings made by phone or email?
Phone and email are first-class identities in the matcher. A guest who clicks the ad and books by phone two weeks later can still be connected, and the match is labeled accordingly.

Prepared and maintained by

BookingBridge

an instrument built by Second Step · July 2026