- GA4
- GTM
- sGTM
- Google Ads
Booking takes visitors to an external platform with none of your tags
What is wrong
The ad leads to your website, and the booking is completed on an external booking platform – a separate service where you have no tags and cannot place them. In the reports that booking shows up as "direct" (the visitor came on their own) or as a referral from a site, and the ad that brought it gets no credit.
Example. In a month, ads brought 100 bookings, but 40 of them were completed on the booking platform. Google Ads sees 60. The ads learn from 60, the report shows a result almost twice as bad as the real one, and the budget gets cut in the campaign that brings bookings. The bookings that disappear are exactly the ones that reached payment, that is, the most valuable ones.
The legend in this demo: a network of travel agencies in Vietnam. The city site brings the customer, and the booking is completed on an external platform that carries none of our tags. All the businesses are fictional.
What the business loses
- The ad identifier is lost on the way to the platform. Google Ads and Meta optimise towards the conversions they can see. A booking that never makes it back to the ad platform does not exist for bidding.
- In analytics the sale is "direct". The booking shows up as direct or as a referral from the site. In the reports the ads look useless, and their budget is the first one cut.
- The ads learn on incomplete data. Without the bookings from the platform, the algorithm sees less than half of the result and steers the budget away from what actually brings payment.
Ways to close the gap
Which option you have is decided by the booking platform. Before choosing, answer four questions about it:
- Does it have an API your site can use to create bookings itself?
- Does it accept a journey code from the link (the code lets your server find which ad brought the visitor), store it on the booking and return it with the booking?
- Can its booking form be embedded on your site, and does the form tell your page that a booking was created?
- Does it send the customer back to your thank-you page with the booking number after payment?
Each "yes" opens an option from the table below. If all four answers are "no", what is left is matching by booking time – or your own booking form on your site instead of the platform.
| Option | Pros | Cons | Where it exists, examples | In the demo |
|---|---|---|---|---|
| Booking through the platform's API from your own site | The form is yours and the platform only receives the data: your site creates the booking through the platform's programming interface, and the visitor never sees the platform. The booking joins the journey at once, because your site creates it. You control both the form and what data goes to the platform. | You build and maintain the form. | Square Appointments, Acuity Scheduling, Cal.com, Mindbody; for tours – Bokun, Checkfront, Rezdy, Xola | open in the demo |
| A journey code stored on the booking: your site adds it to the link to the platform, the platform keeps it on the booking and returns it by webhook (an automatic notification to your server) | Reliable: the confirmed booking comes back with the journey code on it. | The platform needs a field for the code, and not every platform has one: FareHarbor states that no tracking information can be passed through parameters or cookies. | Calendly (UTM tags from the link are stored on the booking and sent in the webhook), Regiondo (Sub-ID in the link) | open in the demo |
| The platform's widget on your site: the platform's booking form inside your page, through the embed code the platform itself provides | The visitor stays on your site, while the platform still runs the form and the payment. When the booking is created, the widget tells the page, and the page joins the booking to the journey. | Not every widget tells the page about the booking – check the platform's documentation. Embed only with the code the platform gives you: a platform can forbid putting its pages on other sites, both technically and in its terms. | Calendly, Cal.com | open in the demo |
| Redirect back to a thank-you page | Simple: the thank-you page on your site recognises the visitor by your site's marker in their browser and joins the booking to the journey by its number. | Some platforms send the customer back to your site with the booking number after payment, some cannot – then this option is not available. | Calendly (can add the booking details to the address), Vagaro | open in the demo |
| Matching by booking time when the platform returns nothing | Works with any platform and needs nothing from it: the system looks at which site visitors could have made the booking at that time. | Unreliable, and it errs both ways. The booking misses the ad when the customer came from an ad but booked two days later from their phone. The booking goes to the wrong visit when several visitors were on the site in those minutes: a regular customer who came on their own can be credited to an ad visit. Better than nothing, but if the platform says "yes" to at least one of the questions above, that option is more reliable. | any platform | open in the demo |
| Your own booking form on your site instead of an external platform | The booking is created on your site, so the journey is known at once. No platform needed. | You build and maintain scheduling, payment, reminders and cancellations yourself. In some industries booking comes with legal requirements, such as how medical data is stored, or with data exchange with government systems – hard to rebuild on your own. | – | description only |
Examples are from the platforms' documentation as of September 2026. Features change, so check your own platform against its documentation.
What the demo does
In the demo you can book with any option from the table that has an "open in the demo" link. The option is the one you choose: through the link in the table or in the "Booking type" field below. The demo shows whether the booking was joined to the ad visit and how confidently.
The booking platform in the demo is a mock built for it, and its webhook is simulated by the demo server. The demo has no ready integration with your platform and sends nothing to Google Ads.
Open the demo
Use a private window for a clean run, because the consent regime and the booking option stick in the browser. The demo itself prompts where to click.
https://alpha.nexusnode.ru/?utm_source=GAds&utm_medium=CPC&utm_campaign=case_booking_platform&demo_click_id=GADS-11111&al_case=booking-platform&al_lang=en&al_transport=server&al_booking=reference&al_regime=auto&al_guide=1&al_reset=1About the author
I used to be a design engineer in the power industry. In 2013 I traded that for an online store, a loan from friends and ads that sold nothing. Things improved from there, mostly. Clients' businesses grew several times over, and a few even asked me to pause the ads so they could get a break from the phone. Thirteen years in, I still enjoy this more than is probably professional.
The long version, awkward bits included →
Book a call
Bring your website, booking platform or CRM. We trace the same journey on your systems and decide what is worth fixing first. If you walked through the demo, I open your journey record on the call: what was recorded, what was linked, what was lost.