Tapple uses Firebase Remote Config to increase subscriptions by 8%
Introduction
Since 2015, Japanese developer Tapple has been helping people
find love through their popular dating app.
By matching users with similar hobbies and interests, Tapple
has connected over 200 million people, pairing thousands of
new couples every month.
Challenge
Since launching their service, Tapple has experimented with
different ways to maximize the lifetime value (LTV) of their 5
million users. But because it involves many components, LTV can
be a challenging metric to optimize. So the team chose to focus
on their subscription
registration rate, which they knew was a major driver of LTV.
In particular, Tapple wanted more users to purchase a
subscription plan, so they designed an experiment to optimize
their subscription rate. Since male users without a subscription
plan can't read the messages they are sent, the app prompts them
to subscribe when they try to access their messages. Tapple
wanted to test multiple versions of the subscription prompt to
see which one was most effective, so they turned to Firebase for
an easy way to set up and run the experiment.
Solution
Using Firebase Remote Config,
Tapple was able to control and change the subscription prompt
dynamically without releasing a new version of their app,
while Firebase A/B Testing
gave them insight on which variant was performing best. The
team also used Firebase Crashlytics
to monitor the app's stability so that if anything went wrong
during testing, they could use Remote Config to roll back the
feature quickly and easily.
While the team was confident that Design C would be most
effective, Firebase A/B Testing showed that Design A actually
drove the highest conversions. After implementing the winning
design, Tapple saw an 8% increase in subscription
registrations.
Using Firebase, Tapple not only increased their users' LTV,
they were also able to make critical business decisions
backed with data and proven results.
Results
8% increase in subscription registrations
"Optimizing LTV has always been a core focus for us, but it's notoriously hard to do. Firebase gave us the tools we needed to systematically boost the lifetime value of our users, plus put safeguards in place in case anything went wrong. The insights we've gained from Firebase have been invaluable in helping us optimize our user experience to grow subscription sign-ups."
- Shohei Kawano and Wataru Mukainakano, Engineers, Tapple
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[],[],null,["# Tapple Case Study\n\n[*arrow_back*\nExplore other case studies](/case-studies) \n[View more solutions](/solutions) \n\n##### Tapple uses Firebase Remote Config to increase subscriptions by 8%\n\n*** ** * ** ***\n\n##### Introduction\n\nSince 2015, Japanese developer Tapple has been helping people\nfind love through their popular [dating app](https://play.google.com/store/apps/details?id=jp.co.matchingagent.cocotsure).\nBy matching users with similar hobbies and interests, Tapple\nhas connected over 200 million people, pairing thousands of\nnew couples every month.\n\n*** ** * ** ***\n\n##### Challenge\n\nSince launching their service, Tapple has experimented with\ndifferent ways to maximize the lifetime value (LTV) of their 5\nmillion users. But because it involves many components, LTV can\nbe a challenging metric to optimize. So the team chose to focus\non their [subscription](https://support.google.com/googleplay/android-developer/answer/140504)\nregistration rate, which they knew was a major driver of LTV.\n\nIn particular, Tapple wanted more users to purchase a\nsubscription plan, so they designed an experiment to optimize\ntheir subscription rate. Since male users without a subscription\nplan can't read the messages they are sent, the app prompts them\nto subscribe when they try to access their messages. Tapple\nwanted to test multiple versions of the subscription prompt to\nsee which one was most effective, so they turned to Firebase for\nan easy way to set up and run the experiment. \n\n*** ** * ** ***\n\n##### Solution\n\nUsing [Firebase Remote Config](/products/remote-config),\nTapple was able to control and change the subscription prompt\ndynamically without releasing a new version of their app,\nwhile [Firebase A/B Testing](/products/ab-testing)\ngave them insight on which variant was performing best. The\nteam also used [Firebase Crashlytics](/products/crashlytics)\nto monitor the app's stability so that if anything went wrong\nduring testing, they could use Remote Config to roll back the\nfeature quickly and easily. \nWhile the team was confident that Design C would be most\neffective, Firebase A/B Testing showed that Design A actually\ndrove the highest conversions. After implementing the winning\ndesign, Tapple saw an 8% increase in subscription\nregistrations.\n\nUsing Firebase, Tapple not only increased their users' LTV,\nthey were also able to make critical business decisions\nbacked with data and proven results.\n\n*** ** * ** ***\n\nResults\n\n8% increase in subscription registrations \n\n\"Optimizing LTV has always been a core focus for us, but it's notoriously hard to do. Firebase gave us the tools we needed to systematically boost the lifetime value of our users, plus put safeguards in place in case anything went wrong. The insights we've gained from Firebase have been invaluable in helping us optimize our user experience to grow subscription sign-ups.\"\n\n\n- Shohei Kawano and Wataru Mukainakano, Engineers, Tapple \nTry Firebase today\n\n\nIntegrating it into your app is easy.\n[Get started](https://console.firebase.google.com/) \n\n#### All Firebase products\n\n##### Build\n\n- [App Check](/products/app-check)\n- [App Hosting](/products/app-hosting)\n- [Authentication](/products/auth)\n- [Cloud Functions](/products/functions)\n- [Cloud Storage](/products/storage)\n- [Data Connect](/products/data-connect)\n- [Extensions](/products/extensions)\n- [Firestore](/products/firestore)\n- [Firebase ML](/products/ml)\n- [Genkit](https://genkit.dev/)\n- [Hosting](/products/hosting)\n- [Realtime Database](/products/realtime-database)\n- [Firebase AI Logic client SDKs](/products/firebase-ai-logic)\n\n[Generative AI](/products/generative-ai) \n\n##### Run\n\n- [A/B Testing](/products/ab-testing)\n- [App Distribution](/products/app-distribution)\n- [Cloud Messaging](/products/cloud-messaging)\n- [Crashlytics](/products/crashlytics)\n- [Google Analytics](/products/analytics)\n- [In-App Messaging](/products/in-app-messaging)\n- [Performance Monitoring](/products/performance)\n- [Remote Config](/products/remote-config)\n- [Test Lab](/products/test-lab)"]]