1. In Stripe, open Developers → API keys and choose Create restricted key.
2. Name it WhichPost.
3. Set these to Read and leave everything else at None:
   • Checkout Sessions
   • Customers
   • Subscriptions
   • Invoices
   • Charges and Refunds
   • Promotion Codes
   • Coupons
   Promotion Codes is optional. Without it, purchases won't show which code was used.
4. Choose Create key, confirm it's you, and copy the key. It starts with rk_live_, and Stripe shows it only once.

• Checkout starts, including the ones people left, with the time and country.
• Trials and subscriptions, and the payment that ends a trial.
• Paid invoices, one-off payments and refunds, in the currency you charged.
• The promotion code on each purchase, so a creator's code can confirm a paying user.
• Stripe doesn't know about app installs, so WhichPost counts checkout starts instead. If your app also uses RevenueCat, connect it as well to count installs.
• Not stored: names, email addresses or card details. The key can't create charges, refunds or customers.

1. In RevenueCat, open your project and choose API keys.
2. Choose New secret API key and pick version 2.
3. Set Customer information to Read only. Leave everything else off.
4. Copy the key, and the project ID from Project settings.

Drag this button to your bookmarks bar. On any post, choose it to send the view count you see to this campaign.

Save views

Drag this button to your bookmarks bar, then use it on a post page.