Track which bookings come from Google, honestly
A park can know which clicks came from its profile, which pages produced inquiries, and where the trail goes cold. This is the whole setup, including the cold parts.
By Korey Brooks · Published August 29, 2026
To track RV park bookings from Google, do three things. Tag the Business Profile links with UTM parameters. Mark booking and inquiry actions as key events in GA4. Reconcile monthly against the booking engine's own report. That three-part setup shows which visits came from the profile versus the search results, and which of those visits turned into action. It will not show everything. Calls, direction taps, and most booking-engine checkouts sit partly or fully outside the park's analytics, and pretending otherwise produces confident numbers that are wrong.
The honest version is still worth an afternoon. A park that runs this setup stops guessing whether the profile work matters. It sees which pages earn inquiries, and it walks into marketing decisions holding its own data. The guide runs from the trackable to the untrackable, in that order.
What is trackable, and what is not
Start with the map of the possible, because the biggest tracking mistake is chasing a number that does not exist.
| Camper action | Trackable? | Where the number lives |
|---|---|---|
| Clicked the profile's website link | Yes, fully | GA4, via the UTM tag |
| Clicked the profile's booking link | Yes, to the handoff | GA4 plus the booking engine's report |
| Called from the profile | Partly | Profile performance report; the phone log has the rest |
| Tapped directions and drove in | Counted, not connected | Profile performance report only |
| Booked inside the booking engine | Depends on the platform | The engine's own attribution, if it keeps one |
| Saw the park in an AI answer | No | Nowhere reliable yet |
Two rows deserve emphasis. Directions taps are real demand that never touches the website, common for parks near interstates. A park with strong direction-tap counts and weak website numbers is winning on Maps and does not need to panic about the site. And booking-engine checkouts happen on another company's domain, which is where most park analytics quietly stop measuring. Both gaps have workarounds below.
The UTM convention, once and forever
UTM parameters are labels added to a link so analytics can name where the click came from. The profile needs exactly two tagged links, and the convention matters more than the choices. Pick once, document it, and never improvise a variant.
- Website link: add ?utm_source=google&utm_medium=organic&utm_campaign=gbp-listing to the homepage URL.
- Booking link: same source and medium, with utm_campaign=gbp-booking so the two links separate cleanly in reports.
- Paste each tagged link into a browser and confirm the page loads normally before saving it to the profile.
Two technical cautions keep the convention safe. The website's canonical tags must point to the clean URL without parameters. That keeps tagged versions from registering as duplicate pages, and a correctly built site already does this. And tagged links belong only on the profile, never in the site's own navigation or sitemap. Internal links carrying UTM tags overwrite the true source of a visit and corrupt the very report being built.
Key events in GA4, kept small
Traffic numbers alone answer nothing. The report becomes useful when the actions that matter are marked as key events: the audit or inquiry form submission, the booking-link click out to the engine, and the phone-number tap on mobile. Three is plenty. Parks drowning in fifteen events read none of them, and the three above cover every action a camper can take that the park can answer.
One privacy rule rides along: no personal information in analytics, ever. Names, emails, and phone numbers stay in the inquiry system where they belong. The event records that an inquiry happened and which page produced it, which is everything the marketing question needs and nothing a privacy policy regrets.
The booking-engine handoff
The moment a camper leaves the park's site for the reservation platform, tracking changes owners. Some platforms accept cross-domain measurement, some report their own referral sources, and some report nothing attributable at all. The workaround is reconciliation rather than plumbing. Each month, set the booking engine's total reservations beside GA4's booking-link clicks and profile-link visits. The ratio between clicks and completed bookings stays roughly stable at most parks, so movements in it flag real changes worth investigating.
Ask the platform two direct questions: does it record where each reservation's visitor came from, and can that report be exported monthly. Platforms differ widely here, and the answer is worth knowing before believing anyone's attribution claims, including Google's.
Parks taking reservations by phone and form, without an engine, have it simpler. The form submission is the trackable conversion, the phone log is the rest, and the reconciliation step collapses into matching inquiries against the reservation book. Fewer moving parts, same monthly habit, same honesty about what the numbers can and cannot say.
Calls and directions, the offline half
The profile's performance report counts calls and direction requests, and those counts are worth logging monthly even though they connect to no individual booking. For the call half, the park's own phone log adds the texture the profile cannot: when calls came, how many went unanswered, and what the misses cost. That method has its own guide in how to measure missed booking calls, and it pairs naturally with this one.
The front desk completes the offline picture with one question asked at every check-in: how did you find the park. Tally the answers for a month. The tally is unscientific and still the best attribution a park owns. It counts the campers who called, drove in, or booked through the engine without touching a tagged link. Analytics counts clicks; the front desk counts people.
The monthly reading habit
The setup pays through a fifteen-minute monthly read of five numbers: profile-link visits, booking-link clicks, key events, the engine's reservation total, and the front-desk tally. Fifteen minutes is the honest budget, because the habit dies the month it takes an hour. Log them in one row per month. Keep the row in the same spreadsheet as the review count and the missed-call totals. The whole marketing picture then reads on one screen. Trends across three rows answer the questions that matter: whether profile work is producing visits, whether visits are producing action, and whether the booking path is leaking between the two. The broader site checks that keep those numbers honest live in the RV park SEO checklist.
Setting the baseline before judging anything
Every number in this guide misleads without a baseline. A new tracking setup should run for one full month untouched before anyone draws a conclusion from it. Seasonal parks should mark which weeks sat inside season, because a September-to-October comparison at a summer park measures the calendar, not the marketing. Write the baseline month's five numbers at the top of the log and date them. Every later month gets compared to that row and to the same month last year once the log is old enough to have one.
Baselines also protect against the classic attribution trap: crediting whatever changed most recently. Profile visits that doubled the week a highway closed reopened have an explanation that is not the new photos. The log plus a one-line notes column, weather, events, closures, catches most of these before they become beliefs.
What AI search changes, and what it does not
Campers increasingly meet parks inside AI-generated answers, and those encounters mostly evade measurement. No reliable report yet shows how often an AI answer named the park or what the camper did next. The working response is indirect. Keep the profile, the reviews, and the site facts accurate, because answer engines draw on the same public signals. Then watch for visits that arrive with no search trail. Some analytics reports label these as direct or unassigned traffic. A rise there alongside steady rankings is consistent with answer-engine exposure, and that cautious phrasing is as far as honest measurement currently goes.
Questions owners ask about tracking
Does adding UTM tags to profile links affect rankings?
No ranking effect is documented, and the tags change nothing about the page itself. The one technical requirement is a canonical tag pointing at the clean URL, which prevents the tagged link from registering as a duplicate page. Any competently built site already handles this.
Can a park see which search terms produced bookings?
Partially. Google Search Console shows which queries surfaced the site and which earned clicks, and the profile report shows searches that surfaced the listing. Neither connects a specific query to a specific reservation. Treat query data as demand intelligence, not attribution.
Is call tracking with a replacement number worth it for a campground?
Sometimes, with one caution: the replacement number must never contaminate the profile's primary number consistency. Use the profile's own call reporting first. Add tracking numbers only in paid campaigns, where the number lives outside the listing and threatens nothing.
What tool budget does this setup need?
Zero. GA4, Search Console, the profile's performance report, and a spreadsheet cover the whole guide. Paid dashboards earn consideration only after the monthly habit exists, because tools multiply attention rather than replace it.
Measure the path, then improve it
Tracking exists to aim effort, and the first month usually reveals one obvious leak: a page that earns visits without inquiries, or clicks that never become reservations. Fix the named leak first, and resist fixing three things at once, because the next month's numbers cannot then say which fix worked. The free Website and Search Audit runs this outside-in, reviewing the park's site, visibility, and measurement setup, by email, within one business day.