Feature Ideas

Revenue cat has LTV prediction which is so helpful please alsl add in qonversion.

On iOS the IDFA-free build is CocoaPods-only, via pod ‘Qonversion/NoIdfa’. Currently the SPM package ships a single “Qonversion” product that always compiles the IDFA code in, so to enable kids mode on iOS is a big change to a KMP project compared to Android which just need to add one line .enableKidsMode() :(

I'm reluctant to allow any AI to perform any configurations, but would like them to help to verify whether my Qonversion configurations matches with my app so a read only permission for all settings including the Integration section would be great. I have tried creating a new member and assigned it developer role to be used for MCP, but that role don't have permission to view the Integration section. So a read only role with full view of everything is what I'm looking for. Either a new role that allows me to do that or allows us flexibility when connecting the MCP to choose read/write permission for each category would be great.

Can you provide an iOS App for Analytics? Thanks.

Be up-to-date with AppStore's payment infrastructure

Glassfy had the feature for universal promo codes that are independent of the AppStore / PlayStore. I would like to have that on Qonversion. Details here: https://docs.glassfy.io/docs/universal-codes

We sometimes need to have the iOS receipt for manual verification. It would be great to have it in the customer profile section. Thank you!

I want to be able to see a list of customers who never purchased any subscriptions or in-apps inside the Customers tab.

Is it possible to add a chart for retention showing % of users who renew after the free trial - 1st / 2nd / 3rd renewal periods - with filter by subscription type? We’d like to see more exactly when users are cancelling / churning, to be able to develop a targeted retention strategy accordingly.

It would be really helpful if I could get a consumable entitlement for in-app purchases that lets me use the item right after it’s delivered to the user. This should also take into account the quantity of items purchased. Also, this way, we could effectively resolve the problem of pending purchases for consumable in-app items.