Receive Instapage events
Bring the selected landing-page form submission into Adscriptly through a mapped webhook payload or a Zapier workflow you control.
Instapage + Google Ads
Send an Instapage form submission through a webhook or Zapier, require the answers that define a qualified lead, carry the supported click identifier, and review the destination conversion action before enabling the external handoff.
Source
Instapage
Destination
Google Ads
Intended outcome
Separate a qualified landing-page response from a generic form submission in Google Ads.
Connection scope
This route handles submitted form outcomes. It does not install Google Ads tags, edit Instapage experiments, or change landing-page content.
What the connection does
Bring the selected landing-page form submission into Adscriptly through a mapped webhook payload or a Zapier workflow you control.
Require the contact and custom-answer fields that distinguish an eligible lead from an incomplete or out-of-scope response.
Capture and include the supported Google Ads click identifier with the form payload when click-level attribution is required.
Choose the Google Ads account and conversion action, inspect the mapping, and test the external handoff before enabling it.
Data flow
Instapage form payload
Form and required-field check
Qualified lead conversion
Form answers and qualification fields
Required-answer condition
Qualified landing-page lead
Hidden click-identifier field
Connect the submission to the paid click
Google Ads lead conversion
Submission or source event ID
Stable event identity and duplicate handling
Submission-backed conversion record
Setup
Start with the Instapage form submission that represents the business outcome you want to route.
Use Zapier or your webhook sender to deliver representative fields, including hidden click-identifier field when attribution depends on it.
Choose the form and answers that must be present. Keep records that do not meet the rule out of the advertising signal.
Confirm the account, lead conversion action, timestamp, and value rule before the external handoff is enabled.
Connection controls
Related integrations
Integration FAQ
Adscriptly receives a mapped Instapage event through a webhook or Zapier, applies the configured rule, and prepares the eligible outcome for the selected Google Ads destination.
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.
No. This page covers a post-submission webhook or Zapier outcome route. Tag installation, consent, and landing-page tracking remain separate setup concerns.
No. This route receives the mapped event for qualification and delivery. It does not edit the source record, workflow, audience, catalog, or storefront configuration.
Instapage + Google Ads
Choose the trigger, send a representative payload, map the rule, and review the destination before enabling the external handoff.