Google Ads and GA4 tracking for Pipedrive
Google Ads on Pipedrive is an offline conversion import triggered by deals reaching won. Two things decide whether it works: whether your median click-to-won fits inside the 90-day window, and whether the conversion action was created as an import type — which cannot be changed later. Check both before building anything.
Free30 minutesNo obligation
Pipedrive + Google · what breaks
What goes wrong on Pipedrive
- 01
The identifier stops at the person and never reaches the deal
The single most common failure. Deals are where the value lives and where the field is usually missing.
- 02
Form fills counted as conversions
Cheap, abundant, and weakly correlated with won revenue.
- 03
Deal value ignored
A small deal and a large one are the same conversion unless the value is sent.
- 04
Long pipelines against import windows
Measure your median click-to-won before assuming a closed-won upload is possible.
Pipedrive + Google · the fix
What changes — Pipedrive + Google
Won deals as the conversion
From the deal's stage change, at the actual deal value.
The identifier present on the deal
Not only on the person, which is where most implementations stop.
Lost deals excluded and reopened deals handled
So the number reflects the pipeline as it actually is.
Pipedrive + Google · architecture
How the Google destinations behave on Pipedrive
Google Ads and GA4 on Pipedrive.
- 1
Offline conversion import on deal won
Against the original click, within the 90-day window.
- 2
Create the conversion action as an import type
A website action cannot be converted and this is discovered late.
- 3
Counting setting on 'one' for lead-type actions
So a repeat enquirer does not count three times.
- 4
Qualified deals as a fallback where cycles are long
Valued at deal value times your own win rate.
- 5
Read the match rate, not the upload result
A file can import cleanly and match almost nothing.
Pipedrive + Google · diagnose
Where Pipedrive tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Open a won deal and look for the identifier field
If it is on the person and not the deal, you have found the cause.
- 02
Compare won deals against reported conversions
Per deal, over a closed window.
- 03
Check the conversion action type
Import versus website. They are not interchangeable.
- 04
Measure median click-to-won
Against every import window, before anything else is designed.
- 05
Check for stage discipline
If half the team marks won late, the dates are wrong and so is everything built on them.
Pipedrive + Google · prove
The QA evidence — Pipedrive + Google
Run on Pipedrive specifically, on a live conversion rather than in preview mode.
Source of truth
Pipedrive's deals report — deals marked won by won-date, at their deal values
- A test lead taken through to a won deal, with the identifier confirmed present on the deal record.
- Won deals reconciled per deal against what each platform reports, over a closed window.
- A reopened deal confirmed not to produce a second conversion.
- The median click-to-won measured and stated in writing against every import window.
- Deal values confirmed sent as actual amounts rather than an average.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Pipedrive + Google · free audit
What we check in the free audit
- Open a won deal and look for the identifier field
- Compare won deals against reported conversions
- Check the conversion action type
- Measure median click-to-won
- Check for stage discipline
Checked against
Pipedrive's deals report — deals marked won by won-date, at their deal values
Free30 minutesNo obligation
Pipedrive + Google · when not to buy
When you don't need this on Pipedrive
Worth reading before you buy anything, from us or anyone.
- If your median click-to-won exceeds 90 days, closed-won upload cannot work against the original click. We will say so before quoting.
- If your team's stage discipline is inconsistent, fix that first — every number here depends on it.
- Check identifier coverage on your own deals before commissioning anything. Ten minutes, and it decides the whole project.
- If you close nearly everything you quote, form-fill optimization may be defensible and this is a smaller job.
Pipedrive + Google · what we deliver
What gets built for Google on Pipedrive
GA4 ecommerce events in the recommended shape
Correct names, transaction_id present, currency per order, an items array that agrees with the value.
Click identifiers captured and persisted
gclid, gbraid and wbraid — not just the first, because iOS traffic arrives with the others.
Enhanced Conversions from the data layer
Not from CSS selectors, which break on every redesign silently.
Conversion action settings reviewed
Counting, primary status and attribution window — free to change and more consequential than most tag work.
Written guarantee
95%+ tracking accuracy
Measured against Pipedrive's deals report — deals marked won by won-date, at their deal values. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Pipedrive + Google questions, answered
An import action. A standard website conversion action rejects uploads and cannot be converted afterwards, so it has to be created correctly from the start — this is discovered late often enough to be worth checking first.
'One' for lead-type conversions so a repeat enquirer does not count several times. 'Every' only if each deal genuinely represents a separate purchase from the same customer.
Where click identifier coverage is poor and you have consented email addresses, yes — it matches on hashed contact data rather than a click ID. It is a different mechanism with different requirements and it is the right answer when capture is the weak link.
Read the per-row diagnostics under Goals → Conversions → Uploads, then check that conversions actually appear against campaigns. A green result means the file parsed, not that the clicks matched.
Free · 30 min
Get Google Ads and GA4 right on Pipedrive
WhatsAppFree30 minutesNo obligation
