Capture Google Ads data with every OnceHub booking
Clicks and calendar bookings are only useful together. This guide explains how to carry campaign, ad and landing-page context from a Google Ads visit through to a OnceHub booking, so each meeting can be judged by the work that produced it.
Why booking-level attribution matters
A booking tells you someone was interested, but not which campaign earned that interest. Analytics may show the click, yet the link to the meeting is lost when the visitor moves through your site. The fix is to tag the ad visit, preserve those tags, and attach them to the booking record.
Step 1: Tag every ad destination
Append UTM parameters to the destination URL for each Google ad. Use paid search for medium, Google for source, the campaign name for campaign, the ad group for term, and the specific ad for content. Keep naming consistent so reports group cleanly instead of creating near-duplicate values.
Step 2: Install and configure the attribution code
Install the small attribution snippet on your website and configure it for OnceHub. The exact placement depends on your site builder, whether WordPress, Webflow, Framer, Squarespace or another platform, so follow the builder-specific installation instructions for the code location.
Step 3: Pass the context with the booking
When a visitor arrives, the tool records where they came from. If they later complete a OnceHub form, it sends that context with the booking. In the logistics example, a warehouse operator who clicked a supply-chain analytics ad would arrive with paid search, Google, the campaign name and the ad name attached to the demo request.
Step 4: Use the captured data
Once inside OnceHub, the data can be inspected beside the meeting, forwarded to a CRM such as Salesforce, Pipedrive or HubSpot for dashboards, or sent to a spreadsheet for filtering and charting. Spreadsheet data can also feed reporting tools for broader views.
Capture every source, not only paid search
The same mechanism records bookings from Facebook ads, organic search, LinkedIn posts, referrals and other sources, not only Google Ads. That matters because channel comparisons are misleading if paid search is measured in detail while every other source is grouped as unknown.
Preserve attribution across browsing and return visits
Built-in UTM handling fails when the landing page and booking page differ: a visitor may land on the homepage, browse, then book from a demo page, leaving no campaign trail. Browser storage solves this by retaining UTM and attribution values across pages and return visits until the booking is submitted.
Add landing-page context
Attribution also records the first page the visitor opened and the group it belongs to. For example, a first visit to a warehouse-automation solution page would be stored as that full path and grouped under the solutions section. This shows whether blog posts, product pages or resources are producing bookings.
Pre-launch checklist
Checklist before you trust the reports: every ad uses the same UTM naming rules; the snippet loads on all relevant pages; a test booking from a tagged ad carries channel, campaign and ad fields; a booking after browsing other pages still carries the original values; and landing page plus page group appear beside the booking.
| UTM field | Recommended value | What it identifies |
|---|---|---|
| UTM Medium | Paid search | Traffic type |
| UTM Source | Platform | |
| UTM Campaign | Campaign name | Campaign |
| UTM Term | Ad group name | Ad group |
| UTM Content | Specific ad | Ad |
Recommended naming pattern from the guide; keep values consistent across campaigns.
| Field passed with booking | Example value | Use |
|---|---|---|
| Channel | Paid Search | Compare channels |
| Channel Drilldown 1 | Identify platform | |
| Channel Drilldown 2 | Supply Chain Analytics Campaign | Compare campaigns |
| Channel Drilldown 3 | Warehouse Efficiency Ad | Compare ads |
| Landing Page | logisync.com/solutions/warehouse-automation | Find entry page |
| Landing Page Group | /solutions | Compare site sections |
Illustrative example for a logistics software demo booking.
| Report | Question it answers | Decision it supports |
|---|---|---|
| Leads by Channel | How many bookings came from each channel each month? | Shift effort and budget toward channels producing bookings |
| Customers by Google Ads campaign | Which campaigns produce paying customers, not only clicks? | Invest in productive campaigns and reduce weak ones |
| Revenue by Keyword | Which search terms generate revenue? | Move budget toward revenue-producing keywords |
Reports require attribution data to be sent to a CRM, spreadsheet or reporting tool.
Frequently asked questions
What is needed to pass Google Ads data into a OnceHub booking?
Add consistent UTM values to each ad destination, install the attribution code on your site and configure it for OnceHub, then let it store the visit data in the browser and pass it with the completed booking.
Does OnceHub's built-in UTM tracking cover visitors who browse before booking?
No. Built-in UTM handling described here only works when the booking happens on the landing page. Storing attribution in the browser preserves it across other pages and later visits.
Which attribution fields arrive with a booking?
Channel, source and campaign drilldowns, plus the first landing page and its page group. Those fields let you connect a booking to the campaign, ad and site section that started the visit.
What can you do once attribution data is captured in OnceHub?
View it with the booking in OnceHub, send it to a CRM for dashboards, or send it to a spreadsheet for filtering, charts and connections to reporting tools.