Skip to content
Ledion
Join the beta
Menu

HubSpot removed deal amounts from Google Ads conversions. Here's how to send real values again.

By Santi ·

If you send HubSpot lifecycle stages to Google Ads as conversions, check your settings. On October 12, 2026, HubSpot updated its help page for Google Ads conversion events. The relevant line:

“Native Google Ads lifecycle stage conversion events use a fixed value. The Use the Deal amount option is no longer available.”

HubSpot now suggests entering “a representative amount, such as your average deal size”. So a $4,000 deal and a $90,000 deal look the same to Google.

Why it matters

Value-based bidding (Maximize conversion value, target ROAS) works by learning which clicks lead to more revenue. Give it the same number for every conversion and it can only learn which clicks lead to a conversion. For B2B accounts with a wide spread of deal sizes, that is most of the signal gone.

It also affects anyone who reports ROAS from Google Ads conversion values. Those numbers are now your average deal size times your conversion count.

What HubSpot’s built-in sync still does

As of October 2026:

  • Conversion events fire on a lifecycle stage change or a form submission. Deal stages, custom events and property changes can’t be triggers.
  • Google: a fixed value per event.
  • LinkedIn: the weighted deal amount (scaled by the stage’s win probability).
  • Meta and Microsoft: a fixed value.
  • Reddit: not supported.

For many teams that’s fine. If you care about sending revenue, here are the options.

Option 1: Use a fixed value per stage

Create separate lifecycle-stage events with different fixed values, for example MQL at $500, SQL at $2,000, Customer at your average deal size. It’s crude, but it’s free and takes ten minutes. It works best when deal sizes are fairly uniform.

Option 2: Build it yourself

HubSpot’s help page points developers at a custom setup: “a developer can build a custom setup using HubSpot workflows and Google’s Offline Conversions API.”

One catch: since June 15, 2026, Google’s Ads API no longer accepts offline conversion uploads from new integrations. New builds need Google’s Data Manager API. Existing integrations that were already uploading can continue for now.

A minimal version looks like this:

  1. Capture the click ID. Make sure the Google click ID (GCLID) lands on the contact. HubSpot fills its “Google ad click id” property when your Google Ads account is connected and auto-tracking is on. Check a few recent contacts that came from paid search.
  2. Create a conversion action in Google Ads for imported conversions (for example “Closed won (import)”), and decide whether it should be primary for bidding.
  3. Send the event. A workflow (deal stage = Closed won) calls a webhook or custom code action. That code:
    • reads the deal amount and the associated contact’s GCLID and email
    • hashes the email as Google specifies
    • calls the Data Manager API with the conversion action, the time, the value and the currency
  4. Handle failures. Google rejects clicks from other accounts, conversions dated before the click, and clicks older than the conversion window. Log what fails, or you’ll never know.
  5. Do it again for every other network you buy from, each with its own API, identifiers, hashing rules and time limits. Meta and Reddit, for example, only accept events up to 7 days old.

If you have a developer and one network, this is a reasonable weekend project. The maintenance is the part people underestimate: tokens expire, APIs change, and click IDs quietly stop being captured.

Option 3: Use a tool

Several tools sync HubSpot conversions to ad platforms. They differ on which triggers and networks they support, whether they send real values, and whether they run inside HubSpot workflows or as a separate sync.

I built Ledion for the version of this I wanted: a Send conversion step you add to any HubSpot contact or deal workflow.

  • One step, four networks. It sends the record’s real amount to Google Ads, Meta, Microsoft Ads and Reddit at once, with LinkedIn next.
  • A result back in the workflow. Each network’s result comes back to the workflow, so you can branch on failures.
  • Click-ID coverage. A health page shows how many of your paid leads actually have a click ID. Without one, none of this works.

It’s in beta. Join here.

Checklist, whichever option you pick

  • Use a separate conversion action for imported conversions, so nothing is double counted.
  • Decide which action is primary for bidding.
  • Check that paid-search contacts actually carry a GCLID.
  • Send the stage that happens within your networks’ time limits (SQL, not just Closed won, if your cycle is long).
  • Watch the upload diagnostics in Google Ads for the first two weeks.

Sources (checked 2026-10-20; re-check before publishing)

Join the beta.

The first 10 companies use Ledion free until it's listed on the HubSpot App Marketplace, then pay $79 a month for Pro, for as long as they stay.

Join the beta