HubSpot + Google Ads integration 2026: offline conversion import setup

For B2B marketers in 2026, the gap between what Google Ads can see and what actually matters to the business is the central measurement problem. Google Ads, by default, sees the website conversion — the form fill, the demo request, the contact submission. But in a B2B funnel, that form fill is the beginning of the story, not the end. The conversions that matter to revenue happen inside HubSpot, over days or weeks: a lead gets qualified, becomes an opportunity, and eventually closes won or lost. If Google Ads never learns which form fills became revenue, it optimizes toward the cheapest form fills — which are frequently the worst ones.

This tutorial walks through connecting HubSpot CRM to Google Ads for offline conversion tracking, end to end and technically. We cover why offline import matters for HubSpot users specifically, the three connection methods (native integration, the Google Ads API, and Zapier/middleware) and when to use each, how to capture the GCLID in HubSpot forms (the foundation everything else depends on), how to map deal stages to conversion actions, how to configure offline conversion import correctly, how to layer Enhanced Conversions for Leads, how to reconcile attribution between the two systems, and how to troubleshoot the failure points that quietly break these setups. The audience is the marketing or revenue-ops practitioner who owns both platforms and wants Google Ads optimizing for pipeline, not vanity lead counts.

Why offline conversion import matters for HubSpot users

The case for offline conversion import comes down to a mismatch between where Google Ads measures and where value is created.

The default state without offline import:

• Google Ads sees the website conversion — typically a form submission counted as a lead.
• Smart Bidding optimizes toward maximizing those form submissions at your target cost.
• It has no idea which submissions became qualified leads, opportunities, or revenue.
• Result: the algorithm chases the cheapest leads, which skews toward low-intent, low-quality, and sometimes spam — because those are easiest to generate at a low cost per lead.

What changes with offline import:

• HubSpot sends back the conversions that represent real value — qualified leads, opportunities, closed-won deals — attributed to the original ad click.
• Smart Bidding can now optimize toward those downstream outcomes instead of raw form volume.
• With deal value attached to closed-won, Google can optimize for revenue via value-based bidding.
• Result: the algorithm learns which campaigns, keywords, and audiences produce leads that actually convert, and shifts budget toward them.

The business impact is the difference between a cost-per-lead mindset and a cost-per-revenue mindset. Two campaigns might produce leads at the same cost per lead, but one produces leads that close at three times the rate of the other. Without offline import, Google treats them as equivalent and may even favor the worse one if its leads are marginally cheaper. With offline import, Google sees the quality difference and reallocates accordingly. For any B2B team where lead quality varies meaningfully across sources — which is essentially all of them — this is the highest-leverage measurement improvement available.

This is the same principle behind importing any CRM outcome into Google Ads, covered in our offline conversions from CRM guide. The HubSpot-specific value is that HubSpot's native integration and well-structured data model make the implementation more accessible than a from-scratch API build, while still supporting advanced configurations when you need them.

Three connection methods: native, API, and Zapier

There are three ways to connect HubSpot to Google Ads for offline conversions, and choosing the right one prevents a lot of wasted effort.

Native HubSpot integration — the default. HubSpot offers a built-in Google Ads integration that connects the accounts and supports syncing CRM lifecycle and deal stages back to Google Ads as offline conversions. For the large majority of B2B teams this is the right choice: it is purpose-built, requires no custom code, and is maintained by HubSpot so it keeps working as both platforms evolve. Start here unless you have a specific reason not to.

Google Ads API — for advanced control. When the native integration cannot do what you need — custom conversion logic, very high pipeline volume, precise control over conversion adjustments and restatements, or bespoke Enhanced Conversions for Leads handling — the Google Ads API offline conversion upload gives you full control. The cost is developer time to build and maintain it. Reserve this for enterprise scenarios or genuinely custom requirements; it is overkill for standard lead-quality optimization.

Zapier or middleware — the fallback. Tools like Zapier (covered in our Zapier and Make automation guide) can bridge HubSpot and Google Ads when the native integration is unavailable for your configuration or you need a quick stopgap. They are flexible and require no developer, but they add a dependency, can be brittle, and offer less control over attribution detail. Use them as a fallback, not a first choice.

The decision rule: native first; API when you have advanced needs the native integration cannot meet; Zapier as a lightweight bridge when neither fits. Most teams should never need to leave the native integration — and adopting the API or middleware prematurely just adds maintenance burden for control they will not use.

Capturing GCLID in HubSpot forms

GCLID capture is the foundation, and it deserves careful, tested implementation because everything downstream depends on it.

What the GCLID is: the Google Click Identifier, a unique parameter Google appends to your landing-page URL when someone clicks an ad and auto-tagging is enabled (for example, ?gclid=ABC123). It uniquely identifies that click, which is what lets you tie a later offline conversion back to the specific ad interaction that started it.

The two prerequisites:

• Auto-tagging must be on in Google Ads (Settings, Account settings, auto-tagging). Without it, no GCLID is generated and there is nothing to capture. This is the most common silent prerequisite failure.
• You need somewhere to store it — a contact property and a deal property in HubSpot so the value persists from form submission through to the deal record.

The capture mechanism:

1. Add a hidden GCLID field to your HubSpot forms, bound to the GCLID contact property.
2. Read the GCLID from the URL when the form loads, using tracking code or a small script. A robust implementation also stores the GCLID in a first-party cookie on landing, so it survives the user navigating across pages before submitting — the GCLID is only in the URL on the first ad-click landing page.
3. Populate the hidden field with the captured GCLID (from URL or cookie) so it submits with the form.
4. Persist to the deal — ensure the GCLID copies from contact to deal when a deal is created, so it is available at the stage where you count conversions.

Why the cookie matters: the GCLID appears in the URL only on the ad-click landing page. If a visitor lands, browses several pages, and submits a form on a different page, the URL no longer contains the GCLID. Storing it in a first-party cookie on landing and reading from that cookie at submission captures these multi-page journeys, which are the majority. Skipping the cookie step is a common reason GCLID capture works in testing (single-page) but misses real users (multi-page).

Test it explicitly: click one of your own live ads, navigate a couple of pages, submit a form, and confirm the GCLID lands on the contact record — then create a deal and confirm it carries over. Do not assume capture works; verify it with a real ad click, because this is the step that most often fails quietly and breaks the entire pipeline.

Mapping deal stages to conversion actions

With GCLID flowing, the next decision is which deal stages to send to Google Ads as conversions, and what value to assign them. This mapping is what determines what Smart Bidding optimizes toward.

The principle: map value, not just volume. The mistake that defeats the entire purpose is mapping only the top-of-funnel form fill. That just recreates the default state — Google optimizing for lead count. The point of offline import is to send the deeper, value-bearing stages so Google can optimize for quality and outcome.

A typical mapping:

How to choose:

• Send the two or three stages that best represent quality and outcome. You do not need every stage; too many fragments the signal. A common strong setup is sales-qualified/opportunity plus closed-won.
• Use increasing values down the funnel so Google understands that a closed deal is worth far more than an early lead. Increasing values let the algorithm weight its optimization toward the outcomes that matter.
• Use actual deal value for closed-won wherever possible. Real revenue values unlock value-based bidding (Maximize Conversion Value with a target ROAS), which optimizes for revenue rather than conversion count — the most powerful configuration for a revenue-driven B2B program.

Primary vs secondary conversions: designate which conversion actions are primary (included in the Conversions column and used by Smart Bidding) and which are secondary (observation only). A common pattern is to bid on the qualified-lead or opportunity stage for volume of good leads, while reporting closed-won as the ultimate truth — or, with enough closed-won volume, bidding directly on revenue. The right primary action depends on your conversion volume: deeper stages are higher quality but lower volume, and Smart Bidding needs sufficient conversions to optimize, so very low-volume accounts may need to bid on an earlier qualified stage.

The mapping is where strategy meets configuration. It is worth deciding deliberately with sales and revenue-ops, because it directly shapes which leads Google works to bring you.

Keep the mapping in sync with your pipeline. HubSpot deal stages change over time as sales processes evolve — stages get added, renamed, or merged. When they do, the conversion mapping can silently break or misalign, sending the wrong stage or no stage at all. Build a quick check into your quarterly revenue-ops review: confirm the mapped stages still exist, still mean what they did, and still flow to the right Google Ads conversion actions. A mapping that was correct at launch can drift out of alignment within a couple of quarters of normal pipeline evolution.

Setting up offline conversion import

With stages chosen, configure the offline conversion actions in Google Ads correctly. The integration creates conversion actions, but you should verify their settings rather than trusting defaults.

The settings that matter:

• Conversion category — set each action to the right category (Lead, Qualified lead, Sale). The category influences how Smart Bidding interprets the conversion and how reporting groups it.
• Conversion window — critical for B2B. Set it long enough to capture your full sales cycle, often 60-90 days, sometimes longer. The window is the maximum time between click and conversion for attribution to occur; if a deal closes after the window expires, it will not attribute and will appear missing. Match the window to your actual click-to-close timeline with margin.
• Counting — generally count one conversion per click for lead-type actions (one person, one qualified lead) rather than every. For sale-type actions, choose based on whether repeat purchases should each count.
• Include in Conversions — set to Yes for the actions you want Smart Bidding to optimize toward (your primary actions), and use secondary status for observation-only actions.
• Value — confirm values flow correctly, especially actual deal value for closed-won.

The import mechanism: with the native integration, HubSpot sends the offline conversion to Google Ads when a deal reaches a mapped stage, matched to the original click via the stored GCLID (or via Enhanced Conversions for Leads using hashed data). The conversion then appears in Google Ads attributed to the campaign, ad group, and keyword that drove the original click — closing the loop.

Sequencing within the funnel: because a single deal can pass through several mapped stages, ensure your configuration handles the progression sensibly — typically each stage is its own conversion action firing once as the deal reaches it, so one deal can generate a lead conversion, then a qualified-lead conversion, then a sale conversion over its lifetime. This staged view is exactly what lets you see, per campaign, how leads progress from volume to qualified to revenue.

Validate the settings before relying on them. A too-short conversion window is the most common configuration error — it silently drops every deal that closes after it expires, making a working setup look broken. Confirm the window comfortably exceeds your sales cycle, then move to validation with a test deal.

Enhanced Conversions for Leads via HubSpot

Enhanced Conversions for Leads is an enhancement that improves how reliably offline conversions match back to ad clicks, using hashed first-party data rather than relying solely on the GCLID.

What it does: instead of (or in addition to) matching on the GCLID, Enhanced Conversions for Leads matches an offline conversion to a click using hashed first-party identifiers — most commonly the email address — captured when the lead is created and sent securely (hashed) to Google. This recovers conversions where the GCLID was lost or unavailable, and can improve overall match rates.

Why it helps:

• GCLID capture is imperfect in practice — some forms miss it, some journeys lose it, some clicks predate your setup. Email-based matching provides a second path to attribution.
• It is more durable as a first-party-data approach in a privacy-constrained environment, aligning with the broader shift toward first-party measurement (see our Enhanced Conversions guide and first-party data strategy guide).

How it works with HubSpot:

• Ensure the lead's hashed identifiers (such as email) are captured at submission and available to pass with the offline conversion.
• Depending on your configuration, this flows either through the native integration's offline sync or through the Google Ads API with Enhanced Conversions for Leads enabled.
• Accept the required customer-data terms in Google Ads, which are a prerequisite for using first-party data this way.

The practical path: treat Enhanced Conversions for Leads as a layer on top of working offline import, not a prerequisite. Get the native integration flowing offline conversions via GCLID first and confirm they appear. Then, if your setup and data permit, enable Enhanced Conversions for Leads to lift match rates. Validate carefully — misconfigured hashing, missing or inconsistent identifiers, or unaccepted data terms produce unmatched conversions that look like a failure. When it is working, you get the best of both worlds: GCLID-based attribution for clicks that carried it, and email-based matching as a robust backstop for the rest.

Attribution reconciliation and validation

A connected pipeline is not a trusted pipeline until you have validated it end to end and established ongoing reconciliation. Offline import fails silently, so verification is not optional.

End-to-end validation with a test deal:

1. Click your own live ad so a real GCLID is generated, and navigate a couple of pages.
2. Submit a form and confirm the GCLID is captured on the contact record.
3. Create a deal from the contact and confirm the GCLID carries to the deal.
4. Advance the deal through your mapped stages.
5. Confirm each mapped conversion appears in Google Ads, attributed to the originating campaign/ad group/keyword, with the right value.
6. Check the conversions report shows recent activity for the offline actions.

If any step fails, fix it before trusting the data — and before letting Smart Bidding optimize on it. A broken pipeline does not just lose data; it actively misleads bidding.

Ongoing reconciliation: the two systems will never match perfectly — attribution windows, modeling, timing, and consent-driven gaps all create legitimate differences. The goal is not identical numbers but explainable differences:

• Monthly, compare Google Ads offline conversions against the corresponding HubSpot deals for the period.
• Investigate large gaps — a sudden drop in offline conversions usually means GCLID capture or the connection broke, not that lead quality changed.
• Expect Google Ads to show somewhat fewer offline conversions than HubSpot has deals, because not every deal had a captured GCLID or a click within the window. A reasonable, stable ratio is healthy; a collapsing ratio signals a problem.

Set drop alerts. Because failures are silent, configure an alert (or a recurring manual check) for offline conversion volume falling unexpectedly. The classic failure is a website change that breaks the hidden GCLID field — conversions quietly stop, bidding slowly degrades, and nobody notices for weeks. An alert turns a silent multi-week failure into a same-week fix.

For the broader attribution context of reconciling platform numbers with reality, our data-driven vs last-click attribution guide and GA4 setup guide are useful companions.

Troubleshooting the common failure points

Most HubSpot to Google Ads offline tracking problems trace to a short list of causes. Work through them in order of likelihood.

The troubleshooting sequence:

1. Confirm GCLID is present on records. This is the foundation and the most frequent failure. If records have no GCLID, nothing else matters until that is fixed. Check both the capture (forms) and the prerequisite (auto-tagging on).
2. Verify auto-tagging. If GCLIDs are universally empty, auto-tagging is almost certainly off in Google Ads.
3. Check the conversion window. If conversions appear for fast deals but not slow ones, the window is too short for your sales cycle.
4. Test multi-page journeys. If single-page tests work but real users do not convert, you are losing the GCLID when visitors browse before submitting — implement the first-party cookie capture.
5. Check the connection and form integrity. A sudden stop usually means the integration connection lapsed or a website change broke the hidden GCLID field. Reconnect and restore.
6. Validate Enhanced Conversions data. Unmatched enhanced conversions point to missing or inconsistent hashed identifiers or unaccepted data terms.

The meta-lesson: because offline import fails silently and the failures cluster around a few causes, the best defense is a tested setup plus ongoing monitoring. Validate end-to-end at launch, reconcile monthly, and alert on volume drops. The cost of a silent failure is not just lost data — it is weeks of Smart Bidding optimizing on a broken signal, quietly steering budget toward the wrong leads. A small amount of monitoring discipline prevents the most expensive failure mode in the entire setup.

If you would like AI-driven optimization layered on top of a healthy HubSpot-to-Google-Ads conversion pipeline — so the system watches for the silent failures and surfaces the optimizations while your team focuses on the funnel — SteerAds runs a free 14-day audit on your Google and Microsoft Ads accounts.

Sources

Official and third-party sources consulted for this guide:

• knowledge.hubspot.com — HubSpot Google Ads integration documentation
• support.google.com/google-ads — Google Ads offline conversion import documentation
• developers.google.com — Google Ads API offline conversion upload
• academy.hubspot.com — HubSpot Academy CRM and ads tracking lessons
• searchenginejournal.com — Search Engine Journal offline conversion and Enhanced Conversions coverage

FAQ