Showing Google Ads which enquiries a B2B services firm actually wants

This is a hypothetical example, not a client story. The fix for a B2B firm whose Google Ads account only knows about form fills is to capture the click details on every enquiry, then send qualified leads and closed deals from HubSpot back to Google Ads, so Smart Bidding can learn which enquiries turn into paying work.

The situation

Picture a UK firm selling a professional service to other businesses, with a sales process that runs for months. Google Ads records a conversion whenever the contact form is submitted. The form brings in serious buyers, but also suppliers with something to sell, job seekers and the occasional person looking for a different company entirely. Google Ads files them all under “success”.

HubSpot knows better. The sales team moves good enquiries through the pipeline and closes the rest as junk. None of that reaches Google Ads, so Smart Bidding goes on looking for more people like everyone who filled in the form.

Is HubSpot’s own connector enough for this?

Sometimes, and we’d say so. Google names HubSpot as a route for importing conversions, so a firm with a simple pipeline might only need that connection set up and checked. For this example we’ve assumed it falls short: “qualified” is a custom stage, deal values sit in a custom property, and one contact can have several deals open at once, so counting contacts would give the wrong answer.

What we’d build

• A Tracking Audit first. Before adding anything, we’d check that the existing form conversion counts once and that consent signals are reaching the tags.
• Click details stored on the contact. Where consent allows, GCLID, gbraid and wbraid are captured on landing and saved to the HubSpot contact with the form submission, along with the visitor’s consent choices.
• Enhanced conversions for leads. Hashed email and phone are collected at the form through GTM. Google describes its classic offline import as a legacy feature and recommends this route.
• Two new conversion actions. “Qualified lead” and “Closed deal”, each tied to a HubSpot deal stage and each counted once per deal.
• A sync on the Data Manager API. New integrations are blocked from the older Google Ads API route, so this one would start on Google’s replacement. Every upload is logged with its result, and failures raise an alert instead of disappearing.

How one enquiry travels

1. A prospect clicks an ad and completes the form. The click details and consent choices land on their HubSpot contact.
2. A salesperson speaks to them and moves the deal to “Qualified”.
3. The sync picks up the stage change and sends a “Qualified lead” conversion to Google Ads, with a value the firm has agreed in advance.
4. Some months later the deal closes, and a “Closed deal” conversion goes across with the real contract value.
5. A deal that can’t be matched, or an upload that’s rejected, appears in the log with the reason.

What happens to the campaigns?

Nothing, as far as we’re concerned. Budgets, keywords and ads stay with whoever runs the account, because managing those isn’t our job. Moving the primary goal from form fills to qualified leads is a real change to what Smart Bidding optimises towards, so the timing would be that person’s decision, made with the new data in front of them.

Where this sits in our services

This is our lead quality feedback service, using the HubSpot integration. A sync like this one is quoted as a fixed project from £2,500, depending on the systems involved, and it would begin with the audit. Tracking Monitoring suits it too, because a quiet mismatch between the website and HubSpot is exactly what those checks are for. Pricing has the full list.