Stripe Sync
Signal Sparrow's conversion events come from your Stripe account — not from guesses or pixels. This page explains how that sync works once you've connected Stripe.
Read-only, always
The connection is read-only. Signal Sparrow can see your subscriptions and payments, but it can never charge, refund, or change anything in Stripe. It only reads.
Two ways data flows in
1. Real-time (webhooks)
As things happen in Stripe — a trial converts, a subscription starts, a plan changes — Stripe notifies Signal Sparrow instantly. Each notification becomes the matching conversion event, which is then attributed to the campaign that earned it. This all happens automatically within seconds.
2. History (backfill)
When you first connect, Signal Sparrow can also read your past Stripe activity so your reports aren't empty on day one. This gives you an immediate baseline of revenue movement to look at.
Backfilled history is used to build your reports and totals. It is not re-sent to ad platforms — only fresh, live conversions are forwarded onward, so your ad accounts never receive a flood of old events.
From Stripe event to revenue movement
Each Stripe change maps cleanly to how your MRR moved:
| In Stripe | Conversion event | MRR movement |
|---|---|---|
| Trial converts / new subscription | Trial Converted / Subscription Started | New |
| Plan increased | Upgraded | Expansion |
| Plan decreased | Downgraded | Contraction |
| Subscription cancelled | Churned | Churn |
| Payment refunded | Refunded | Refund |
Because every movement traces back to real Stripe records, your numbers always reconcile to what's actually in your account.