Deal pipeline-stage qualification
Choose a Pipedrive pipeline and map selected deal stages to qualified or converted outcomes.
Pipedrive + Google Ads
Native connectionCRM
Send qualified Pipedrive outcomes to Google Ads.
Adscriptly connects one authorized Pipedrive account to a controlled Google Ads conversion workflow. Qualify records with selected lead labels or deal pipeline stages, use a selected person field to recover the captured GCLID, and attach the configured value used by the workflow.
P
Source
Pipedrive
GA
Destination
Google Ads
Intended outcome
Help Google Ads distinguish a captured contact from a Pipedrive lead or deal outcome your team considers qualified.
Connection scope
This page documents an enabled Adscriptly provider connection and its current source-specific conversion workflow.
What the connection does
What the connection reads, maps, and sends.
Lead-label qualification
Use selected Pipedrive lead labels when the label, rather than a deal stage, owns the business rule.
Person-field attribution
Select the Pipedrive person field that stores the GCLID used to connect a downstream record to the original ad click.
Controlled Google Ads destination
Review the destination customer, conversion action, and configured value before publishing the workflow.
Data flow
Know what moves between systems.
PipedriveAdscriptly logicGoogle Ads
Pipedrive
Pipedrive deal stage
Adscriptly logic
Selected pipeline-stage rule
Google Ads
Qualified or converted outcome
Pipedrive
Pipedrive lead label
Adscriptly logic
Selected label rule
Google Ads
Eligible offline conversion
Pipedrive
Selected person field
Adscriptly logic
Recover the captured GCLID
Google Ads
Google Ads click conversion
Pipedrive
Configured conversion value
Adscriptly logic
Value assigned during workflow setup
Google Ads
Value-bearing conversion
Setup
Set up and test the connection.
- 01
Connect Pipedrive and Google Ads
Authorize both providers and choose the Google Ads account that should receive the selected outcome.
- 02
Choose stages or labels
Select deal pipeline stages or lead labels that represent a qualified or converted record.
- 03
Map attribution and value
Choose the person field that stores the GCLID and set the conversion value used by the workflow.
- 04
Review and publish
Confirm the qualification rule, conversion action, destination account, and value before publishing.
Connection controls
Choose the source scope and Google Ads destination.
- Pipedrive access is limited to the authorized connection.
- Qualification uses deliberately selected stages or labels.
- The chosen person field is used for attribution, not arbitrary qualification.
- Destination account and conversion action remain explicit.
Related integrations
Integration FAQ
Before you connect.
Can Pipedrive deal stages become Google Ads conversions?
Yes. Selected Pipedrive deal pipeline stages can qualify an offline conversion when the workflow has the GCLID required for attribution.
Can I qualify Pipedrive leads by label?
Yes. The setup flow supports selected Pipedrive lead labels as an alternative to deal pipeline-stage qualification.
Which Pipedrive field connects the outcome to Google Ads?
Your team selects the Pipedrive person field that stores the captured GCLID. The workflow uses that identifier for the Google Ads click-conversion upload.
Does the workflow import each Pipedrive deal value?
No. The current conversion workflow sends the configured value chosen during setup rather than dynamically importing each deal amount.
Pipedrive + Google Ads
Send qualified Pipedrive outcomes to Google Ads.
Connect both systems, map the outcome, and review the destination before the workflow is published.
