Skip to content

Capture GCLID in Pipedrive and Send Offline Conversions to Google Ads

A Google Ads click identifier (GCLID) is the thread that ties a paid click to a real lead. If it never reaches your CRM, you can see clicks but not customers. This guide shows how to carry the GCLID from a website form into Pipedrive and then return it to Google Ads as an offline conversion, so bidding can learn from the leads that actually matter.

What the GCLID is and why it matters in Pipedrive

The GCLID is a value Google Ads appends to the landing page URL when someone clicks an ad. It is the only reliable key that lets Google Ads match a later CRM event back to the original click. Without it, offline conversion imports cannot attribute a closed deal or a qualified lead to the ad that produced it. Storing the GCLID on the Pipedrive record keeps that link intact through the sales cycle.

The four-step capture flow

The flow has four stages: install the capture script and add a hidden GCLID field to forms; the script saves the GCLID when a visitor first arrives and writes it into the hidden field on submit; the form tool captures the value alongside name, email and phone; the value is passed into Pipedrive through a native integration or a connector such as Zapier or Make.

Where the GCLID lives at each stage

Use this field map to check that nothing drops the value between the ad click and the CRM record.

Choosing the conversion point

Before wiring the return path, decide which pipeline event counts as the conversion. Sending only closed deals feels accurate, but Google's smart bidding strategies (Maximise Conversions, Maximise Conversion Value, Target CPA) need roughly 50 conversions per month to optimise well. If you close fewer than 50 deals a month, an earlier event such as Deal created in Pipedrive gives the system enough signal. Use the checklist below to pick a stage.

Creating the offline conversion in Google Ads

In Google Ads, open Goals, then Conversions, add a new conversion and choose Offline Conversion. On the final data-source screen, select the option to add a data source later. This creates the conversion action that the return path will target.

Returning the GCLID with Zapier

In Zapier, create a Zap whose trigger matches the conversion point you chose (for example, a new Deal in Pipedrive). Set Google Ads as the action and choose Send Offline Conversion. Then map the stored GCLID from Pipedrive to the matching field in the action. Test the Zap before scaling spend.

Why URL-only capture fails and browser storage succeeds

Many form tools can read URL parameters, but only from the URL present at submit time. If a visitor clicks an ad, lands on the homepage, then navigates to a contact page before filling the form, the GCLID is gone from the URL and is never captured. A capture script that stores the GCLID in the visitor's browser avoids this: the value survives page changes and return visits, and is written into the hidden field whenever the form is submitted.

What else can travel with the GCLID

Beyond the GCLID, the same hidden-field approach can carry UTM parameters and organic source data. For a law firm running paid search, a lead might arrive with Channel = Paid Search, Channel Drilldown 1 = Google, Drilldown 2 = the campaign name, Drilldown 3 = the keyword, and Drilldown 4 = the ad. An organic search lead might carry Channel = Organic Search, Drilldown 1 = Google, Drilldown 2 = the search engine domain, and Drilldown 3 = the query when available. These fields let Pipedrive reports show where all leads originate, not only paid ones.

GCLID field and control map
StageWhere the value sitsWhat to check
Ad clickLanding page URL query stringThe GCLID parameter is present on the first page load
Visitor browsingBrowser storageThe value persists across pages and return visits
Form submitHidden GCLID fieldThe field is present on every lead form
Form toolSubmission recordThe GCLID is captured with name, email and phone
PipedriveDeal or person fieldA custom field stores the GCLID on the record
ZapierMapped action fieldThe Pipedrive GCLID maps to the Google Ads offline conversion field
Google AdsOffline conversionThe conversion action exists and receives test data

Field names and connector steps reflect the described workflow; confirm current Pipedrive and Zapier field labels in your own accounts.

Conversion-point decision checklist
QuestionIf yesIf no
Do you close 50 or more deals per month?Sending closed deals gives smart bidding enough volumeConsider an earlier event such as Deal created
Is lead quality the main signal you want Google to learn from?Send a qualified-lead eventSend a deal-created event
Do you need revenue-based bidding?Send conversion value with the closed dealSend a count-only conversion at an earlier stage
Can you test the Zap before scaling spend?Run a test conversion and verify it appearsDo not increase spend until the test passes

The 50-conversions-per-month figure is the threshold described for Google's smart bidding strategies; confirm current Google Ads guidance before relying on it.

Frequently asked questions

Does the GCLID survive if a visitor browses several pages before filling a form?

Yes, when the capture script stores it in the visitor's browser. URL-only capture would lose it after navigation, but browser storage keeps the original click value available at submit time, even if the visitor leaves and returns later.

Can I send the GCLID to Pipedrive without Zapier?

Yes. If your form builder has a native Pipedrive integration, it can pass the GCLID along with the other form fields. Zapier or Make is the fallback when no native integration exists.

Which pipeline stage should I use for the offline conversion?

If you close fewer than about 50 deals a month, an earlier event such as Deal created gives Google's smart bidding more data. If volume is high and revenue accuracy matters most, a closed-deal event with value can work.

What other lead source data can I store alongside the GCLID?

UTM parameters and organic channel details can be captured through the same hidden-field method, giving Pipedrive records a fuller picture of paid and organic origins.