Refficks

RevenueCat affiliate tracking with Refficks

RevenueCat reports every App Store and Google Play purchase, renewal and refund your app makes, so app subscriptions credit the partner who brought the customer.

Nobody has walked these steps against a real RevenueCat setup yet. They are built from the provider's documentation, listed at the bottom of this page.

What it gives you

  • Every first purchase and renewal is a sale on RevenueCat's price in US dollars before its estimated tax, so an app sale and a web sale of the same plan pay alike. A programme can earn on the estimated proceeds instead, after the store's cut, for sales from the day it switches.
  • A free trial earns nothing; the partner is paid when it turns into a paid subscription.
  • A refund RevenueCat reports takes back its share of the commission.
  • Renewals of a subscription a partner won keep paying that partner, even when RevenueCat moves the purchase to another app user, and a subscription that already paid once is never a first sale again.

What it does not

  • RevenueCat reports a refund only when the latest period is refunded. A refund of an earlier month never reaches Refficks: cancel its commission on the Commissions screen.
  • Amounts are RevenueCat's: its conversion to US dollars and its estimates of tax and the store's cut, not what Apple or Google pays you.
  • Sandbox purchases are shown and never credited. Family Sharing grants and free promotional grants credit nobody, because nobody paid.
  • Purchases made through your own Stripe account are counted through your Stripe connection when it is connected, never twice.
  • Refficks never matches people by device, IP address or advertising id. A purchase from someone Refficks has not seen before credits nobody.
  • Refficks keeps each delivery as RevenueCat sent it, except a buyer's IP address, which is never stored.
  • Apple reversing a refund does not give the commission back by itself. Your admins are told whose commission it was, and somebody takes the reversal back in History while nothing has been paid on it.

Steps

These are the steps as they read inside Refficks. Where one says “below”, it means this guide's page in Refficks, where your own script, addresses and checks are.

  1. 1. Connect RevenueCat

    Press Connect below. Refficks shows you an address and an Authorization value. The value is shown once.

    In RevenueCat, open your project → Integrations → Webhooks → Add new configuration. Paste the address as the webhook URL and the value as the Authorization header, and send events for production purchases. Sandbox purchases are never credited, so sending them only fills the list below.

    Recommended: turn on signing for the webhook in RevenueCat and paste its signing secret below. Every delivery is then checked against it too.

    Press Send test event in RevenueCat. It arrives below and says the connection works.

    The connection is made on this guide in Refficks, once you have an account.

  2. 2. Tell RevenueCat who bought

    Use the same user id in your app (Purchases.logIn) as the one your website gives Refficks when the person signs up. That is the surest way: no code in your app beyond what you have.

    For a code a customer types or taps in your app, set the subscriber attribute refficks_ref to it; for a visitor who came from your website, pass the visitor id the Refficks script keeps (the rk_vid cookie) to your app and set refficks_visitor. Set them before you show the paywall: an attribute set after the purchase reaches only the next renewal.

    Your copy of the Refficks script, with your own key in it, is on the Integrations page in Refficks.

  3. 3. Give each partner their code in the stores

    Create each partner's App Store offer code or Google Play promo code spelt the same as their Refficks code. A purchase that redeems it is credited to that partner, with no code in your app.

Sources

Have an account? Open this guide in Refficks for your own script and the checks that show when it is working. New to Refficks? Create an account.

More in Checkouts and billing