Pipedrive Google Ads Integration: gclid and Offline Conversions

Pipedrive is a good place to keep the result of a Google click, even if it does not fetch one. Four things are already there, and each one does its job well.

• Source fields on every deal and leadSource origin records how the record was created (web form, API, import, chatbot and so on) and cannot be edited. Source channel is a list your admin defines, so "Paid search" can be one of its options.
• Custom fields for anything elseA text field called GCLID on the deal is all the storage the loop needs. Pipedrive does not create one for you, but adding it takes a minute in Company Settings.
• Automations that can call outOn plans that include Automations, an automation can send a webhook when a deal moves stage or is won. That is the trigger an upload script or a Zapier zap listens for.
• Web Visitors, at company levelThe Web Visitors add-on can filter visiting companies by Google AdWords campaign. It shows which organisations came from a campaign, not which person converted, so it is not a conversion sync.

All three are legitimate. They differ in how much of the loop they cover and how much of it you maintain yourself.

• GA Connector: the gclid into Pipedrive

  Google Analytics Connector, listed as free on the marketplace, runs its own script on your site and writes UTMs, first and last click, the GA4 client and session IDs and the GCLID into Pipedrive fields. It solves the capture half. The upload is still yours.

• LeadsBridge: conversions back out

  LeadsBridge is on the marketplace with lead sync, audience sync and offline conversions for Google, Facebook, LinkedIn and TikTok. It solves the upload half, provided a gclid is already on the record it reads.

• Zapier: a template you own

  Zapier's template sends an offline conversion to Google Ads for a new deal in Pipedrive. Change the trigger to a won deal and map the value, or it reports deal creation, which is a lead event in disguise.

• An attribution tool: both halves

  A tracking platform records the click and every visit after it, writes the result into Pipedrive and uploads the won deal itself. One setup instead of two, and usually more than one ad platform.

A common and perfectly sound combination is GA Connector for capture plus a Zapier zap or LeadsBridge for the upload. Just know that you now own two tools, a field mapping between them and a trigger, and that a gap in any of the three looks exactly like a quiet month on Google.

Every option above is an implementation of the same four steps. If you understand them, you can debug any of the tools.

1. The click carries a gclid. With auto-tagging on, Google appends a gclid to the landing page URL. Google requires auto-tagging for offline conversion import, so check it first.
2. Something on your site reads it and keeps it. The gclid is only in the URL of the page the visitor landed on. A script has to store it (in a first-party cookie or on your server) so it is still there when the visitor fills in a form three pages, or three days, later.
3. The form hands it to Pipedrive. The stored value goes into a hidden field, and from there into a GCLID custom field on the person or the deal. If it lands only on the person, copy it onto the deal, because the deal is where the money is.
4. The won deal goes back to Google. When the deal is marked won, its gclid, the time it was won and its amount are uploaded to a conversion action you created for this. Leave the value blank and Google applies the conversion action's default value, which throws away the most useful thing you know.

1. The gclid is only on the converting visit's landing URL. A visitor who clicked an ad on Monday and comes back by typing your address on Thursday arrives with no gclid. Unless Monday's value was stored, Thursday's form is a lead with nothing to upload.
2. Google keeps a gclid for 90 days. Its help centre says so plainly, and an older click is refused with "This click is too old for its conversion to be imported". A deal that takes four months to close cannot be uploaded against the click that started it. Upload a qualified stage that happens inside 90 days as well.
3. Auto-tagging gets switched off. Somebody prefers clean URLs or a manual tagging template overrides it. No gclid on the landing page, nothing to capture, and no error anywhere.
4. The conversion action is brand new. Google asks you to wait 4 to 6 hours after creating a conversion action before uploading to it. A test run in the first hour fails for that reason, not because your setup is wrong.
5. The trigger fires on the wrong event. A Zapier template left on "new deal" uploads every lead as a conversion. Re-opened and re-won deals can upload twice unless the upload is deduplicated.
6. Uploads are rare. Google recommends uploading at least daily for Smart Bidding. A monthly CSV is better than nothing, but bidding learns from it a month late.

And one that no tool can fix: a lead who phoned you, or was typed in by a seller, never had a gclid at all. Whatever share of your pipeline arrives that way is invisible to Google whichever path you choose.

1. Auto-tagging is on in Google Ads, at account level.
2. A GCLID custom field exists on the deal, and the person field (if you use one) is copied onto the deal when it is created.
3. Something stores the gclid on the first visit, not only on the page with the form. Click an ad, browse two pages, submit, and check the deal.
4. Every form path carries it: Pipedrive Web Forms, your own site forms, the booking tool. Chatbot and live chat leads usually do not.
5. A dedicated conversion action for won deals exists in Google Ads, created at least a few hours before the first upload.
6. The upload fires on won, with the amount and the won time, and at least daily.
7. Count the deals won in the last 90 days that carry a gclid. Set that against the share of your budget on Google. The gap is the part of the loop that is still open.

The Pipedrive integration is native: a one click sign in and a field mapping screen, live in about 21 minutes with no developer. It writes source, campaign, ad, click ID, UTMs, landing page and a journey link onto the Person, and the attributed channel, campaign and credit onto the Deal, into dedicated LeadJourney custom fields so your existing source fields are left alone. It reads stage changes and won deals as they happen.

The capture half is one script on your site or in GTM. It records every visit server-side on your own domain, first-party, at 95%+ accuracy, and it captures gclid, gbraid and wbraid at the click, along with fbclid, li_fat_id and msclkid for the other platforms. The anonymous history is joined to the person at the form fill, the call or the booking, so the Monday click is still there on Thursday.

The upload half runs on the deal. When a deal is won, it goes to Google Ads as an offline conversion import matched on the gclid, with the deal value, and the same won deal goes to Meta and LinkedIn through their Conversions APIs and to Microsoft Ads on msclkid. Spend is pulled from the ad platforms and joined to the deals, and five attribution models run on the same events. The Chrome extension shows the same won deals and revenue as columns inside Google Ads, next to Google's own conversions.

The limits: tracking respects consent, so a visitor who declines is not measured, and a lead who never touched your website still needs a source typed in by a person. Google's 90-day rule applies to us as it does to everybody.

Start with Pipedrive lead source tracking and UTM parameters in Pipedrive, then the Meta Ads side of Pipedrive and the attribution tools that work with Pipedrive. On the mechanics, the GCLID guide, Google Ads enhanced conversions for leads and offline conversion tracking.