Booking Widget Attribution

Cloudbeds Immersive Experience 2.0 launched in early 2026 with documentation explicitly placing Google Ads conversion tracking responsibility on the property’s WordPress site. The redirect from the hotel’s domain to the booking engine drops gclid before any conversion pixel can fire, leaving Google Ads dashboards with zero confirmed bookings while GA4 shows reservation revenue from the same guests. The fix is server-side: capture gclid in a first-party cookie on the hotel’s subdomain, persist it through the Cloudbeds confirmation webhook, and replay it to Google Ads via Enhanced Conversions when the booking arrives. This architecture restores attribution without GTM expertise.

Calendly’s embed is a third-party iframe, so the browser’s same-origin policy kills your Google Ads GCLID the moment a visitor clicks in — which is why bookings show as “calendly.com / referral” in GA4 and zero conversions in Google Ads. Every browser-side fix (GTM postMessage listeners, redirect pages, Calendly’s built-in GA hit) is either fragile or loses the GCLID. The durable pattern: capture the GCLID server-side when the ad click lands on WordPress, then match Calendly’s booking webhook to it and submit a Google Ads offline conversion. Same architecture works for Cal.com, Acuity, HubSpot Meetings, and Chili Piper.