Skip to main content

Hi,

I’m currently trying to figure out how exactly I’m supposed to show promotional offers when using the pre-built paywall created in RevenueCat and displaying it in a iOS app.

I can confirm that the promotional offer exists in the .storekit file.
 

Hi, our paywalls do not support Offer Codes or Promotional Offers yet.


Any timeframe on when the RevenueCat paywalls will support Promotional Offers?


How to implement a promotional Paywall for a holiday sale?

We have an app with a default annual and monthly subscription with a one week free trial introductory offer.  Several times a year, we would like to offer 50% off an annual subscription. We would like to configure two paywalls one which shows for the default pricing, and one that shows for the sale pricing when running.

How is this best implemented with RevenueCat Paywalls?

Within the App Stores it looks like we can either configure an introductory offer or a promotional offer.

Unfortunately, it looks like RevenueCat requires a whole new product offering to configure a paywall?  I don’t see a way to configure a paywall for a promotional offer, and it looks like there is no way to change which paywall is shown based on the introductory offer.  As far as I can tell, we’d need to configure a whole new product to change the paywall when the promotion is running and we’d have to push client side code to determine which paywall is shown.

Is that correct? What is the best way to implement a promotional Paywall for a holiday sale? Ideally, this would all be configured through the revenue dashboard so the client would only need to be configured once.  Any help would be greatly appreciated.


@Colenbrander no ETA at this time.

@Ty Rauber right now our paywalls do not support promotional offers and offer codes. Introductory offers will be automatically applied though and you can describe them with the variables we provide: https://www.revenuecat.com/docs/tools/paywalls/creating-paywalls#variables

 

If you want to use our paywalls for a holiday sale, you can do this in a couple of ways. Introductory offers are automatically applied to eligible users so you could configure this information on your paywall. Alternatively you could create separate annual products priced at 50% off that you can have in a new offering and paywall to display. 

 

Let me know if you have any questions on this.


Just came here to add that promotional offers in paywalls would be phenomenal. The promo codes should link to RevenueCat offerings.

  • A promo code button on the paywalls that opens up a “redeem promo code” UI
  • the ability for users to type in promo codes in that UI. I tried various ways for redeeming promotions on my users in the past, like links and QR codes. Most users really expect that they have to type in the code.
  • The ability for RC to then display a new paywall with the promo code applied, where a promo code is tied to an offering.
    • Optionally the ability to have promo codes that don’t just display a new offering but grant a free duration without automatically enrolling in a sub afterwards. We use this for schools where we don’t want students to be charged afterwards if they use our app in class, but I guess that’s a niche use case.
  • Plus the ability for RC to check whether a code has already been redeemed by a user so users can’t redeem the same offer twice if the promo code doesn’t allow it.

Right now I had to program all of that myself and it is quite a lot of work. Promo codes are super important for social media channel acquisition though -  the usual “use the promo code {CHANNELNAME} for 20% off” on YouTube, for example.

Ideally this logic would be split into two components: the purchase flow in the regular RevenueCat SDK for developers who want to build their own views, and then the same thing integrated into RevenueCatUI.

This isn’t supported by companies like Superwall either, and would really set RevenueCat apart.


Hey ​@Thomas Walther, thanks for the feedback! I’m sharing this with our paywalls team to see if there’s more that we could do on this front.


Reply