Skip to main content
Question

Offer code redemption via URL in App Store - is offer code exposed?

  • December 13, 2022
  • 5 replies
  • 138 views

Forum|alt.badge.img+3

Hello! I’ve been having a hard time finding a definitive answer in Apple’s docs. As some of these offer code flows appear to only be fully testable in production, it’d be helpful to see if I can get an answer ahead of time.

If we use RevenueCat’s recommended method for redeeming App Store offer codes - that is, creating a custom URL and linking to the App Store where the code is automatically redeemed, does anyone know if the code is exposed to the subscriber at any point in that flow?

Is the offer code shown in the customer’s emailed receipt from the App Store?

We are investigating to see if we can use offer codes to drive discounts in the App Store without exposing those codes to users. So if there is any part of this flow that might expose that code, we’d love to know.

Thank you!

5 replies

Michael Fogel
Forum|alt.badge.img+6
  • Dedicated Contributor
  • 382 replies
  • December 14, 2022

Hello!

 

Honestly they could probably still find the code somehow, since the code is exposed in the URL they would just have to see the URL and we cant guarantee that they would not see the URL. 

 

I can pass this along to the team as something we could look into, but as of now I cant guarantee that the URL would never be seen. 

 

More information about this could be found here: https://www.revenuecat.com/docs/ios-subscription-offers#option-2-redirect-to-app-store-app


Forum|alt.badge.img+3
  • Author
  • Member
  • 7 replies
  • December 14, 2022

We were thinking to have a button in the app which fires the link action to the app store to obscure the link that way - but definitely understood that if the URL was exposed the code would be. Still curious about that redemption flow in the app store. Thank you!


Forum|alt.badge.img+2

Did you ever find out if the code is exposed to the user in the App Store? I’m working on doing the same thing to allow a customer to get a discount if they had purchased an older version of my app. The new app is brand new, with a different bundle identifier. I read the receipt from the old version and determine the original purchase date. If it’s recent, I give them free access to the app for a period of time. If it’s older than a certain point, I give them a 50% discount on the subscription. The only way I can think of doing this is with offer codes, but I don’t want the URLs to be easily visible. I know they can be sniffed on the network, but I’m hoping they’ll at least not be shown to the user in the App Store. 


Forum|alt.badge.img+3
  • Author
  • Member
  • 7 replies
  • February 10, 2025

@Brendan Duddridge I was able to find an example of an app with an offer code and try it out, here is what I learned:

  • It doesn’t look like the code is shown in the redemption flow

    • Of course, Apple could change this at any time, the implementation is not something we control.

  • While we can hide the code in our app by using a button to link to the App Store, We won’t ever be able to fully eliminate the risk of the code being exposed, because the offer code is contained in plain text in the URL that links to the App Store.

Given this, we haven’t moved forward with this approach.


Forum|alt.badge.img+2

@Eric DH Thanks for your reply. I was watching the WWDC video about subscription offer codes last night and they actually did mention that the codes won’t be shown when using the URL. So that’s good. But I agree it’s not an ideal approach. I wish there was a way to ask StoreKit to generate a unique offer code dynamically. I have no logins in my app so I can’t just build a web service that keeps a list of the unique offer codes (that you can download from ASC) and assigns them to each user uniquely.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings