Pixelflow
Integrations

Trigger Events from Stripe Payments

Use the Stripe integration to send a Purchase event to Meta each time a payment completes in Stripe. This is the simplest way to track Stripe sales without building a custom setup.

Before you start, make sure your site is already connected in PixelFlow and you have access to create a restricted API key in Stripe.

Connect Stripe

  1. In your PixelFlow dashboard, go to Events and click Add Trigger.

  2. Choose Stripe Payments from the integration options.

Choose which payments to track

Select which Stripe payments should trigger Purchase events:

Connect Stripe modal showing payment tracking options
Choose whether to track all purchases or include subscription renewals.
  • All purchases — Every one-off sale and the first charge of a subscription. Recommended for most accounts.

  • All purchases + subscription renewals — Also fires a Purchase event each time a subscriber renews. Most accounts shouldn't need this.

Add your Stripe restricted API key

PixelFlow needs a restricted key to create webhooks in your Stripe account. This takes about a minute.

Connect Stripe modal showing API key setup instructions
Create a restricted key in Stripe with webhook-only access.
  1. Click Open Stripe API keys to go directly to the right page in Stripe.

  2. Click Create restricted key.

  3. Choose Providing this key to a 3rd party application, set the name to PixelFlow and URL to pixelflow.so.

  4. Check Customise permissions for this key, set Webhook to Write, and leave all other permissions as None.

  5. Click Create key, then paste the key (starts with rk_live_) into PixelFlow.

The restricted key can only create and delete webhooks — PixelFlow cannot access the rest of your Stripe account.

Select your payment method

Choose how you're collecting payments in Stripe so PixelFlow can show you the exact setup steps.

Connect Stripe modal showing payment method options
Select the payment method you use in Stripe.
  • Payment Link — A shareable Stripe link (starts with buy.stripe.com) you send customers or use on a button. Most common.

  • Third-party tool — Memberstack, Outseta, Bolt, or similar handles checkout for you.

  • Stripe Checkout — Your site redirects customers to a Stripe-hosted page (URL changes to checkout.stripe.com).

  • Pricing Table — A pre-built table embedded with a <stripe-pricing-table> snippet.

  • Stripe Elements — A custom payment form built with Stripe's developer SDK.

This optional step dramatically improves attribution by passing extra buyer data to Meta. It takes about 30 seconds in Stripe. The exact steps differ depending on your Stripe checkout setup, so select your Stripe setup and follow the instructions.

Connect Stripe modal showing redirect link setup instructions
Setting up a redirect link improves attribution significantly.

Review and connect

The final step shows a summary of your setup before connecting.

Connect Stripe modal showing review summary and data to be sent
Review your settings before connecting Stripe.

Click Connect Stripe to finish the setup.

When a payment completes, PixelFlow sends a Purchase event to Meta with:

  • Email address

  • Name

  • Phone number

  • Purchase value

  • Currency

  • Content Type

If you set up the redirect link after Stripe, PixelFlow also includes:

  • IP address

  • City, State, Zip Code & Country

  • fbc (if the user came from a Facebook ad)

  • External ID

  • User Agent

  • fbp

Purchase events are deduplicated automatically. If Stripe sends the same payment multiple times via webhooks, PixelFlow sends only one event to Meta.

Test the connection

  1. Complete a test payment in Stripe.

  2. Open your PixelFlow Events Log and confirm the Purchase event appears.

  3. Check Meta Events Manager to verify the event arrives there as well.

For a full testing workflow, see How to Test and Verify Your PixelFlow CAPI Setup.

What to do next

Was this helpful?