Conversion tracking for Lodgify direct bookings
A Lodgify website sends the guest to checkout on a different URL from the one they browsed, and that hop is where most direct-booking attribution quietly dies. Lodgify's own GA4 connection reports bookings and revenue, which is a real help, but GA4 is not where Google Ads or Meta learn. Unless the booking is passed on with its value and the original click, the ads optimize on page views of your listings.
Free30 minutesNo obligation
Lodgify · what breaks
Where Lodgify bookings slip out of the ad accounts
- 01
Checkout lives on another URL
GA4 starts a fresh session there unless the hop is handled, and the booking gets credited to a referral.
- 02
GA4 revenue that never reaches the ad platforms
The native link reports to Analytics. Meta sees nothing, and Google Ads only sees it if someone imports it properly.
- 03
A seven-night stay weighted like a one-night stay
Without the booking total on the conversion, bidding cannot tell a weekend from a fortnight.
- 04
Cancellations that stay counted
A guest who cancels next month is still a conversion in every platform unless it is reversed.
Lodgify · the fix
After the rebuild — Lodgify
Each direct booking reported once, with its total
So bidding learns which listings and dates pay.
The click identifier kept through the checkout hop
Confirmed on a live reservation, not assumed from preview mode.
Cancelled stays taken back out
Matched to the reservation they came from.
Lodgify · architecture
What Lodgify actually lets you do
Only what Lodgify documents. Anything we could not confirm is written as a check, not a promise.
- 1
A native Google Analytics connection
Turned on under Tools > Marketplace. It is the supported way to get GA4 onto a Lodgify website.
- 2
Booking conversions and revenue in GA4
Lodgify states these are tracked on its websites since the GA4 migration. Confirm the value matches the reservation.
- 3
A checkout on its own URL
The step that needs referral exclusion and cross-domain handling, or the session breaks in two.
- 4
Check whether a GTM container or Meta Pixel can be added
Neither shows up in the Lodgify material we read, so it gets tested on your plan before anything depends on it.
- 5
No sending to ad platforms of its own
Nothing we found says Lodgify pushes bookings to Meta or Google Ads directly.
Lodgify · diagnose
Diagnosing a Lodgify site, step by step
Start at the checkout hop and work outward. Most problems on Lodgify show themselves in the first two checks.
- 01
Book a test stay and follow the session across the checkout URL
If GA4 shows a new session or a self-referral, the hop is the leak.
- 02
Compare GA4 purchases against website reservations
Per reservation, for a closed month.
- 03
Check what Google Ads is actually importing
A page-view goal or a GA4 key event without value are both common.
- 04
Look for a second GA4 tag
A hand-pasted tag alongside the Marketplace link doubles every booking.
- 05
Count cancellations that are still conversions
On longer-lead stays this gap grows every month.
Lodgify · prove
How we show it works on Lodgify
We book a real stay on your Lodgify site, cancel it, and watch both reach the ad platforms.
Source of truth
The reservations list in Lodgify, filtered to bookings made on your website
- A test reservation traced from ad click through the checkout URL to the confirmation, with the identifier intact.
- Every website reservation in the window paired with its Google Ads and Meta conversion, and the unpaired ones explained.
- Booking value checked against the reservation total, including fees.
- A cancellation confirmed to reverse the original conversion.
- Channel bookings confirmed absent from the ad conversions.
- Re-checked 30 days later on a fresh set of reservations.
Lodgify · free audit
What we check in the free audit
- Book a test stay and follow the session across the checkout URL
- Compare GA4 purchases against website reservations
- Check what Google Ads is actually importing
- Look for a second GA4 tag
- Count cancellations that are still conversions
Checked against
The reservations list in Lodgify, filtered to bookings made on your website
Free30 minutesNo obligation
Lodgify · when not to buy
When Lodgify's own GA4 link is enough
Not every Lodgify owner needs a server-side build.
- If you do not run paid ads and only want to see bookings and revenue, the native GA4 connection already does that.
- If almost all of your stays come from channels rather than your website, direct-booking tracking has little to measure.
- If you spend a small amount on Google Ads only, importing the GA4 booking event with value may get you most of the way.
- If you are a single property with a handful of direct bookings a month, a careful check of the checkout hop is cheaper than a rebuild.
Lodgify · what we deliver
The Lodgify event map
Listing viewed
Which property and which dates the guest looked at.
Checkout started
Fires on the checkout URL, carrying the stay dates.
Booking confirmed
The conversion, at the reservation total in USD.
Nights and guests
Attached to the booking so value per night can be compared.
Booking cancelled
Reversed against the original conversion.
Direct versus channel source
Kept apart so only website bookings count as ad conversions.
Written guarantee
95%+ tracking accuracy
Measured against The reservations list in Lodgify, filtered to bookings made on your website. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Lodgify questions, answered
Not by itself. It reports to GA4; Google Ads only sees bookings if the GA4 key event is imported or a conversion is sent separately, and either way it needs the value on it.
Lodgify's documentation, as far as we could find, does not describe a pixel field, so we try it on your account first. If the website cannot carry it, Meta gets the booking from the server instead.
Because checkout runs on a different URL. Without referral exclusion and cross-domain setup, the session restarts there and the original source is lost.
The reservation total in dollars, with nights and guests alongside. If you take a deposit, send the full booking value and handle the balance separately so campaigns are compared fairly.
They should not be. We keep conversions to reservations made on your Lodgify website, so channel bookings stay out of the ad accounts.
More on Lodgify
- Lodgify → Google AdsConnecting Lodgify to Google Ads
- Lodgify → MetaConnecting Lodgify to Meta Conversions API
- Lodgify → GA4Connecting Lodgify to GA4
RELATED GUIDES
Booking tools beside Lodgify, and what their bookings feed
- Hospitable (Direct)Hospitable Direct: tracking the booking, not just the visit
- HostfullyConversion tracking for Hostfully direct booking sites
- RMS CloudConversion tracking for the RMS Cloud booking engine
- Meta · Vacation rentalsMeta Ads conversion tracking for vacation rental management companies
- Google Ads · HotelsGoogle Ads conversion tracking for hotels
- Meta × Booking SystemHow to reconcile Meta Ads against your booking or reservation system
- Meta · Abandoned cart → recoveredHow to track cart abandonment to recovered sale for Meta Ads
- Vacation rentalsConversion tracking for vacation rental managers, on both sides
Free · 30 min
Put Lodgify's direct bookings where your bidding can use them
Free30 minutesNo obligation
