Receive CRM events
Bring the selected lead, opportunity, or revenue event into Adscriptly through a mapped webhook payload or a Zapier workflow you control.
CRM + Google Ads
Webhook or ZapierCRM
Connect a CRM outcome to Google Ads, even without a native connector.
Use this workflow for any CRM that can send a webhook or participate in Zapier. Map the qualified status, stage, or revenue milestone, include the supported attribution fields, and review the Google Ads conversion destination.
C
Source
CRM
GA
Destination
Google Ads
Intended outcome
Send qualified CRM events to Google Ads through a webhook or Zapier when no native Adscriptly connector is available.
Connection scope
Native Adscriptly pages remain the better setup reference for HubSpot, Salesforce, GoHighLevel, Pipedrive, and Zoho CRM.
What the connection does
Choose which CRM events to send to Google Ads.
Define the CRM outcome
Choose the lead status, opportunity stage, tag, or revenue condition that represents the conversion your business wants to optimize.
Preserve the ad-click field
Capture a supported Google Ads click identifier before the lead enters the CRM and include it in the webhook or Zapier payload.
Review the Google Ads output
Choose the Google Ads account and conversion action, inspect the mapping, and test the external handoff before enabling it.
Data flow
Know what moves between systems.
CRMAdscriptly logicGoogle Ads
CRM
CRM status or stage event
Adscriptly logic
Mapped outcome rule
Google Ads
Qualified CRM conversion
CRM
Status, stage, tag, or value field
Adscriptly logic
Selected qualified-outcome condition
Google Ads
Eligible CRM conversion
CRM
Mapped CRM click-ID field
Adscriptly logic
Recover click-level attribution
Google Ads
Google Ads click conversion
CRM
CRM record and event ID
Adscriptly logic
Stable event identity and duplicate handling
Google Ads
Stable conversion record
Setup
Set up and test the CRM event route.
- 01
Choose a CRM trigger
Start with the qualified status, stage, or revenue milestone that represents the business outcome you want to route.
- 02
Send a test payload
Use Zapier or your webhook sender to deliver representative fields, including mapped crm click-id field when attribution depends on it.
- 03
Map the qualification rule
Map the exact status, stage, or value condition that counts. Keep records that do not meet the rule out of the advertising signal.
- 04
Review the Google Ads destination
Confirm the destination account, conversion action, timestamp, value, and currency before the external handoff is enabled.
Connection controls
Review the connection method, event rule, and destination.
- The connection uses a mapped webhook or Zapier route; it is not a native source integration.
- CRM must send the fields used by the mapping.
- A CRM record without the required attribution field cannot be treated as a click-linked upload.
- The Google Ads destination is reviewed before the handoff is enabled.
Integration FAQ
Before you connect.
How does the CRM Google Ads integration work in Adscriptly?
Adscriptly receives a mapped CRM event through a webhook or Zapier, applies the configured rule, and prepares the eligible outcome for the selected Google Ads destination.
What must CRM send?
The payload must include the event fields used for qualification and a stable event identifier. When click-level attribution is required, it must also include the supported identifier captured before the handoff.
When should I use a native CRM page instead?
Use the native page when your CRM is in the supported provider catalog because it documents the provider-specific fields and scopes. Use this page for a webhook or Zapier-based CRM route.
Does Adscriptly change records in CRM?
No. This route receives the mapped event for qualification and delivery. It does not edit the source record, workflow, audience, catalog, or storefront configuration.
CRM + Google Ads
Send a selected CRM event to Google Ads.
Choose the trigger, send a representative payload, map the rule, and review the destination before enabling the external handoff.
