Receive Webhook events
Bring the documented JSON event payload into Adscriptly through a mapped webhook payload or a Zapier workflow you control.
Webhook + Google Ads
WebhookDeveloper tools
Build a webhook route for Google Ads conversion outcomes.
Post a documented first-party event from your app or automation layer, validate its required fields and stable identity, apply the qualification rule, and prepare the accepted outcome for the selected Google Ads conversion action.
W
Source
Webhook
GA
Destination
Google Ads
Intended outcome
Use one documented event contract for sources that can send the required webhook payload.
Connection scope
A webhook expands source coverage, but it does not remove the attribution, consent, validation, or identity requirements of the destination.
What the connection does
Choose which Webhook events to send to Google Ads.
Validate the business outcome
Require the event name, status, value, or other mapped fields that prove the source event meets the conversion rule.
Map Google Ads attribution
Include the supported click identifier, event time, and other fields required by the chosen Google Ads conversion path.
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.
WebhookAdscriptly logicGoogle Ads
Webhook
Webhook event name and payload
Adscriptly logic
Schema and required-field validation
Google Ads
Reviewed conversion action
Webhook
Event status and business fields
Adscriptly logic
Configured qualification condition
Google Ads
Accepted conversion event
Webhook
Click identifier and event timestamp
Adscriptly logic
Normalize destination attribution fields
Google Ads
Google Ads conversion payload
Webhook
Source event ID
Adscriptly logic
Stable event identity and duplicate handling
Google Ads
Idempotent conversion record
Setup
Set up and test the Webhook event route.
- 01
Choose a Webhook trigger
Start with the server-side business event 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 click identifier and event timestamp when attribution depends on it.
- 03
Map the qualification rule
Define the required fields and accepted values. 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, event time, 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.
- Webhook must send the fields used by the mapping.
- The sender is responsible for capturing and sending the attribution fields required by the selected upload path.
- The Google Ads destination is reviewed before the handoff is enabled.
Related integrations
Integration FAQ
Before you connect.
How does the Webhook Google Ads integration work in Adscriptly?
Adscriptly receives a mapped Webhook event through a webhook or Zapier, applies the configured rule, and prepares the eligible outcome for the selected Google Ads destination.
What must Webhook 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.
Can any webhook event become a Google Ads conversion?
Only when the payload meets your qualification rule and includes the fields required by the chosen Google Ads conversion path. A generic event without attribution data is not automatically uploadable.
Does Adscriptly change records in Webhook?
No. This route receives the mapped event for qualification and delivery. It does not edit the source record, workflow, audience, catalog, or storefront configuration.
Webhook + Google Ads
Send a selected Webhook event to Google Ads.
Choose the trigger, send a representative payload, map the rule, and review the destination before enabling the external handoff.
