HubSpot to Google Ads conversion tracking: sending lifecycle stages back as offline conversions

HubSpot’s native Google Ads integration can push CRM lifecycle stage changes back into Google Ads as conversion actions, so bidding optimizes toward pipeline instead of raw form fills. This guide walks through what the integration syncs, the tracking prerequisites, the exact setup sequence, and when you need to move to a custom workflow plus offline conversions architecture that mirrors the broader offline conversion pattern.

What HubSpot syncs to Google Ads and how clicks are attributed

With a connected Google Ads account, HubSpot can create ad conversion events that sync CRM lifecycle stage changes using Google’s Enhanced Conversions feature, and only lifecycle stage changes that occur after the event is created are counted, per HubSpot’s documentation. HubSpot can also use form submissions as documented triggers, but deal pipeline stages are not supported as triggers for these native events.

Each lifecycle stage event is independent, so a contact that moves through Lead and then Customer will fire both events, and HubSpot maps these lifecycle stages to corresponding ad network stages according to its documented behavior. This corrects the misconception that you can trigger conversions off deal stages, since HubSpot’s research states that only lifecycle stage changes and form submissions are supported triggers.

For attribution back to Google Ads clicks, HubSpot requires either a value in the Google ad click id contact property (the GCLID that HubSpot auto-sets when tracking is in place) or sufficient contact data such as email, phone, or address that can be shared with Google. HubSpot’s documentation states that Enhanced Conversions matching uses this GCLID or hashed customer data to associate the CRM event with the original ad interaction.

Prerequisites: tracking code, auto-tracking, forms, and tracking template

Before any syncing works, HubSpot’s tracking code must be installed on the ad landing pages so HubSpot can set and read its tracking cookie, as described in HubSpot’s ads attribution documentation. The connected Google Ads account must have auto-tracking enabled in HubSpot, which only affects future ad clicks and is not retroactive for clicks that occurred before enablement.

HubSpot requires that you use HubSpot forms, HubSpot pop-up forms, or forms submitted through the HubSpot Forms API that include the page URL and tracking-cookie parameters. This ensures HubSpot can tie the form submission to the contact and the ad click, which is required for either lifecycle stage or form-submission events to sync correctly.

On the Google Ads side, HubSpot uses an ad tracking template that must begin with {lpurl} and appends hsa_* parameters, and Google’s auto-tagging is compatible with this template according to HubSpot’s tracking documentation. Any redirect in the click path, including HTTP-to-HTTPS redirects or third-party click trackers, strips HubSpot’s tracking parameters, which breaks HubSpot’s ability to attribute the click and later sync lifecycle events for that contact.

This also corrects the misconception that connecting the integration backfills history, because HubSpot’s research states that neither lifecycle stage changes before event creation nor ad clicks before auto-tracking enablement will sync. Only events and clicks that occur after these prerequisites are in place can be used for conversion syncing.

Configuring a lifecycle-stage conversion event in HubSpot and Google Ads

To configure a lifecycle-stage conversion event in HubSpot, you must be using Marketing Hub Starter, Professional, or Enterprise, since ad conversion events are only available on those tiers. In HubSpot’s ads tools, you create a new ad conversion event, select Google Ads as the network, and choose the trigger as a lifecycle stage change or a specific form submission, with the documented limitation that each HubSpot form can trigger only one event.

When configuring the event, you select the lifecycle stage that should fire the conversion, such as Lead or Customer, and assign a fixed conversion value, since HubSpot’s documentation states that the option to use the deal amount has been removed. This corrects the misconception that the integration sends real deal values, because native lifecycle events now use a fixed value and syncing actual deal amounts requires a different path.

After you save the event in HubSpot, a corresponding conversion action is created in Google Ads. On the Google Ads side, HubSpot’s documentation states that these synced CRM lifecycle events appear as conversion actions, and you must ensure that Included in account-level goals is set to Yes for each event you want Google’s bidding to optimize toward.

If you want the lifecycle-stage event to count in the Conversions column and influence automated bidding, you set it as a primary action in Google Ads, following HubSpot’s guidance that primary actions are those counted in the Conversions column. This aligns with the Temper And Forge practice that conversion events are set as primary only once the data flowing through them is trusted, as described in the firm’s stated position.

How the Enhanced Conversions path works and what HubSpot sends

HubSpot uses Google’s Enhanced Conversions for leads when syncing lifecycle-stage events, and HubSpot’s documentation states that it hashes customer data with SHA-256 before sending it to Google. At least one customer property must be selected for hashing, with email recommended as the default identifier for matching.

When you first set up Enhanced Conversions for Google Ads in this integration, you must enable Enhanced Conversions in Google Ads and select Google Ads API as the user-provided-data method, per HubSpot’s documented setup steps. Once enabled, HubSpot sends the hashed customer data fields you selected, such as email, phone, or address, along with the conversion event so Google can match it to prior ad interactions.

HubSpot’s research states that a contact can sync if it has either a GCLID stored in the Google ad click id property or sufficient contact data to match via Enhanced Conversions. This means the integration can attribute conversions even when the GCLID is not present, as long as the hashed identifiers match Google’s records for a prior click or impression.

Tier limits and account requirements for the integration

HubSpot’s documentation states that ad conversion events require Marketing Hub Starter, Professional, or Enterprise, with limits of up to 5, 50, and 100 events respectively. These limits apply to the total number of ad conversion events you can create and sync from HubSpot to connected ad networks, including Google Ads.

On the account side, only individual Google Ads accounts can connect to HubSpot, not manager accounts, according to HubSpot’s connection documentation. The user connecting the account must have ads publish access in HubSpot and Admin access in Google Ads for the integration and conversion syncing to function.

HubSpot’s documentation also states that manager-account-managed Enhanced Conversions syncing is unsupported, which means that while you might be able to create an event under an MCC structure, the form data will not sync correctly. This corrects the misconception that an MCC connection works like a normal account, since HubSpot explicitly documents that MCC connections are not supported for this syncing.

Documented limitations: triggers, values, retroactivity, and reporting

HubSpot documents that only lifecycle stage changes and form submissions are valid triggers for ad conversion events, and deal pipeline stages cannot be used as triggers. This directly corrects the misconception that you can trigger conversions off deal stages, since deal stages are excluded from the native event trigger options.

HubSpot’s research states that lifecycle-based conversion events use a fixed value and that the Use the Deal amount option is no longer available. As a result, syncing real revenue values from deals requires a custom setup using HubSpot workflows and Google’s offline conversions path, rather than the native lifecycle-stage integration.

HubSpot also documents that only lifecycle stage changes occurring after the event is created are counted, and that auto-tracking is not retroactive for past ad clicks. This corrects the misconception that connecting the integration backfills history, because neither historical lifecycle changes nor historical ad clicks will be synced as conversions.

On the reporting side, HubSpot’s documentation states that synced events appear in the All conversions column in Google Ads only when they are attributable to a Google Ads campaign. HubSpot also states that totals will not match HubSpot’s internal numbers because the two platforms calculate conversions differently, which corrects the misconception that HubSpot and Google Ads numbers should match.

HubSpot’s attribution documentation further states that deal attribution works only with the default Customer lifecycle stage and that custom lifecycle stages are excluded from this behavior. Deleting an event in HubSpot does not delete the corresponding conversion action in Google Ads, so you must clean up unused conversion actions directly in Google Ads if needed.

Finally, HubSpot’s connection documentation states that manager accounts (MCCs) cannot connect to HubSpot and that MCC-managed Enhanced Conversions syncing is unsupported, which reinforces the limitation that only individual Google Ads accounts can be used for this integration.

When to move to workflows and offline conversions instead of the native sync

HubSpot’s research states that native lifecycle events use fixed values and that the option to use the deal amount has been removed, so any scenario that requires syncing real deal amounts to Google Ads must use a custom workflow plus offline conversions path. This corrects the misconception that the integration sends real deal values, since real revenue syncing is explicitly documented as requiring a different architecture.

Google’s help pages describe HubSpot as a supported Data Manager source for Customer Match and offline conversion import, and they state that HubSpot Data Manager conditions must use the Lifecycle Stage field unless combined with other conditions. Google also labels plain offline conversion import as a legacy feature and recommends Enhanced Conversions for leads via Data Manager, which is the pattern you follow when you outgrow the fixed-value lifecycle events.

In practice, you move to the workflow plus offline conversions path when you need deal-stage triggers, real deal amounts, or more granular conditions than a single lifecycle stage or form can provide. This aligns with Temper And Forge’s stated practice that when real deal amounts drive the keep-or-kill decision on campaigns, the custom workflow and offline conversions path is worth the build so that ROAS is measured in the CRM, and the feedback loop is in place before spend scales.

Temper And Forge’s stated practice is that this integration is the practical implementation of the rule that a lead business’s ROAS lives in the CRM, using lifecycle-stage syncing to turn form-fill counts into pipeline by vertical, and that when real deal amounts must drive keep-or-kill decisions, a custom workflow plus offline conversions path is built before scaling spend, with conversion events set as primary only once their data is trusted.