Also I have been trying out the Revenuecat webhook an the "offer_code" is the "Apple offer identifier" rather than the actual code they used. How do you attribute the referrer then if you don't know what the code was?
Awesome solution. I am trying to implement something very similar to this. The idea is that you can share a code with a friend which discounts lifetime premium by 50%. You give that Apple code from the pool to your friend and once they redeem, you credit the referrer via a RevenueCat webhook. My question is: what is stopping the referrer to just use the Apple code in the Apple's redemption sheet and get the reward which is supposed to be for the friend. I understand that in the attribution part you check for "if referrer_id == referee_id: reject", but what is stopping the referrer to use the code which has been given for them to send to their friend? Since you are using Apple's redemption flow I assume you cannot "block" a code for a particular user? Thank you for clarification!
Also I have been trying out the Revenuecat webhook an the "offer_code" is the "Apple offer identifier" rather than the actual code they used. How do you attribute the referrer then if you don't know what the code was?
Awesome solution. I am trying to implement something very similar to this. The idea is that you can share a code with a friend which discounts lifetime premium by 50%. You give that Apple code from the pool to your friend and once they redeem, you credit the referrer via a RevenueCat webhook. My question is: what is stopping the referrer to just use the Apple code in the Apple's redemption sheet and get the reward which is supposed to be for the friend. I understand that in the attribution part you check for "if referrer_id == referee_id: reject", but what is stopping the referrer to use the code which has been given for them to send to their friend? Since you are using Apple's redemption flow I assume you cannot "block" a code for a particular user? Thank you for clarification!