Conversion tracking for Clubspeed
Booking Manager shows a full Saturday of races, lanes and party packages. Google Ads shows a handful of conversions, Meta a different handful. Clubspeed documents a GA4 connection and a GTM container for Club Booking, both finished by its support team, and nothing for Google Ads or Meta. We build on those two hooks and prove it on a real reservation.
Free30 minutesNo obligation
Clubspeed · what breaks
What goes wrong with Clubspeed
- 01
The checkout lives on Clubspeed's domain, not yours
Clubspeed's GA4 guide has you add the ClubBooking domain for cross-domain measurement, because the guest leaves your site to pay. Miss that linker and Google Ads sees a click that never converts, then keeps bidding on it.
- 02
Nobody finished turning tracking on
The GA4 and GTM integrations need an ID entered in Director and emailed to support to be plugged in. Skip the email and the Purchase step fires for nobody, so Meta optimizes on pricing-page views.
- 03
A $50 deposit counted as a $500 party
Club Booking lets guests book without paying in full. Value the conversion at what was charged online and a birthday party for twelve looks cheaper than two adults booking a race.
- 04
Reschedules and walk-ups muddy the count
A guest can modify a reservation from the confirmation page; the booking is edited, not recreated. Phone and front-desk bookings never touch the booking site. Count the first twice and miss the second, and the platforms learn from the wrong week.
Clubspeed · the fix
What changes — Clubspeed
The click survives the jump to Club Booking
The Google click ID is carried into the booking domain, so the Purchase step is credited to the ad that earned it.
Conversions valued from the booking, not the charge
Each reservation reports the full package value with the deposit noted separately. A party is worth a party.
Every reservation counted once at every platform
One event per booking confirmation code, shared across browser and server, so Google Ads and Meta match Booking Manager.
Clubspeed · architecture
What Clubspeed actually lets you hook into
Clubspeed documents two tracking integrations for Club Booking, both enabled in Director and finished by support. Everything else is confirmed on your account first.
- 1
GA4 integration (documented)
Director > Integrations > Google Analytics, Measurement ID emailed to support@clubspeed.com. Documented events: page views, view filter, view product offering, add to cart, checkout, the "Your Details" and "Confirm & Pay" steps, remove from cart, purchase. Value and transaction ID aren't documented, so we verify them live.
- 2
Cross-domain measurement (documented)
Clubspeed points you to Google's cross-domain guide and tells you to include the ClubBooking domain. The checkout runs off your site, so a linker has to carry the click ID across.
- 3
GTM container on the booking site (documented, gated)
Director > Integrations > Google Tag Manager, container ID emailed to support, repeated per location. The article sits behind a login and publishes no data layer, so we read what the container can see live on your booking pages.
- 4
Booking records by API (confirm on your account)
Third-party connectors read Clubspeed through a per-venue clubspeedtiming.com subdomain and a private key from support, with booking, checks, payments and customers tables. We confirm access on your license before relying on it.
- 5
No native Google Ads, Meta or offline conversion tools
Nothing in the help center covers a Google Ads conversion tag, Meta Pixel or Conversions API, webhooks or Zapier. We build those in the container and from your records.
Clubspeed · diagnose
Where Clubspeed tracking breaks, in diagnostic order
Start at the integration switches, because nothing fires on Club Booking until support has plugged your ID in.
- 01
Is the GA4 or GTM integration actually live?
An ID typed into Director isn't live until support plugs it in. We confirm the tag loads on the booking domain.
- 02
Does the click ID cross to the ClubBooking domain?
Open the booking site from an ad-tagged link and check for the linker parameter on arrival.
- 03
Does the Purchase step fire, and with what value?
One deposit booking and one paid-in-full, compared with what each platform recorded.
- 04
Are reschedules or refunds counted again?
Modify a test reservation from the confirmation page and watch for a second conversion.
- 05
Which locations are covered?
Clubspeed configures GA4 and GTM per location, so each site is checked on its own.
Clubspeed · prove
The QA evidence — Clubspeed
Run on the live Club Booking site your guests use, with one deposit booking and one paid-in-full booking.
Source of truth
Booking Manager in Clubspeed — your online reservations, matched by booking confirmation code against what each ad platform recorded
- One reservation from an ad-tagged link, click ID confirmed on the booking domain and on the conversion.
- One Google Ads conversion and one Meta event per confirmation code, shared event ID visible in Events Manager.
- Package value and deposit both on the conversion, matching the product offering.
- A reschedule from the confirmation page produces no second conversion.
- A Booking Manager refund reversed wherever the platform supports it.
- A closed week matched reservation by reservation against Booking Manager.
- Repeated 30 days later and after any change to product offerings or booking settings.
Clubspeed · free audit
What we check in the free audit
- Is the GA4 or GTM integration actually live?
- Does the click ID cross to the ClubBooking domain?
- Does the Purchase step fire, and with what value?
- Are reschedules or refunds counted again?
- Which locations are covered?
Checked against
Booking Manager in Clubspeed — your online reservations, matched by booking confirmation code against what each ad platform recorded
Free30 minutesNo obligation
Clubspeed · when not to buy
When you don't need this on Clubspeed
Some venues are better served by finishing Clubspeed's own setup than by hiring us.
- If you haven't emailed a Measurement ID or GTM container ID to Clubspeed support yet, do that first. It's free, and it may be the whole problem.
- If most revenue is walk-up races and league nights, the online count stays small however well it's tracked.
- If you run one Google Ads campaign and the GA4 purchase event already matches Booking Manager week to week, leave it alone.
- If bookings arrive in Briq.app and get keyed into Clubspeed by hand, fix that before adding ad tracking on top.
Clubspeed · what we deliver
The event map on Clubspeed
Product offering viewed
Clubspeed's own "View product offering" step, with the campaign that sent the guest.
Time slot added to cart
Leading signal with activity and party size, never the optimization target.
Reservation confirmed
The conversion. Fires on "Confirm & Pay" completion with the booking confirmation code as transaction ID.
Deposit versus full payment
Both on one event: the amount charged today and the full package value.
Gift card purchase
Its own event from Clubspeed's gift card portal, kept out of the reservation count.
Reschedule, refund and no-show
A reschedule leaves the conversion alone. A Booking Manager refund reverses it wherever the platform allows.
Written guarantee
95%+ tracking accuracy
Measured against Booking Manager in Clubspeed — your online reservations, matched by booking confirmation code against what each ad platform recorded. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Clubspeed questions, answered
Not a documented one. Clubspeed covers a GA4 integration and a GTM container for Club Booking, both finished by support. Google Ads and Meta tags go inside that container, which is what we build.
Usually the click ID never crosses to the ClubBooking domain, or the integration was entered in Director but never plugged in by support. Both show on the first test booking.
Only if a Meta tag runs on the booking site; Clubspeed doesn't document a Pixel of its own. We place it in the GTM container Clubspeed loads and send the same reservation server-side with the guest's email.
They never touch Club Booking, so no browser tag sees them. The full stack's offline loop matches them from your Clubspeed customer records and uploads them to Google Ads and Meta.
Three in Director, because Clubspeed's GA4 and GTM guides repeat the steps per location. The server-side build is shared, with the location passed on every reservation.
More on Clubspeed
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside Clubspeed, and what their bookings feed
- CleanCloudCleanCloud pickup orders not showing in Google Ads? Here's the fix.
- SpectoraSpectora conversion tracking: see which ads book inspections, not which agents
- DockMasterDockMaster conversion tracking: your ads ring the dock office, but which ones actually fill slips and sell boats?
- EnrollsyConversion tracking for Enrollsy
- SiteLinkGoogle Ads counts reservations. SiteLink counts move-ins. Which ads actually fill your units?
- OrderryOrderry conversion tracking: see which ads book repairs, not just clicks
- FormFoxConversion tracking for FormFox: your ads win the employer, the collection shows up in Workforce days later
- PoshPosh tickets are selling, but your ads can't tell which ones they sold
