Stripe revenue, next to the visit that paid.
Tapll verifies every Stripe webhook against your endpoint’s signing secret and counts the money in its own block. Pass the visit’s id into Checkout and a payment is tied to the first-touch channel and campaign of that visit.
What you get. Once Stripe is connected.
Revenue for the website
Gross revenue, trials, renewals, cancellations and refunds from Stripe, with MRR and a breakdown of how it moved.
Money at each source
Purchases per channel and campaign when checkout carries `tapll.sessionId()`. It shows what goes with a source, first-touch, and never claims the source caused the sale.
Kept apart from the app
Website money is never added to in-app revenue, and not to Paddle either: each source is its own block.
What it needs.
- A webhook URL created in Tapll and added in the Stripe Dashboard under Developers → Webhooks.
- The endpoint’s signing secret (`whsec_…`) pasted back into Tapll. It is stored but cannot be checked until the first delivery arrives.
- `tapll_session_id` set from `tapll.sessionId()` in the metadata of the Checkout Session and of the subscription.
What Tapll keeps, and what it does not.
- Amounts in the currency charged, product, plan and the event behind each change.
- The customer only as a keyed hash: no email, name or address reaches Tapll.
- A USD amount only when the charge was in USD; otherwise none, and Tapll does not convert.
Questions about Stripe.
What if a payment has no visit attached?
It still counts as revenue. It just has no channel or campaign, and the panel shows how much revenue has none.
Does it replace RevenueCat or App Store notifications?
No. Stripe describes purchases on the web; RevenueCat and Apple describe purchases in the app. Both run side by side and are never summed.
Does Tapll change anything in Stripe?
No. Tapll only receives webhooks. Events it does not use are acknowledged and ignored.
Other integrations.
- IntegrationWebsite scriptOne script tag for your website: visitors, page views, sources and campaigns, cookieless by default.Read more
- IntegrationRevenueCatSubscriptions, trials, renewals and refunds from RevenueCat webhooks, tied to the sessions that bought them.Read more
- IntegrationApp Store Server NotificationsRevenue straight from Apple’s signed notifications, with your own backend still receiving every one.Read more
- IntegrationPaddleWebsite sales from Paddle Billing notifications, tied to the visit and channel that brought them.Read more
- IntegrationApp Store ConnectDownloads, impressions, product page views, proceeds, reviews and TestFlight from your App Store Connect key.Read more
- IntegrationApple Search AdsSearch popularity for the phrases you track, from Apple’s own genre lists.Read more
- IntegrationSurvicateNPS answers from Survicate surveys, next to retention and revenue — the score, never the comments.Read more