For teams billing through Stripe
Stripe creator attribution: see which posts paid
Stripe knows every checkout, trial and payment. It doesn't know which creator's post sent the buyer. Connect a read-only key, add the posts you paid for, and WhichPost connects the two, with a range on every result.
The short answer
Create a restricted Stripe key with read access and paste it with links to your creator posts. WhichPost reads when people started a checkout or a trial and when they paid, credits each creator's posts with the paying customers they brought, each with its likely range, and sets that against what you paid them.
The problem
Your revenue is in Stripe. The reason it arrived isn't.
Stripe records the sale, not the post that caused it. The usual fixes each leave a gap.
-
Checkout tags need a click
Tagging checkouts with a creator ID works only when the buyer arrives through that creator's link. People who watched, then typed your name into Google, arrive untagged.
-
Coupons count the few who type them
A Stripe coupon per creator gives clean counts for the customers who use it, and nothing for everyone else the post persuaded.
-
Dashboards show totals
Revenue went up the week of the campaign. Which creators earned it, and who to book again, isn't in the chart.
How WhichPost answers it
From a read-only key to a call on every creator
About two minutes to connect. Nothing changes in your checkout, your site or your captions.
Connect Stripe read-only
Create a restricted key with read access and paste it. Full secret keys are turned away, and a read-only key can't charge anyone, refund a payment or change your account.
Add your creator posts
Paste links to the posts you paid for, from a clipping platform, an agency or a direct creator deal. WhichPost checks their public views every hour.
See which posts paid
Every creator ranked by the paying customers they brought, each with its range, and their cost per paying customer set against your limit.
What you need
Two things to connect. Nothing to install.
No SDK, no tracking links and no changes to your app, checkout or captions.
Stripe or RevenueCat
A restricted, read-only Stripe key for a web product, or a read-only RevenueCat key for a mobile app. Connect both if you sell in both places.
The posts you paid for
Links to the TikTok, Instagram or YouTube Shorts posts, from a clipping platform, an agency's sheet or direct creator deals.
Enough daily volume
About 20 new sign-ups or installs a day or more, and at least a week of history before the campaign started. A free data check tells you whether your data is enough before you pay.
Questions
Questions, answered.
What does WhichPost read from Stripe?
Checkouts, customers, subscriptions, invoices, refunds and promo codes: when someone started a checkout or a trial, when they paid and how much. It keeps times, amounts, countries and Stripe's customer IDs. It doesn't keep names, emails or card details, and it never contacts your customers.
Is WhichPost made by Stripe?
No. WhichPost is an independent product, not made or endorsed by Stripe. You create a restricted key in your own Stripe account and paste it here. Revoke it in Stripe at any time and syncing stops.
Do I need to tag checkouts or add links?
No. WhichPost works from the timing of your posts' views and your Stripe events, so there's nothing to tag. If you already tag checkouts or give creators coupons, keep them: the report shows code-confirmed customers next to our models' results.
What about our mobile app?
Mobile apps connect RevenueCat, which adds installs and trials from the App Store and Google Play. If your app also sells on the web through Stripe, connect both.
More guides
Other questions teams ask
See which of your creators paid
Connect in about two minutes, or look through a sample report first. Every result comes with its range.