使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Tapple 使用 Firebase Remote Config 将订阅量增加了 8%
简介
自 2015 年以来,
日本开发商 Tapple 一直在通过其广受欢迎的约会应用帮助人们找到真爱。
通过匹配爱好相似、兴趣相投的用户,
Tapple 已经帮助超过 2 亿人建立了联系,
每月促成数千对新情侣。
挑战
自从推出这项服务以来,Tapple 尝试了多种不同的方式
来最大化其 500 万名用户的
生命周期价值 (LTV)。但由于
生命周期价值指标涉及到的元素为数众多,优化难度极大。该团队选择专注于
订阅注册率,
因为这是生命周期价值的主要驱动因素。
具体来说,Tapple 希望有更多用户购买订阅方案,
为此,他们设计了一个实验来优化订阅率。
没有购买订阅方案的男性用户
无法阅读别人发来的消息,于是应用会在他们尝试访问消息时
提示他们订阅。Tapple 希望测试
多个版本的订阅提示文字,
看看哪个版本效果最佳,他们为此选择了 Firebase,
希望找到一种简单的方式来设置和运行实验。
解决方案
尽管团队先前确信设计 C 将最为有效,
但 Firebase A/B Testing 表明,设计 A 带来的转化率
实际上是最高的。在实施测试表现
最好的设计后,Tapple 的订阅注册量
增加了 8%。
借助 Firebase,
Tapple 不仅增加了用户的生命周期价值,
还在数据和经验证的结果的支持下制定了多项关键业务决策。
"优化生命周期价值 (LTV) 一直是我们的核心关注点,而这项任务的难度众所周知。Firebase 为我们提供了必要的工具,支持我们系统性地提高我们用户的终身价值,此外也提供了许多保护措施,让我们在遇到问题时安心无忧。通过 Firebase 获得的数据洞见无比宝贵,切实帮助我们优化了用户体验,从而增加订阅服务注册数。"
- Tapple 工程师 Shohei Kawano 和 Wataru Mukainakano
[null,null,[],[],[],null,["[*arrow_back*\nExplore other case studies](/case-studies) \n[View more solutions](/solutions) \n\nTapple uses Firebase Remote Config to increase subscriptions by 8% \n\n*** ** * ** ***\n\nIntroduction Since 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\nChallenge Since 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\nSolution \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\nAll Firebase products \n\nBuild\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\nRun\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)"]]