In May 2022, Google did it again… And you’ll have to do it again, too!
The fresh face in the brand’s lineup for In-App billing and subscriptions, Google Play Billing Library 5 came with a suite of features and upgrades that promise a smoother In-App Purchase experience for your users and a smarter revenue generation experience for your app.
These updates aren't the only reason to think about leaving the v4 behind.
Historically, getting all the developers to stay on the side of innovation was a challenge. But with this timeline, we should see some more motivation or at least pressure.
But we've got you covered. Everything you need for a safe migration? It's ready with Purchasely's support for Google Billing V5.
Read on!
Google Play Billing Library 5 updates: What subscription apps need to know
- New subscription architecture
Migrating to Google Play Billing Library 4 to 5: Hidden challenges
Here's a breakdown of what’s noteworthy for apps with subscriptions and/or In-App Purchases.
'Migrate to Billing Library 5' - Introduction to Google Play Billing 5 at android dev summit
Image source: Google
Subscriptions: Represents what's being sold to users, including the product and its benefits.
Base plans: Covers how it's sold, detailing whether it's an auto-renewable or a prepaid plan, its duration, and the base price.
Offers: Modifications made to the base price, such as free trials or introductory prices, with developers determining eligibility criteria.
Enhanced purchase tracking: With the introduction of queryPurchasesAsync, developers can now more accurately track and manage user purchases.
▶️ Enhanced purchase visibility allows marketers to build post-purchase engagement strategies, fostering loyalty and repeat business while simultaneously minimizing customer support demands.
Streamlined subscription status retrieval: The new subscriptionPurchasedV2 endpoint allows for a more efficient way of fetching subscription statuses.
Granular purchase insights: The subscriptionPurchases.subscriptionsV2 entity offers detailed insights into every purchased item.
▶️ This means developers can understand user behavior at a micro-level, tweaking offers and strategies based on real-world data.
The migration to version 5 requires a series of steps that can be avoided if you are already monetizing your app with Purchasely. If that is the case, update to the latest Purchasely 4.x SDK version and you are good to go.
The full migration steps are provided by Google here.
While migrating to Google Play Billing v.5, you will come across several challenges.
Here are some major issues, including those that Google hasn’t clearly addressed:
Google suggests you start over with your products using PBL5 before updating your app. This means merging similar products with different prices or durations. And doing it wrong? Your app on PBL4 might break.
Up until GB4, you could retrieve active subscription details using the purchases.subscription.get endpoint.
Since GB5 and its revamped product/base plan configuration, the new purchases.subscriptionsv2.get endpoint is needed to query subscriptions (One-time purchases remain unaffected).
In its May 2022 subscription changes guide, Google highlighted the main differences between the APIs and which properties were mapped from, to, or moved to a completely different API.
Below, we highlight the hidden challenges that will be encountered when migrating to the new API:
🏋 Challenge: Two new endpoints monetization.subscriptions and monetization.subscriptions.basePlans.offers have been introduced to track base plan pricings and offer pricing separately. There's no way to retrieve the history of these changes. For instance, you can't determine the exact price at which a subscription was bought, or if it had a trial and/or introductory offer associated.
In addition, those endpoints do not list the configuration associated with countries that are subdivisions, whereas regionCode can be associated with a subdivision:
If regionCode is PR (Puerto Rico), look for prices the United States (US) region
More subtle, if regionCode is FO (Faroe Islands), look for prices in Denmark (DK) region
▶️ How Purchasely helps: For each purchase, Purchasely helps query the new endpoints, maintain a history of prices, offers, and durations. We recommend useing the Google Play Support Page to retrieve the actual associated country if regionCode denotes a subdivision before querying the base plans / offer endpoints.
⏱ In the past: promotionType, promotionCode fields of purchases.subscription were available directly.
🆕 Now: There is no equivalent to these fields (anticipated to be available soon).
🏋 Challenge: As of September 2023, it's unclear if a subscription was granted using a promotional code by just using purchases.subscriptionsv2.
▶️ How Purchasely helps: Purchasely helps query both SubscriptionPurchase and SubscriptionPurchaseV2. The former has the property to identify promotional code usage, while the latter determines the correct plan linked to the subscription. But, querying both might double your quota usage with Google, risking quota exceedance.
For now, only the Backwards compatible plan (a plan that can be purchased from the older GPBL4) can be associated with promo codes when creating a promo code from the Google Play Console.
We anticipate other base plans becoming available once Google adds the missing fields.
Scratching your head over the migration? Let Purchasely step in to help you escape the maze of updates and adaptations.
Migrating to Google Play Billing v.5 and v.6 doesn't need to be intimidating. With Purchasely, you can ensure your app's billing system remains updated without the typical hassles.
Discover how Purchasely can enhance your app's billing system.
Book a 1:1 chat with us now to learn more about our comprehensive migration solutions and elevate your app's potential.