Receive Stripe events
Bring the selected checkout, payment, invoice, or subscription event into Adscriptly through a mapped webhook payload or a Zapier workflow you control.
Stripe + Google Ads
Webhook or ZapierRevenue
Turn a verified Stripe revenue event into a Google Ads signal.
Use a Stripe webhook or Zapier trigger for the checkout, payment, invoice, or subscription outcome your business recognizes. Map the eligibility rule, stable event identity, value, and supported paid-click attribution before routing it to Google Ads.
S
Source
Stripe
GA
Destination
Google Ads
Intended outcome
Connect media optimization to a selected payment outcome rather than a page view or checkout start.
Connection scope
This route uses selected Stripe events as advertising signals. It does not change payments, invoices, subscriptions, refunds, or customer records.
What the connection does
Choose which Stripe events to send to Google Ads.
Choose the accepted payment state
Require the event type and payment, invoice, or subscription state that represents recognized revenue for the workflow.
Carry checkout attribution
Store and include the supported Google Ads click identifier with the Stripe object or event metadata when click-level attribution is required.
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.
StripeAdscriptly logicGoogle Ads
Stripe
Stripe revenue event
Adscriptly logic
Event-type and payment-state check
Google Ads
Selected revenue conversion
Stripe
Event type and payment state
Adscriptly logic
Selected revenue eligibility rule
Google Ads
Accepted revenue outcome
Stripe
Stripe metadata click ID
Adscriptly logic
Tie the payment to the original ad click
Google Ads
Google Ads revenue conversion
Stripe
Stripe event and object ID
Adscriptly logic
Stable event identity and duplicate handling
Google Ads
Stripe-backed conversion record
Setup
Set up and test the Stripe event route.
- 01
Choose a Stripe trigger
Start with the successful payment or subscription 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 stripe metadata click id when attribution depends on it.
- 03
Map the qualification rule
Choose the event type and accepted state, including refund handling. Keep records that do not meet the rule out of the advertising signal.
- 04
Review the Google Ads destination
Confirm the account, conversion action, value source, currency, and refund behavior 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.
- Stripe must send the fields used by the mapping.
- The route cannot connect a payment to an ad click unless the supported identifier was captured and retained.
- The Google Ads destination is reviewed before the handoff is enabled.
Related integrations
Integration FAQ
Before you connect.
How does the Stripe Google Ads integration work in Adscriptly?
Adscriptly receives a mapped Stripe event through a webhook or Zapier, applies the configured rule, and prepares the eligible outcome for the selected Google Ads destination.
What must Stripe 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 Stripe refunds be handled?
Define refund behavior in the event contract and workflow before enabling the external handoff. This page does not promise automatic retroactive adjustment for every Stripe or Google Ads setup.
Does Adscriptly change records in Stripe?
No. This route receives the mapped event for qualification and delivery. It does not edit the source record, workflow, audience, catalog, or storefront configuration.
Stripe + Google Ads
Send a selected Stripe event to Google Ads.
Choose the trigger, send a representative payload, map the rule, and review the destination before enabling the external handoff.
