Skip to content

Capture the GCLID in OnceHub and Connect Bookings to Google Ads

OnceHub bookings are a strong signal of intent, but a booking record without the Google Ads click identifier leaves you guessing which campaign produced it. This guide shows how to place a hidden GCLID field on a OnceHub booking form, how a browser-stored click identifier survives navigation, and how to route that value into a CRM or back to Google Ads as an offline conversion. It also covers the trigger-stage decision that determines whether smart bidding receives enough data to optimize.

Three setup steps for OnceHub

The setup has three moving parts: a script on your site, a hidden field on the booking form, and a destination for the captured value.

  1. Install your attribution script on your website and add a hidden field to the OnceHub booking widget embedded on your site. The exact placement depends on your site builder (WordPress, Webflow, Squarespace and similar platforms typically expose a settings area for scripts). Name the hidden field "GCLID" so the script has a known target.
  1. When a visitor arrives from a Google Ad, the script reads the GCLID from the URL and keeps it in the browser. That storage step matters: the visitor may browse several pages, or leave and return on another day, before completing a booking. Because the value is held in the browser rather than only in the landing-page URL, it is still available when the booking form is submitted.
  1. On submission, the script writes the stored GCLID into the hidden field. OnceHub then records it alongside the booking details such as name, email and phone number. The value appears in the bookings area of the OnceHub account and in any booking notification emails you have configured. From there, OnceHub's built-in integrations or a connector such as Zapier or Make can forward the record to a CRM or another tool.

A useful field map for this flow:

  • Input: the GCLID parameter on the ad landing URL.
  • Stored value: the GCLID held in the visitor's browser by the script.
  • Form field: the hidden OnceHub field named "GCLID".
  • Booking record: the GCLID stored with the booking and shown in notifications.
  • Output: the GCLID mapped into a CRM record or a Google Ads offline conversion.

A common failure distinction: if the GCLID is missing from a booking, first check whether the visitor actually arrived through a Google Ad. A visitor from organic search, referral or direct traffic has no GCLID to capture. If paid-ad visitors are also missing the value, check that the hidden field exists on the embedded widget and is named exactly "GCLID", and that the script is present on the pages where the widget loads.

Sending the GCLID back to Google Ads as an offline conversion

Before any GCLID can flow back, Google Ads needs a conversion action ready to receive it. In the Google Ads account, open Goals in the left sidebar, select Conversions, add a new conversion and choose Offline Conversion as the type. On the final screen, when asked for a data source, choose the option to add a data source later.

Next, decide which sales-process stage should trigger the send. This is the decision most worth pausing on. Many teams default to firing the conversion only when a deal closes, which feels logical but often backfires on volume: Google's smart bidding strategies (Maximise Conversions, Maximise Conversion Value, Target CPA) generally need at least 50 conversions per month to work effectively. If your closed-deal count sits below that threshold, the bidding model simply does not receive enough events to learn from. Triggering earlier, at a stage such as a new deal being created in the CRM, still sends a meaningful signal because the lead has been qualified by sales, and it gives smart bidding enough monthly events to optimize properly.

Once the trigger is chosen, build the automation. In Zapier, create a new Zap and set the trigger to the chosen moment (for example, a new deal in the CRM). Select Google Ads as the action app and "Send Offline Conversion" as the event. Then map the GCLID from the CRM, or wherever it is stored, to the matching field in Zapier. Test the flow before increasing ad spend.

Why browser storage changes the result

Many simple GCLID capture methods only work when the booking happens on the same page the visitor first landed on. That works in theory but fails in practice: a visitor who clicks an ad, lands on the homepage and then navigates to a contact page to book has already lost the GCLID from the URL. Storing the value in the browser at arrival removes that dependency, so the booking page and the time gap no longer determine whether the identifier is captured.

The same script can also record non-paid attribution. For a visitor arriving through a regular Google search rather than an ad, the captured fields can look like this:

  • Channel = Organic Search
  • Channel Drilldown 1 = Google
  • Channel Drilldown 2 = www.google.com (or whichever search engine domain they came from)
  • Channel Drilldown 3 = the search keyword, when available

That gives paid and organic bookings a comparable attribution record in the CRM.

What the captured record enables

{{OWNER_CUSTOMER_STORY_PERMISSION_AND_ATTRIBUTION}}

{{OWNER_CUSTOMER_STORY_QUOTE_AND_NAME}}

{{OWNER_CUSTOMER_STORY_RESULTS_VERIFICATION}}

A legal practice serving federal employees described a visibility gap familiar to many advertisers: campaigns were sending traffic, and analytics showed the visits, but the business could not see which visitors booked a consultation or became paying clients. After the attribution setup, each new booking carried campaign, ad group, ad, keyword and GCLID details into the CRM alongside the contact record. That connected ad spend to client outcomes rather than only clicks and page views. The review found that some display campaigns produced strong traffic numbers but few paying clients, while search campaigns consistently brought in new business; budget was moved toward the search campaigns. The reported result was more clients at a lower cost to acquire each one.

Pre-launch checklist

  • The attribution script loads on every page where a OnceHub widget is embedded.
  • The OnceHub booking widget has a hidden field named exactly "GCLID".
  • A test paid-ad click produces a booking record containing a GCLID.
  • A test organic visit produces the expected channel and drilldown values.
  • The CRM mapping stores the GCLID on the contact or deal record.
  • The Google Ads offline conversion action exists and is set to receive data later.
  • The automation trigger matches the chosen pipeline stage.
  • The Zapier field mapping points the CRM GCLID to the Google Ads offline conversion field.
  • A test conversion is sent and confirmed before ad spend is increased.

Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.

{{OWNER_SETUP_TIME_CLAIM}}

Frequently asked questions

Why is the GCLID missing from some OnceHub bookings?

The most common reason is that the visitor did not arrive through a Google Ad, so there was no GCLID to capture. Organic search, referral and direct visitors have no GCLID. If paid-ad visitors are also missing it, confirm the hidden field exists on the embedded widget, is named exactly "GCLID", and that the script is loaded on the pages where the widget appears.

Do I have to send the conversion when a deal closes?

No. Google's smart bidding strategies generally need at least 50 conversions per month to function effectively. If closed deals fall below that, triggering the offline conversion at an earlier qualified stage, such as a new deal created in the CRM, usually gives smart bidding more usable data.

Can the same setup capture non-paid attribution?

Yes. The script can also record channel and drilldown values for organic search, organic social, referral and direct traffic, so paid and non-paid bookings share a comparable attribution record.

Where does the GCLID appear after a booking?

It is stored with the booking in the OnceHub bookings area and appears in any booking notification emails you have configured. From there it can be forwarded to a CRM or another tool through OnceHub integrations or a connector such as Zapier or Make.