How to Connect Stripe Subscription Revenue to Ad Campaigns

Key takeaways
- Airbridge has no native Stripe integration. You forward Stripe events yourself through the S2S API, or through a supported subscription tool.
- On Core, use three standard events: Start Trial, Subscribe and Unsubscribe. A first payment, a trial conversion and a renewal all arrive as Subscribe.
- Failed payments, refunds and trial ending soon have no standard event. Custom events are on the Growth plan only.
- Each event you send counts as one data point. Core includes 500K data points per month for $40+/mo after a 14-day free trial.
- Read the results in the Revenue, Actuals, Funnel and Retention reports.
On this page
To connect Stripe subscription revenue to ad campaigns, send each Stripe billing event to your mobile measurement partner (MMP) as a standard event from your own server. The Airbridge SDK records where the user came from. Your server listens to Stripe webhooks and sends Start Trial, Subscribe and Unsubscribe events to Airbridge through the server-to-server (S2S) API.
Airbridge publishes this blog. It has no native Stripe integration, so this server path is the real one. Airbridge then credits that revenue to the campaign. If you already use RevenueCat or Adapty, their Airbridge integrations are a second path. This guide walks through both, step by step.
At a glance (as of November 2026)
- Airbridge has no native Stripe integration. You forward Stripe events yourself through the S2S API, or through a supported subscription tool.
- On Core, use three standard events: Start Trial, Subscribe and Unsubscribe. A first payment, a trial conversion and a renewal all arrive as Subscribe.
- Failed payments, refunds and "trial ending soon" have no standard event. Custom events are on the Growth plan only.
- Each event you send counts as one data point. Core includes 500K data points per month for $40+/mo after a 14-day free trial.
- Read the results in the Revenue, Actuals, Funnel and Retention reports.
Why do Stripe and your MMP each see only half the picture?
Stripe knows the money: charges, invoices, subscription status and cancellations. It does not know which ad brought the customer.
An MMP knows the source: which ad was clicked, which campaign it belonged to, and when the install happened. It does not see billing unless you send billing events to it.
| System | Knows | Does not know |
|---|---|---|
| Stripe | Payments, subscription status, cancellations | Which campaign acquired the customer |
| Airbridge | Ad click, channel, campaign, install time | Payments, unless you send them as events |
| Both, joined by a shared user ID | Which campaign drove which subscription revenue | Only what you choose not to send |
The join is a user ID that both systems know. That ID is the most important part of the whole setup.
Should you use the S2S API or a subscription tool?
| Your setup | Path | What you build |
|---|---|---|
| Stripe only (web checkout or in-app with Stripe), with a backend team | Your server to Airbridge S2S API | A webhook handler and an event mapping |
| RevenueCat or Adapty already in the app | The subscription tool's Airbridge integration | No webhook code for the events the tool forwards. Confirm Stripe coverage first. |
| App Store and Google Play billing only | Subscription tool or SDK events | Stripe is not involved |
RevenueCat, Adapty and Superwall are supported Airbridge integrations. Core includes 2 third-party integrations. Whether RevenueCat or Adapty forward Stripe-billed purchases to Airbridge depends on how you set them up. Check their docs before you rely on it. Superwall's integrations page lists Stripe among its revenue-tracking sources, so it is worth checking too if you use Superwall. The rest of this guide covers the S2S path.
Map Stripe events to Airbridge standard events
Core uses standard events only. Airbridge has 25 standard events. Three of them cover the subscription lifecycle.
| Stripe webhook | What it means | Airbridge event on Core | Notes |
|---|---|---|---|
customer.subscription.created with status trialing |
Trial started | Start Trial | Send once per trial |
invoice.paid (first paid invoice, after a trial or with no trial) |
First payment | Subscribe | Include revenue and currency. Skip zero-amount invoices, which can appear when a trial starts |
invoice.paid (later invoices) |
Renewal | Subscribe | Renewals also arrive as Subscribe. There is no separate renewal event. |
customer.subscription.updated with cancel at period end, or customer.subscription.deleted |
Cancelled | Unsubscribe | Send once per subscription, at whichever comes first |
invoice.payment_failed |
Payment failed | No standard event | Custom events are Growth only |
customer.subscription.trial_will_end |
Trial ends soon | No standard event | Custom events are Growth only |
charge.refunded |
Refund | No standard event | Do not send it as a negative Subscribe |
One consequence: on Core, a count of Subscribe events includes renewals. A "trial-to-paid rate" built from Subscribe counts will be too high if renewals are mixed in. Keep the date range short, or track first payments in your own database as well.
To tell them apart, put the type in the event you send. Set the event action to initial or renewal and group the report by Event Action, which is how the Superwall integration does it. The semantic attributes isRenewal and renewalCount also exist.
Step-by-step setup: Stripe to Airbridge
Step 1: Install the Airbridge SDK
Add the Airbridge SDK to your app. A basic install takes about 5 minutes. The SDK records the install and its source. This record is what Stripe revenue will be credited to later.
Step 2: Set a user ID in the SDK and store it with the Stripe customer
When the user signs up or signs in, set your own user ID in the Airbridge SDK. Store the same user ID on the Stripe customer, for example in the customer's metadata. Your server needs this link to look up who a webhook belongs to.
Use an ID you control, such as your internal account ID. Do not use an email address as the ID.
Step 3: Register a Stripe webhook endpoint
In the Stripe dashboard, add an endpoint on your server and select only the events you will map: customer.subscription.created, customer.subscription.updated, customer.subscription.deleted and invoice.paid. Fewer events means less noise and fewer data points.
Step 4: Build the forwarding handler
A small service (a serverless function is enough) should:
- Verify the Stripe webhook signature before it reads anything.
- Read the Stripe customer and find your user ID in the metadata.
- Decide the Airbridge event from the mapping table above. Skip zero-amount invoices, and send Unsubscribe only once per subscription.
- Add revenue and currency for Subscribe.
- Send the event to the Airbridge S2S API with the identifiers the API guide requires.
- Log the Stripe event ID so a retried webhook does not send the same event twice.
Identifiers. Send the event to the S2S endpoint for mobile apps, not the web one. A web checkout has no device ID, so set user.externalUserID to the same user ID your app passes to the Airbridge SDK with setUserID. Airbridge then uses the device mapped to that user ID. If no device is mapped, attribution is less accurate. Also include app.packageName and the X-Forwarded-For header. Airbridge does not process an event whose eventTimestamp is more than 24 hours old, so forward late Stripe retries quickly.
Keep secrets such as your Airbridge API token and Stripe signing secret in environment variables or a secret manager. Do not put them in code.
Step 5: Test with one subscription
Use Stripe test mode. Install the app from a test tracking link, sign in, start a trial, and pay. Then check that a Start Trial event and a Subscribe event appear in Airbridge for that user.
Want to see how Connect Stripe subscription revenue to ad campaigns works with your data?
Get hands-on with Airbridge and see real results.
Try It Free →What you will see in the dashboard
Once events flow, these Core reports answer the main questions.
- Revenue report. Pick Subscribe as the Revenue Event. Revenue is credited to the most recent Start Event, with no attribution window. Use it to see revenue by channel and campaign. The report also shows CAC, defined as total ad spend divided by Start Event users. That is not cost per paying customer.
- Actuals. Counts Start Trial, Subscribe and Unsubscribe events by channel and campaign, but only events inside the attribution window. Actuals and Revenue will not match. That is expected.
- Funnel report. Install to Start Trial to Subscribe, by channel. Remember that Subscribe includes renewals.
- Retention report. Subscribe can be the Return Event on Core. This shows whether users from a channel keep paying.
- Trend report. Watch daily Subscribe events and revenue for sudden changes after a release.
- Predictive LTV. A dashboard view of predicted lifetime value up to day 180, by source. It is a machine-learning prediction of user lifetime multiplied by ARPDAU. It is not sent to ad networks.
Cost comes from the ad channel integrations on Core: Meta Ads, Google Ads, Apple Ads and TikTok for Business. Cost data reaches campaign or ad group level, not creative level.
Common mistakes
- No shared user ID. If the SDK user ID and the Stripe metadata do not match, the event cannot be credited to a campaign.
- Sending every Stripe webhook. Each event you send is a data point. Send only the events in the mapping.
- Counting renewals as new subscribers. Subscribe includes renewals. Do not read a Subscribe count as new payers.
- Sending refunds as negative revenue. There is no refund event on Core. Track refunds in Stripe.
- Retries without deduplication. Stripe retries webhooks. Store the Stripe event ID and skip repeats.
- Expecting web-only conversions on Core. Web event measurement is a Growth feature. The Core Web SDK covers web-to-app only.
- Comparing Actuals with Revenue. They use different attribution rules, so their totals differ.
What does it cost on Airbridge Core?
Core is $40+/mo after the 14-day free trial, with no card needed to start. It includes 500K data points per month, then $0.0001 per additional data point. A data point is one event your app or server sends to Airbridge. Installs count. Tracking-link clicks and impressions do not. Each Stripe event you forward is one more data point, so the mapping above keeps usage small.
Billing is monthly, charged in advance. Overage is billed after the period ends. You can cancel from the dashboard any time. There is no minimum term.
The Growth plan (custom pricing, contact sales) adds custom events, raw data export, fraud detection, the Conversions API, web event measurement and 330+ channels.
Customer results
Planfit cut CAC by 40% by optimizing for free trial starts (case study). Bitbyte grew revenue 10x within four months using Predictive LTV (case study). These are Airbridge customers. The case studies do not say which Airbridge plan they used. Neither case study is about Stripe. For more on ROAS, see the Alarmy case study.
Trade-offs to know
- You own the code. The S2S path is a small service, but your team maintains it.
- Three subscription events on Core. Payment failures, refunds and plan changes need custom events (Growth) or your own reporting.
- Four ad channels on Core. If you buy on other networks, you need Growth.
If you already run RevenueCat or Adapty for all billing, use their integration and skip the custom service.
FAQ
Can Stripe send webhooks straight to Airbridge?
No. There is no native Stripe integration. You need a small service between them that verifies the webhook, finds the user ID and sends a standard event to the S2S API.
Do renewals show up separately from first payments?
No. On Core, the first payment, a trial conversion and a renewal all arrive as Subscribe. There is no separate renewal event.
Can I track failed payments or refunds?
Not as standard events. These would be custom events, and custom events are on the Growth plan only. Track them in Stripe on Core.
What if a user pays on the web before installing the app?
Web event measurement is a Growth feature. On Core, the Web SDK covers web-to-app only: it can credit an app install to the web campaign that sent the user to the store. A payment made on the web before an install is not measured as a web event on Core.
Related reading
Ready to transform your mobile growth?
Learn how Airbridge helps leading brands measure and optimize every touchpoint.
“Airbridge understands the essence of what it has to offer as an MMP. Its objective, transparent, and accurate performance analysis allows marketers to realize the true impact of their efforts.”





