How to Capture Google Analytics Data in OnceHub Bookings
Google Analytics shows traffic and sessions, but it does not tell you which booking came from which campaign. This guide explains how to attach source context to each OnceHub booking using a third-party attribution tool, then how to route and report on that data so you can compare channels by meetings rather than visits.
What the attribution layer adds to a OnceHub booking
The attribution tool is a third-party service that runs as a small script installed on your site. On each visit it reads signals such as UTM parameters and referrers, groups the visit into a marketing channel in the style of Google Analytics (Paid Search, Paid Social, Organic Search, Referral and others), and stores that classification in the visitor's browser.
When the visitor submits a OnceHub booking form, the tool supplies the stored values to the form's hidden fields. OnceHub then saves them next to the booking's name, email and meeting time. From OnceHub you can forward the record to a CRM, a spreadsheet, an email tool or another destination through native integrations or a connector such as Zapier.
Setup sequence
- Create an account with the attribution tool and copy the snippet it provides.
- Install the snippet on your website; the vendor's help centre covers common site builders.
- Confirm that your OnceHub booking form contains hidden fields matching the tool's field names.
- Submit a test booking from a tagged URL and check that the values appear on the OnceHub record.
- Connect OnceHub to the destination where you will report on the data.
The order matters: if the snippet is missing, no values are stored; if the hidden fields are missing or misnamed, values are stored but never reach OnceHub. Test with a real tagged link rather than a direct visit, because a direct visit will usually resolve to a direct or referral channel and will not prove that campaign data flows through.
Worked example: an accounting firm's Google Ads booking
A prospective client clicks a Google Ads link, lands on the firm's site and books a consultation. Depending on the UTM parameters on the ad, the hidden fields could receive:
- Channel: Paid Search
- Channel Drilldown 1: Google
- Channel Drilldown 2: Brand Campaign
- Channel Drilldown 3: Apex Financial Group
The tool would also record the first landing page, such as a tax-consulting services page, and the broader landing-page category, such as services. The booking record therefore answers two separate questions: which channel and campaign produced the meeting, and which page content attracted the visitor.
What gets captured
Two elements are central.
Channel: the marketing route that brought the visitor, such as Organic Search, Paid Search or Referral. For paid search, the tool can also carry campaign name, ad group and keyword detail, which lets you compare performance below the channel level.
Landing page: the first page the visitor reached, plus a broader category for that page. This separates 'which channel' from 'which content', so you can see whether a particular service page or article is producing bookings.
Four reports and the decision each supports
Once the data sits in a CRM or spreadsheet, its built-in charting is enough to produce useful views.
Leads by Channel: monthly bookings split by originating channel. Use it to compare channel volume and decide where to add or reduce effort.
Opportunities by Google Ads campaign: month-by-month sales opportunities per campaign. Use it to move budget toward campaigns that create pipeline for the sales team.
Customers by Facebook Ads Network: new customers per network (for example Instagram, Messenger or WhatsApp) each month. Use it to decide placement and budget allocation across networks.
Revenue from Organic Search by search engine: revenue from customers who arrived through organic search, split by search engine. Use it to judge SEO return and where to concentrate optimisation.
A practical rule: pick the report that matches the decision you are about to make. Channel volume informs budget split; campaign opportunities inform paid search allocation; network customers inform social placement; organic revenue informs SEO investment.
Troubleshooting: no data versus undelivered data
If bookings show no attribution values, first check whether the attribution snippet is present on the pages that host the booking form. If it is present but values are still empty, test a tagged URL and inspect the browser storage.
If values appear in the browser but not on the OnceHub record, the likely cause is a missing or mismatched hidden field on the form. If values appear on the OnceHub record but not in your CRM, the issue is downstream: check the OnceHub integration or connector mapping.
Keeping these three stages separate — capture, form handoff, delivery — prevents you from changing the wrong part of the setup.
Frequently asked questions
Does this replace Google Analytics?
No. Google Analytics continues to measure traffic and sessions. The attribution layer adds booking-level source context so you can count meetings and customers by channel, which session-based reporting does not show on its own.
Where does the attribution data live before the booking?
It is stored in the visitor's browser after the tool classifies the visit. It is passed to the OnceHub form only when the visitor submits a booking.
Can I get campaign, ad group and keyword detail?
For paid search, the tool can carry campaign name, ad group and keyword in addition to the channel, provided the corresponding UTM parameters are present on the ad links.
What if my booking form has no hidden fields?
The values cannot reach OnceHub. Add hidden fields whose names match the tool's field names, then retest with a tagged link.