All integrations

Stripe logo

Stripe Server-Side Tracking

Stripe Server-Side Tracking

Stripe Server-Side Tracking

Send every Stripe payment to your ad platforms, matched back to the ad that drove it.

Send every Stripe payment to your ad platforms, matched back to the ad that drove it.

Checkout happens on Stripe’s domain where no pixel can fire. PixelFlow receives the payment by webhook, matches it to the visit on your site and sends one Purchase to Meta, TikTok and the rest.

Checkout happens on Stripe’s domain where no pixel can fire. PixelFlow receives the payment by webhook, matches it to the visit on your site and sends one Purchase to Meta, TikTok and the rest.

LIVE CONNECTIONBrowser + server
Stripe
Snapchat logo

Why your ad platforms can’t attribute purchases from Stripe

Why your ad platforms can’t attribute purchases from Stripe

Why your ad platforms can’t attribute purchases from Stripe

The moment a customer clicks Buy, they go from your website to checkout.stripe.com and your ad tracking is left behind. Cookies can't cross domains, so the click ID that ties that person to your ad stays behind on your site, and you cannot load a script on a page Stripe owns.

The moment a customer clicks Buy, they go from your website to checkout.stripe.com and your ad tracking is left behind. Cookies can't cross domains, so the click ID that ties that person to your ad stays behind on your site, and you cannot load a script on a page Stripe owns.

A webhook alone is not the answer either. It says a payment happened and who paid, but nothing about the ad they came from.

Meta Ads Manager

$0

attributed to your ads in Meta

Stripe

$597

paid to you through Stripe

How PixelFlow fixes it

How PixelFlow fixes it

How PixelFlow fixes it

PixelFlow holds on to the visit, then joins each Stripe payment to the click that caused it, then sends one Purchase to every ad platform.

PixelFlow holds on to the visit, then joins each Stripe payment to the click that caused it, then sends one Purchase to every ad platform.

Stitches the click back on

Stitches the click back on

The click ID and browser details from the visit are joined to the Stripe payment when it arrives.

The click ID and browser details from the visit are joined to the Stripe payment when it arrives.

Fires from Stripe’s webhook

Fires from Stripe’s webhook

Checkout, Payment Links, invoices and subscriptions, even if the customer never returns to your site.

Checkout, Payment Links, invoices and subscriptions, even if the customer never returns to your site.

Real values, tax optional

Real values, tax optional

Sends the amount Stripe charged, or the pre-tax amount if you prefer.

Sends the amount Stripe charged, or the pre-tax amount if you prefer.

Sends all order data

Sends all order data

Pulls all order data including name, email, phone, location, product name etc and sends it with the event

Pulls all order data including name, email, phone, location, product name etc and sends it with the event

Sent once and logged

Sent once and logged

Sent to your ad platform and logged so you can see exactly what can sent

Sent to your ad platform and logged so you can see exactly what can sent

Value and product filters

Value and product filters

Only fire above a minimum value, or for chosen Stripe product IDs.

Only fire above a minimum value, or for chosen Stripe product IDs.

Renewals, your call

Renewals, your call

Count recurring charges or leave them out. Off by default.

Count recurring charges or leave them out. Off by default.

Every ad platform

Every ad platform

One connection feeds Meta, TikTok, Snapchat, Pinterest, Reddit and ChatGPT.

One connection feeds Meta, TikTok, Snapchat, Pinterest, Reddit and ChatGPT.

Choose what's sent

Choose what's sent

Define which events should be sent to your ad platform.

For example, only send Purchases for the first purchase of a renewal or for all subscription payments.

Event name
Sent when
Enabled
Purchase
One-off sales and the first payment of every subscription.
Purchase
Every time a subscriber is charged again.
StartTrial
When someone starts a free trial.
Subscribe
When someone saves a card without being charged.
Event name
Sent when
Enabled
Purchase
One-off sales and the first payment of every subscription.
Purchase
Every time a subscriber is charged again.
StartTrial
When someone starts a free trial.
Subscribe
When someone saves a card without being charged.

Before & after using PixelFlow

Before & after using PixelFlow

Before & after using PixelFlow

What changes in Ads Manager once payments are stitched back to the click.

What changes in Ads Manager once payments are stitched back to the click.

Without PixelFlow
PixelFlow
Purchases never appear against a campaign in Ads Manager
Every Stripe purchase is matched back to the ad that drove it
Ad platforms report far fewer purchases than Stripe
Purchase counts in Ads Manager line up with Stripe
Revenue in Ads Manager is missing or much lower than real revenue
Real payment values and currency are sent with every event
Purchase events have a low Event Match Quality score
Hashed email, IP and click ID raise Event Match Quality
Events Manager keeps asking for more customer information
Complete customer data is sent automatically
Other setups fire on every Stripe charge
Only trigger events by value or product ID filters

Send conversions from Stripe to your ad platforms

Send conversions from Stripe to your ad platforms

Send conversions from Stripe to your ad platforms

Connect any ad platform in one click. The same Stripe payment feeds each platform’s conversions API with the real value, the customer’s hashed details and the ad click, so every Ads Manager sees the same purchase once.

Connect any ad platform in one click. The same Stripe payment feeds each platform’s conversions API with the real value, the customer’s hashed details and the ad click, so every Ads Manager sees the same purchase once.

Set it up with your AI agent.

Set it up with your AI agent.

Set it up with your AI agent.

Connect the PixelFlow MCP server to your agent can set up and install everything. Prefer to build your own custom tracking? Just use our infrastructure and build on top of it.

Connect the PixelFlow MCP server to your agent can set up and install everything. Prefer to build your own custom tracking? Just use our infrastructure and build on top of it.

Setup

FAQ

Stripe tracking questions, answered

Stripe tracking questions, answered

How payments are matched to the ad click, what reaches your ad platforms and what you need to get set up. Still stuck? Get in touch and we’ll help.

It means your Stripe payments reach Meta, TikTok and your other ad platforms from a server, through each platform's conversions API, rather than from a pixel in the customer's browser. That matters more for Stripe than for most tools, because checkout happens on Stripe's domain where your pixel cannot run at all. PixelFlow receives each payment from Stripe by webhook and sends it on as a Purchase event.

Stripe checkout happens on Stripe's domain, not yours. Cookies do not travel between domains, so the click ID that ties a purchase to an ad stays behind on your site. The payment goes through, but Meta, TikTok and the rest never learn which ad drove it.

PixelFlow captures the visitor's ad click and browser data when they land on your site and holds that visit while they pay on Stripe. When Stripe reports the completed payment, PixelFlow waits a short moment for the customer to return to your site, matches the two and sends one Purchase event with the click ID, browser ID, IP address and hashed customer details attached. If no visit can be matched, the purchase is still sent so no revenue goes missing.

No. The checkout page belongs to Stripe, so you cannot load your own scripts there. That is why a browser pixel alone can never attribute Stripe sales, and why the fix has to happen server side.

Nothing goes on Stripe. In PixelFlow open Track More Events, choose Stripe and paste a restricted API key with webhook write access. PixelFlow registers its own webhook endpoint in your Stripe account. Keep the PixelFlow script on your site and send customers back to a page on your domain after checkout so the payment can be matched to their visit. It takes about five minutes, and there is a step-by-step guide in the help centre.

The real value and currency from Stripe, the customer's hashed email, name, phone and address where Stripe has them, plus the ad click ID, browser ID, IP address and user agent from their visit to your site, and a shared event ID. Personal data is hashed before it leaves PixelFlow.

Yes. Checkout sessions, Payment Links, invoices and one-off payments all become Purchase events with the real value and currency, and trials and saved cards send StartTrial and Subscribe. Renewals are off by default so you only count new revenue, and you can exclude tax, set a minimum value or limit purchases to chosen Stripe product IDs.

Meta, TikTok, ChatGPT Ads, Snapchat, Pinterest and Reddit. One Stripe connection feeds every platform you connect. Plans include one, three or five ad platforms, and you can add more from $10 a month each.

No. Stripe often sends two or three webhooks for one payment, and PixelFlow collapses them into a single Purchase. That event carries the same event ID as any browser event for the order, so each ad platform counts it once.

Yes. PixelFlow supports consent-aware tracking so events respect your cookie banner, and personal data is hashed before it is sent to any ad platform. A data processing agreement is available.

Smarter, server-side tracking

Start sending accurate conversions today - no tag manager, no code, no developer required.

Compatible with

  • GoHighLevel logo
  • Kajabi logo
  • Stripe logo