DATALYR

Stripe to Google Ads.

Send every Stripe payment to Google Ads so campaigns optimize on real revenue. Each payment uploads as a conversion with the ad click attached.

What gets sent.

What DATALYR sends from Stripe to Google Ads
DATALYR eventWhen it firesSent to Google asWhat it carries
checkout.session.completedA Checkout Session is paidYour Import from clicks conversion actionamount_total as the value (0 when the session has an invoice), currency, the gclid, and hashed email
invoice.payment_succeededAn invoice is paid, such as a subscription paymentYour Import from clicks conversion actionamount_paid as the value, currency, the gclid, and hashed email
payment_intent.succeededA PaymentIntent you created succeedsYour Import from clicks conversion actionamount_received as the value, currency, the gclid, and hashed email

How it's matched.

DATALYR checks these in order and stops at the first one that finds the ad click.

  1. The visitor ID on the Stripe object: client_reference_id on a Checkout Session, metadata.visitor_id on a PaymentIntent or Subscription
  2. For Checkout, the session ID the site reported as the browser left for Stripe
  3. The customer email, when no ad click was found

Google gets the gclid (or gbraid or wbraid), looked up within 90 days of the click, plus email and phone hashed with SHA-256. DATALYR uploads only when the conversion has a click ID, an email or a phone number.

How it works.

  1. 01

    Connect Stripe.

    Open Sources, select connect on Stripe and finish Stripe's sign-in. DATALYR owns the webhook, so you create nothing in Stripe. Pass the visitor ID when you create a Checkout Session or PaymentIntent. Payment Links get it automatically.

  2. 02

    Connect Google.

    In Google Ads, create a conversion action of type Import from clicks (Goals, Conversions, New, Import, Manual import using the API). In Sources, connect Google Ads and set your customer account as primary. In Conversions, create a rule: trigger event checkout.session.completed, target platform Google, that conversion action. Set value to dynamic and pick the currency.

  3. 03

    Check one conversion.

    Complete one real Stripe payment from a Google ad click. Find checkout.session.completed or payment_intent.succeeded in Events, then open the newest row in Conversions and read the reply from Google.

Check it worked.

  • In Events, the payment's visitor_id does not start with stripe_, and the event carries a gclid or an email. Google rejects an upload with neither.
  • Select send test event on the rule. The request carries validateOnly, so Google checks it without recording a conversion.
  • Trigger one real conversion. Its row reads processing, then sent within 40 minutes once Google's own diagnostics confirm it.

View docsStripe revenueGoogle AdsConversion delivery

Questions, answered.

Contact us
  • Your site passes the visitor ID to Stripe, as client_reference_id on Checkout or metadata.visitor_id on a PaymentIntent. DATALYR uses it to find the visit and its gclid, looked up within 90 days. Payment Links get the visitor ID automatically from the web SDK.

  • Import from clicks. A GA4, website or call action accepts no API upload, and every conversion sent to it fails.

  • No. Google rejects negative conversion values, so the rule editor blocks any trigger event with refund or chargeback in its name. Handle refunds outside conversion rules.

See what really drives revenue.

Real-time attribution, analytics and conversions for every channel, campaign and ad, ready for your team and your agents.

Get started