The bridge between Google Ads and HubSpot depends on a handful of specific technical identifiers. When Auto-tagging is enabled in Google Ads, the platform automatically appends a Google Click Identifier, or GCLID, to every landing page URL a user clicks. HubSpot's tracking code reads the GCLID and, together with the hubspotutk cookie, a first-party cookie that persists a visitor's identity across sessions, associates the ad click with subsequent form submissions or contact creations. The Tracking Template in Google Ads defines additional URL parameters, typically UTMs including utm_source, utm_medium, and utm_campaign, which let HubSpot categorize traffic as Paid Search and surface more granular source data in reports. If Auto-tagging is disabled or the HubSpot tracking code is missing, this attribution chain breaks and ad clicks will not be tied to contacts.
Attribution itself is governed by two key concepts: Lookback Windows and Attribution Models. A Lookback Window is the period after an ad interaction during which a conversion is still credited to that click, with thirty days being a common default for click-through conversions though adjustable per conversion action. The Attribution Model determines how credit is distributed across multiple touchpoints; the traditional Last Click model assigns all credit to the final interaction, while Data-Driven Attribution uses historical account data to calculate each interaction's true contribution to conversions. In HubSpot, the Original Source property for a Google Ads lead is typically set to Paid Search, and the Original Source Drill-Down 1 property provides further detail, often naming the specific campaign or ad network. HubSpot can even perform retrospective matching: if a visitor carries a hubspotutk cookie from a past ad click and later identifies themselves through a form, the original click is attributed to the new contact. A persistent user_id parameter can also link the same person across multiple devices when they are signed in, supporting cross-device attribution.
Because tracking relies on cookies, several common issues can interrupt attribution. Users who decline cookie consent, deploy ad blockers, or clear cookies between click and conversion will not be tied back to their ad interaction. These gaps are a major reason advertisers look beyond cookies toward server-side and hashed-data approaches. Additionally, offline conversions uploaded more than 90 days after the original GCLID click will not be recorded, making timely data syncs essential for accurate measurement. Understanding these mechanics clarifies why numbers often differ between HubSpot and Google Ads and where the integration can lose fidelity.