Android

5 posts

RevenueCat webhook event names sorted into commissionable and non commissionable columns

RevenueCat Webhooks for Affiliate Commissions Explained

Only four RevenueCat events change what a creator is owed. This is the field level mapping from event to ledger entry, including trials, refunds, aliases and transfers.

Affiliate link click flowing through app install, RevenueCat purchase and webhook to a creator commission

RevenueCat Affiliate Tracking: The Complete Setup Guide

RevenueCat knows what your subscribers paid. It does not know which creator sent them. This guide covers the four ways to close that gap, the webhook events that move money, and the identity edge cases that silently drop commissions.

A phone and a browser window feeding the same affiliate commission ledger

One Affiliate Attribution Engine for Mobile and Web

A creator posts one link and the audience splits across an App Store install and a web checkout. One click id, one window and one ledger cover both, and only four things underneath actually differ.

Two timers on one subscription timeline, from a creator click to a payable commission

Attribution Windows for Subscription Apps: How They Work

Two timers decide whether a creator gets paid: the attribution window bounds credit, the hold window bounds payment. Here is what each one measures, what breaks at the boundary, and the ledger arithmetic for a $9.99 plan with a refund.

One referred signup followed by 24 monthly renewals, with only the first charge marked as paid to the creator

Why Subscription Apps Need Their Own Affiliate Layer

A one-time affiliate payout pays a creator for the signup and ignores every renewal after it. E-commerce affiliate platforms and mobile measurement partners both miss for structural reasons, and this is what a subscription-native attribution layer has to handle instead.