DATALYR

Stripe to Meta Conversions API.

Send every Stripe payment to Meta so ads optimize on real sales. Each payment reaches your Meta Pixel with the ad click attached.

What gets sent.

What DATALYR sends from Stripe to Meta Conversions API
DATALYR eventWhen it firesSent to Meta asWhat it carries
checkout.session.completedA Checkout Session is paidPurchaseamount_total as the value (0 when the session has an invoice), currency, the ad click and hashed email
invoice.payment_succeededAn invoice is paid, such as a subscription paymentPurchaseamount_paid as the value, currency, the ad click and hashed email
payment_intent.succeededA PaymentIntent you created succeedsPurchaseamount_received as the value, currency, the ad click and hashed email
charge.refundedA refund is createdNot sentThe rule editor blocks a refund trigger aimed at a purchase event

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

Meta gets the click ID (fbc, built from the _fbc cookie or fbclid) and browser ID (fbp), plus email, phone and name hashed with SHA-256 when known. DATALYR sends the same event ID the browser pixel uses, so Meta merges the pair into one conversion.

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 Meta.

    Open Sources, select connect on Meta Ads and sign in with Facebook Login for Business. Set the primary ad account. In Conversions, select manage rules, then new rule: trigger event checkout.session.completed, target platform Meta, your pixel, platform event Purchase. Set value to dynamic and pick the currency.

  3. 03

    Check one conversion.

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

Check it worked.

  • In Events, the payment's visitor_id does not start with stripe_. That prefix means the visitor ID never reached Stripe, so pass client_reference_id on Checkout and metadata.visitor_id elsewhere.
  • Set a Test Events code on the rule, then select send test event. The event shows in Events Manager under Test events with the name, value and currency you mapped. Without a code, a test is a real conversion.
  • Open the newest row in Conversions. Its status reads sent, and the response body carries Meta's own acceptance field.

View docsStripe revenueMeta AdsConversion delivery

Questions, answered.

Contact us
  • No. DATALYR sends the same event ID the browser pixel uses, and Meta merges the pair into one conversion when both fire on the same page load. A Stripe payment arrives by webhook, so keep the purchase coming from DATALYR alone.

  • Use checkout.session.completed for Checkout, payment_intent.succeeded for payments you create yourself, and invoice.payment_succeeded for subscription invoices. A Checkout Session that has an invoice carries a value of 0, and DATALYR skips a zero-value purchase, so the invoice event carries the amount. Never enable two rules on the same trigger and pixel.

  • The event value is gross, before tax and processor fees. Stripe amounts are converted from minor units, such as cents, to the currency's own unit.

  • The connection is live mode. Connect a test-mode Stripe account separately for test payments, and set a Test Events code on the Meta rule so a test is not a real conversion.

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