How to Instantly Set Up a Make.com Stripe Webhook (Tracking)

A complete guide to Stripe webhook Make.com setup. Learn how to securely intercept payment data, parse metadata, and build a Stripe webhook for tracking server-side events.

Most tutorials simply teach you how to pass basic payment alerts into Slack. That is an amateur use case. We are going to engineer a Stripe webhook Make.com setup specifically designed to extract ad click identifiers (like the fbclid) so you can build a secure server-side tracking pipeline.

1. Make.com Stripe Integration Webhook Generation

Before you touch Stripe, you need to generate the “listener” in Make.com. This acts as the secure endpoint that catches the data payload.

• Open your Make.com scenario and add a new module.
• Search for Webhooks and select Custom Webhook.
• Click Add to create a new hook and name it “Stripe Tracking Catcher”.
• Copy the unique URL to your clipboard (it will look like https://hook.us1.make.com/abc123xyz...).

2. Stripe Configuration (The Critical Layer)

Now, we route the financial data from Stripe to Make.com. You must configure this inside the Stripe Developer Dashboard to ensure you only catch verified transactions.

• Log in to Stripe and navigate to Developers > Webhooks.
• Click Add an Endpoint.
• Paste the Make.com URL you generated in the previous step.
• CRITICAL: Do not select “all events.” Under the “Select events to listen to” menu, select strictly: charge.succeeded.

Listening only to charge.succeeded guarantees that failed payments or duplicate checkouts do not falsely inflate your ad platforms.

3. The Stripe Webhook Tracking Payload

When a successful purchase occurs, Stripe will instantly fire a JSON payload to your Make.com scenario. Here is exactly what the tracking architecture looks like when correctly mapped:

{
  "id": "evt_123456789",
  "type": "charge.succeeded",
  "data": {
    "object": {
      "amount": 5000,
      "billing_details": {
        "email": "operator@matrix.com"
      },
      "metadata": {
        "fbclid": "IwAR2xyz123abc...",
        "utm_source": "facebook",
        "utm_campaign": "Q3_Retargeting"
      }
    }
  }
}

4. The Data Parsing Layer (The Differentiator)

This is where standard tutorials fail and high-ticket attribution engines succeed. Notice the metadata object in the JSON payload above.

To pass tracking parameters into Stripe, you must configure your checkout page (like ThriveCart or Stripe Payment Links) to append URL parameters into the Stripe session’s metadata. Once the Make.com Stripe webhook catches the payload, you map the data.object.metadata.fbclid directly into your attribution pipeline.

⚠️ Operational Warning:

Once you extract this data, you must push it to the Meta API perfectly formatted. If you successfully catch the Stripe webhook but get errors pushing the data to Facebook, read our guide to fix the CAPI 400 Bad Request error.

5. Why Server-Side Webhooks Are the New Standard

Modern ad platforms rely entirely on server-side signals because browser-based tracking is increasingly unreliable due to privacy restrictions, ad blockers, and iOS updates. By using a Make.com Stripe webhook, you ensure first-party financial data is transmitted directly between backend systems without loss.

By routing this pure, unblockable data back into your ad platforms, you effectively train the Meta and Google algorithms with 100% accurate conversion data, drastically lowering your cost per acquisition (CPA).

Frequently Asked Questions