Contact-status qualification
Use selected HubSpot lifecycle statuses or lead statuses to define which contacts count as qualified outcomes.
HubSpot + Google Ads
Native connectionCRM
Send qualified HubSpot outcomes back to Google Ads.
Adscriptly connects HubSpot contact and deal data to a controlled Google Ads conversion workflow. Select the lifecycle statuses, lead statuses, or deal stages that count, map the field that stores the click identifier, and send eligible outcomes with a configured value.
H
Source
HubSpot
GA
Destination
Google Ads
Intended outcome
Help Google Ads distinguish a new contact from a qualified opportunity or closed deal.
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.
Deal-stage qualification
Map selected HubSpot deal stages to eligible conversion events and assign the configured value used by the workflow.
Click-identifier field mapping
Map the field that stores the advertising click identifier so downstream CRM outcomes can be tied back to the original ad click.
Reviewable Google Ads output
Choose the destination account and conversion action before the workflow is published.
Data flow
Know what moves between systems.
HubSpotAdscriptly logicGoogle Ads
HubSpot
Contact lifecycle or lead status
Adscriptly logic
Selected qualified-status rule
Google Ads
Named Google Ads conversion
HubSpot
HubSpot deal stage
Adscriptly logic
Selected qualified-stage rule
Google Ads
Eligible offline conversion
HubSpot
Captured click identifier
Adscriptly logic
Attribution to the originating ad click
Google Ads
Google Ads click conversion
HubSpot
Configured conversion value
Adscriptly logic
Value assigned during workflow setup
Google Ads
Value-bearing conversion signal
Setup
Set up and test the connection.
- 01
Connect HubSpot and Google Ads
Authorize the HubSpot portal and the Google Ads account that should receive qualified outcomes.
- 02
Select statuses, stages, and attribution
Choose the lifecycle or lead statuses, deal stages, and click-identifier field used by the workflow.
- 03
Map stages to conversion events
Define which selected statuses or stages count and set the conversion value attached to eligible outcomes.
- 04
Review the Google Ads destination
Confirm the conversion action and publish the workflow after the mappings are correct.
Connection controls
Choose the source scope and Google Ads destination.
- Only the connected HubSpot portal is available to the workflow.
- Stage and field mappings are explicit.
- The Google Ads account and conversion action are reviewed before publish.
- Provider connections can be revoked from Settings.
Related integrations
Integration FAQ
Before you connect.
Can HubSpot lifecycle stages be sent to Google Ads?
Yes. Adscriptly can map selected HubSpot lifecycle statuses, lead statuses, or deal stages into named Google Ads offline conversion events.
How does Adscriptly connect a HubSpot record to an ad click?
The workflow maps the HubSpot field that contains the advertising click identifier captured with the lead. That identifier is used when the qualified downstream outcome is prepared for Google Ads.
Can a conversion value be assigned to a HubSpot outcome?
Yes. A workflow can assign a configured conversion value to an eligible HubSpot outcome. It does not currently import each deal’s amount into the upload.
Does Adscriptly change my HubSpot pipelines?
No. This conversion workflow reads the CRM data used for mapping and qualification; it does not change your HubSpot pipeline structure.
HubSpot + Google Ads
Send qualified HubSpot outcomes to Google Ads.
Connect both systems, map the outcome, and review the destination before the workflow is published.
