Every Stripe payment tied to the campaign that drove it

Updated July 21, 2026

If you charge with Stripe, you probably built your own funnel: sales page, checkout, upsells. That's exactly where the Meta pixel stumbles — iOS shortens cookie lifetimes, ad blockers kill the script before it fires, and a thank-you-page Purchase counts even payments that were declined. The result: Ads Manager shows one number, Stripe shows another.

IzeAds fixes this at the server level: Stripe notifies IzeAds on every payment, and IzeAds ties the sale back to the original click through the tracking code (SCK) that followed the buyer from your ad. What enters your dashboard is the payment confirmed by the processor — and refunds and chargebacks are counted against the same ledger.

How to set it up

The connection is done inside IzeAds in a few minutes: you connect Meta, generate the notification link and enable it in the platform panel. The full, always up-to-date walkthrough lives in the help center.

Open the guide in the help center →

What the integration delivers

Approved payments in real time

Every charge approved in Stripe shows up in your dashboard instantly, attributed to the campaign, ad set and ad that drove it.

Truly net ROAS

Refunds and chargebacks adjust the numbers automatically — you scale on real results, not gross ones.

Works with your custom funnel

Own checkout, sales page, upsell flow: tracking follows the buyer from ad to payment, whatever the path looks like.

CAPI back to Meta

The confirmed conversion is sent back to Meta via Conversions API — and to 7 other ad platforms — feeding the algorithm a clean signal.

Immune to iOS and ad blockers

The sale arrives from Stripe's server, not the browser. An expired cookie or blocked script won't erase the attribution.

Frequently asked questions

I use Stripe on my own checkout / custom sales page — does it work?

Yes. The tracking code follows the buyer from the ad click to the payment, even in a fully custom funnel. Once Stripe confirms the charge, the sale comes back attributed to the right campaign.

Why isn't the Meta pixel enough to track Stripe sales?

Because the pixel depends on the browser and the thank-you page: iOS and ad blockers kill part of the fires, and what does fire doesn't guarantee an approved payment. IzeAds receives the event straight from Stripe's server — only confirmed payments count.

Do refunds and chargebacks show up in the dashboard?

Yes. When Stripe reports a refund or dispute, IzeAds adjusts the revenue and ROAS of the matching campaign — the number you see is always net.

Can I connect Stripe alongside other platforms?

Yes. Each platform gets its own notification link, and all sales land in the same IzeAds dashboard, each attributed to its campaign.

More integrations

Connect in ~4 minutes

Create your account, connect Meta and paste one webhook link. Free trial, no lock-in.