01

Quick answer

A booking click is not a completed reservation, and a reservation is not an arrival. Build the tracking chain around the restaurant’s real operating stages. Then show where attribution is strong, partial, or missing instead of forcing one precise answer from disconnected systems.

02

Define the booking stages

Use consistent definitions for menu view, booking start, completed booking, confirmation, cancellation, no-show, arrival, covers, spend, and repeat visit. Decide which system owns each stage. The booking platform may hold reservations, the point of sale holds spend, and the CRM or guest system holds permission and history.

Use stable booking identifiers where available. Avoid relying on names or telephone numbers in general analytics tools.

03

Tag every controlled route

  • Add UTM parameters to ads, social profiles, creators, email, Maps links where possible, and partner placements.
  • Use distinct landing or booking links for important campaigns and locations.
  • Record a booking-start event on the restaurant domain when the handoff begins.
  • Pass permitted source context into the booking platform when it supports it.
  • Use controlled call tracking or host source fields for routes that leave digital gaps.
  • Keep naming consistent across campaign, analytics, booking, and reporting systems.
04

Reconcile the systems

Export campaign, analytics, booking, and point-of-sale data for the same period and timezone. Match on safe identifiers and timestamps. Report matched, unmatched, duplicated, cancelled, and missing records. Do not silently drop bookings that cannot be connected.

Review the handoff with operations. A sudden fall from booking start to completion may be an availability, mobile, or booking-platform issue. A fall from confirmation to arrival may require reminders, deposits, or policy changes rather than more advertising.

05

Explain attribution limits

Guests may see creator content, search later, click a map listing, call, and arrive with friends. Last-click reporting sees only part of that path. Use booking questions, controlled links, incrementality tests, location or daypart patterns, and customer research as supporting evidence. State which conclusion is an observation and which is an inference.

06

Decision checklist

  • Are stages and systems defined before campaign launch?
  • Do important links use a consistent naming convention?
  • Can a booking identifier connect reservation and arrival safely?
  • Are cancellations, no-shows, and duplicate bookings visible?
  • Does reporting show match rate and missing data?
  • Are consent, access, retention, and deletion processes documented?
07

Improve one handoff at a time

Start with one paid campaign, one booking route, and one location. Reconcile it manually, fix the largest data break, then automate only the fields that proved useful.

Sources and evidence note

  1. Google Ads conversion trackingsupport.google.com
  2. Google Business Profile performancesupport.google.com

Something changed or looks wrong? Point us to the claim and the strongest source.

Request a correction