One Pipedrive lead, from ad click to won deal in Google Ads

A Pipedrive to Google Ads offline conversion is a record telling Google that a specific ad click became a qualified or won deal, along with its value. We’re not aware of a native Pipedrive connector for this, so it’s normally done through a tool like Zapier or a small bespoke integration using Pipedrive’s API and webhooks.

The easiest way to explain it is to follow one made-up lead all the way through. Meet Priya, an operations manager who needs her company’s warehouse racking inspected, and who has no idea how much paperwork she’s about to cause.

Tuesday, 10:14am: the click

Priya searches “racking inspection Northampton” and clicks your ad. Google adds a click identifier to the landing page URL: a GCLID, or on some Apple traffic a gbraid or wbraid. A short script on your site stores it in a first-party cookie, provided her consent choices allow it.

That little string is the whole trick. Without it, or some other way to recognise her later, nothing that happens in Pipedrive can ever be tied back to that ad.

Tuesday, 10:21am: the form

She fills in your enquiry form. Alongside her name and number, hidden fields quietly submit the click identifier. Her email and phone can also be hashed and passed to Google through enhanced conversions for leads, which gives a second way to match her if the click ID goes missing. Google describes its classic click-based import as a legacy feature and points people towards that hashed route, so we’d usually set up both where consent allows.

The form pushes a new person and a new deal into Pipedrive. The click ID lands in a custom field on the deal, where your sales team can ignore it for the rest of time.

Thursday: qualified

Dan in sales calls Priya and moves the deal to “Site survey booked”. Pipedrive fires a webhook, our sync checks the deal, sees a click ID and queues a conversion called “Qualified enquiry” with an estimated value.

Pipelines twitch constantly, and very few of those movements predict money. We’d agree one or two stages that do, then leave the others out, which keeps Google’s picture of a good lead nice and sharp.

Five weeks later: won

The survey goes well and Dan marks the deal won at £4,200. Another webhook fires and a second conversion goes to Google Ads: “Deal won”, carrying the real value, the original click ID, the hashed contact details and the deal ID as a key. If somebody reopens the deal and wins it again because they clicked the wrong button, that key stops it counting twice.

A colleague then knocks the deal down to £3,800 after agreeing a discount. A decent integration handles that too, with a conversion adjustment instead of pretending nothing changed.

On the Google Ads side, those two events are separate conversion actions. “Deal won” is the primary one if you close enough deals to feed Smart Bidding, with “Qualified enquiry” kept as a secondary signal, or the other way round if wins are too rare to learn from. The original form fill gets demoted, so Google stops treating Priya’s enquiry as the finish line.

And the prospect who phoned instead?

Priya’s colleague Mark saw the same ad, skipped the form and rang the office. If your call tracking records the click, or Mark later gives an email address already held against an earlier website enquiry, his deal can still be linked. If nothing connects him to a click, the deal stays unattributed, however much you’d like the credit. Those deals simply aren’t sent, and Smart Bidding carries on learning from the ones that can be traced.

Could Zapier do this instead?

For a low-volume account with one pipeline, possibly yes. Google names Zapier as a route for importing conversions, and a Zap triggered when a deal reaches “won” is quick to set up. It starts to creak when you need value changes, reopened deals, multiple pipelines and a warning when something stops. Those are the jobs a bespoke sync is there for. It goes straight to Google’s Data Manager API, because new integrations are blocked from uploading through the old Google Ads API route, and our guide to offline conversion tracking for B2B goes through the options.

What you’d be buying

A Pipedrive sync starts from £2,500 ex VAT as a fixed quote, and the figure depends on how many pipelines and other systems are involved. We build it inside your own Pipedrive and Google Ads accounts, which means you’re free to carry on without us. The lead quality feedback page has the full service, or you can tell us about your pipeline.