|
Important:
|
Cleeng supports subscription upgrades and downgrades in native apps (aka In-Apps) – Android, Apple iOS & tvOS, Roku. Subscription switches are important parts of the user experience, as well as effective churn prevention and upselling mechanisms.
In-App subscription switches are configured and controlled by native apps’ ecosystems. Cleeng listens to the notifications and mirrors the changes in the system. To ensure that Cleeng reflects the subscription switches properly, you need to follow the three steps described below.
Configuration and prerequisites
Offer params mirroring
For each subscription offer configured in another system (Android, Apple iOS & tvOS, and Roku), you need to create an analogical offer in Cleeng with the same price, trial duration, and billing cycle. It is essential, as not all offer details are exposed outside InApp platforms. Cleeng follows those details (offer settings such as the price or trial duration) to replicate operations.
It’s not necessary to create separate offers for each platform if the parameters of the offers are identical. If all subscription product parameters are the same, a Cleeng offer with the same parameters can be shared.
Notifications setup
Cleeng performs offer switching based on notifications delivered by InApp systems. To ensure notifications' successful delivery, you need to set up appropriate Cleeng URLs in the InApp systems. Please refer to our InApps integration guides for details:
Linking InApp products to Cleeng offers
Once a subscription upgrade or downgrade happens in the InApp system, a notification is sent to Cleeng. Notifications carry platform-specific subscription product names. Based on the offers mapping, Cleeng can identify a corresponding Cleeng offer and perform an analogical subscription upgrade or downgrade on Cleeng’s side.
Therefore, you need to link the InApp products with corresponding Cleeng offers. You can do that during step 2 of offer creation:
How Cleeng handles subscription switches in the In-Apps
Once the initial subscription purchase is registered in the Cleeng platform via appropriate APIs (for details check the revenant integration guidelines: Apple iOS & tvOS, Android, or Roku), all the following subscription upgrades and downgrades are performed automatically in the background based on notifications delivered from InApp systems to Cleeng.
Your application shall trigger subscription switching with the use of platforms' native APIs or through app stores if possible. No other actions or API calls are needed in Cleeng to handle subscription upgrades and downgrades.